Re: [openrisc] or32 compile errors

["Jeff Hanoch" <jeff@lowrance.com>]

A little more information on that last message:

I renamed my or1k directory and then checked out a brand new fresh copy of
the or1k tree from CVS.  I built all the tools in the order shown on the web
site regarding the GNU toolchain.  The tool installs went smoothly.  I also
added the /opt/or32-rtems/bin to my path.  I then compiled and installed the
or1ksim simulator as follows:

./configure --target=or32-rtems --prefix=/opt/or32-rtems && make all install

This also worked without any problems.  Then I wanted to try the
testbenches, so I cd'd into the testbench directory and typed the following:

./configure --target=or32-rtems

I get the error show below in the previous message.  I am hoping something
has changed in the recent past because I ran this command on a different
system which has an older version of the or1ksim (probably a month old) and
it works correctly.  Or maybe I am doing this wrong.  Any suggestions would
be appreciated.

Thanks,
Jeff

----- Original Message -----
From: "Jeff Hanoch" <jeff@lowrance.com>
To: <openrisc@opencores.org>
Sent: Friday, April 12, 2002 11:02 PM
Subject: Re: [openrisc] or32 compile errors


> Marko,
>
> I went back to look at the tests in the or1ksim/testbench directory.  I
> cannot get the ./configure --target=or32-rtems to work.  Could you or
> someone try this to see if they are having the same problem.  Here's my
> transcript:
>
> [jeff@control testbench]$ ./configure --target=or32-rtems
> loading 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 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.
> [jeff@control testbench]$
>
> thanks,
> Jeff
>
> ----- Original Message -----
> From: "Marko Mlinar" <markom@opencores.org>
> To: <openrisc@opencores.org>
> Sent: Tuesday, April 09, 2002 12:53 AM
> Subject: Re: [openrisc] or32 compile errors
>
>
> > > Ok, I put your code into a file called sample1.c.  I compiled it as
> > > follows.  It compiled cleanly.
> > >
> > > [jeff@asic1 jeff]$ or32-rtems-gcc -g -o sample1.or32 sample1.c
> > You should specify -nostdlib option, to tell the gcc that you are not
> > compiling
> > for rtems. Also some linking script -T options should be also supplied
> (look
> > into ld documentation, e.g. 'info ld' or take a look into
> or1ksim/testbench
> > how
> > tests are compiled. You can also run configure and make there, and run
> those
> > tests with the DDD.
> >
> > > The simulator spewed some MEMWRITE and MEMREAD statements.
> > yes, this is due to the wrong linking. You should also place your
> > memories --
> > set your .cfg file according to the link file.
> >
> > > I am unable to interupt the debugger.  The machine code window says
"No
> > > Code."  I have to kill the debugger and restart it to get the gdb
> > > command line back.  Any suggestions as to what I am doing wrong?
> > >
> > > Thanks for any advice
> > > Jeff
> > no problem, the rest looks ok. I hope it will work now.
> >
> > Marko
> >
> >
> > --
> > 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
>

--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml