Re: Re: [openrisc] or32 compile errors

["Damjan Lampret" <lampret@opencores.org>]

----- Original Message -----
From: "Damjan Lampret" <lampret@opencores.org>
To: "Marko Mlinar" <markom@opencores.org>
Sent: Thursday, August 08, 2002 6:51 PM
Subject: Re: Re: [openrisc] or32 compile errors


> > > 2) You can create your own crt0.o in install_path/or32-uclinux/lib
> (where
> > > install_path could be /opt/or32-uclinux - note or32-uclinux needs to
be
> > > repeated twice !). Important is that you put _start function in your
> > > crt0.o. You can try something like this:
> > It is maybe better to specify -nostdlib when compiling, if you are not
> > planning to use uclibc at all, but you have or32-uclibc complier.
> > You can also build or32-elf compiler. AFAIK this should work ok,
> > but I did not test it.

 Issue is that when you execute or1ksim/testbench/configure it will do part
of the configure procedure also check of the or32-* gcc tool if it can
generate an executable. There you can't specify -nostdlib. So what happens
configure fails even before it generate Makefiles.

 regards,
 Damjan



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