OPENCORES.ORG

-- Messaggio originale --

Hi,
thanks for your  feedback.
I run aclocal && automake && autoconf, after running autoconf I get:
configure.in:62: warning: AC_TRY_RUN called without default to allow cross
compiling
autoconf: Undefined macros:
configure.in:68:AC_CHECK_TYPES([uint8_t, uint16_t, uint32_t],,, [#include
<inttypes.h>])
configure.in:69:AC_CHECK_TYPES([int8_t, int16_t, int32_t],,, [#include <inttypes.h>])

I tried to run anyway the or1k_ats_uclinux.sh script but I get the following

error (only part of the log is reported):

checking for sys/file.h... yes
checking for locale.h... yes
checking for net/ethernet.h... no
checking for sys/ethernet.h... no
checking for malloc.h... yes
checking for inttypes.h... yes
checking whether byte ordering is bigendian... no
../or1ksim/configure: 2016: Syntax error: word unexpected (expecting ")")
/bin/sh ./config.status --recheck
./config.status: Can't open ./config.status: No such file or directory
make: *** [config.status] Error 2

What I'm still missing?

Thanks again
Stefano

>-- Messaggio originale --
>Date: Fri, 18 Feb 2005 12:24:18 +0100
>From: "György 'nog' Jeney" <nog@s...>
>To: List about OpenRISC project <openrisc@o...>
>Subject: Re: [openrisc] or1ksim compilation problem
>Reply-To: List about OpenRISC project <openrisc@o...>
>
>
>> I was trying to install the whole tools chain but I have problem with
>> or1ksim installation package. I downloaded the package few hours
>> ago but is seems not consistent. Files like configure.in and Makefile.in
>> are referring to sub-directory or1ksim/extras but is is empty!
>> 
>> The configure script will try to look for rules files inside this
>> directory
>> and it will stop sicne they don't exist in the original data base.
>> 
>> Any suggestion?
>
>Recently the extras directory became the port directory.  We are still
waiting
>for the opencores admin to regenerate configure and the Makefile.ins. 
In
>the
>mean time all you have to do is run `aclocal && automake && autoconf' in
>the
>or1ksim top directory and then proceed with the standard build procedure.
>
>nog.
>_______________________________________________
>http://www.opencores.org/mailman/listinfo/openrisc