Re: [openrisc] clueless regarding or1ksim/testbench

[Simon Srot <simons@opencores.org>]

Hi Richard,

The README file in testbench is was not up to date. I change it. You
should use or32-uclinux tool chain to build the testbench. Also, don't
forget to install uClibc before building testbench. 

Simon

Richard Prescott wrote:
> 
> I am following README instructions and I don't understand how it can
> works.  What I am doing wrong ?
> 
> [rip@carduel testbench]$ ./configure --target=or32-rtems
> creating cache ./config.cache
> checking host system type... i686-pc-linux-gnu
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... found
> checking for working autoconf... found
> checking for working automake... found
> checking for working autoheader... found
> checking for working makeinfo... found
> checking whether make sets ${MAKE}... (cached) yes
> checking for a BSD compatible install... /usr/bin/install -c
> checking build system type... i686-pc-linux-gnu
> checking for or32-rtems-gcc... or32-rtems-gcc
> checking for or32-rtems-ranlib... or32-rtems-ranlib
> checking for or32-rtems-ld... or32-rtems-ld
> checking for or32-rtems-sim... or32-rtems-sim
> checking for strerror in -lcposix... no
> checking how to run the C preprocessor... /lib/cpp
> checking for ANSI C header files... no
> checking for gcc... (cached) or32-rtems-gcc
> checking whether the C compiler (or32-rtems-gcc  ) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
> 
> (NOTE: I am not a automake/autoconf expert)
> 
> I cannot remove 'AC_CHECK_TOOL(CC, $target-gcc, cc)' otherwise no compiler
> will be defined and I cannot leave it there (like it is right now) because
> or32-rtems-gcc cannot find its crt0.S...   What I am doing wrong ?
> 
> --
> To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml
--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml