On Thu, 2011-12-15 at 09:16 +0000, Jeremy Bennett wrote: > On Wed, 2011-12-14 at 00:04 +0100, Franck JULLIEN wrote: > > Hello, > > > > I found the solution to my link libgcc problem. > > > > I'm using or32-elf. > > > > I needed to add "-L $(shell dirname `$(CC) $(CFLAGS) > > -print-libgcc-file-name`) -lgcc" to the final link. > > > > Is there any other solution ? > > Hi Franck, > > Apologies, but I can't find your posting of the original problem. Could > you repost, and then I can try to help. You should not need to go > through a contortion like this for any normal use of GCC. >
I belive we resolved this on IRC yesterday. Franck's app is a bootloader and doesn't use any standard libraries, so he really does need to pull in the support bits (i.e. libgcc) by hand. This is in line with what other apps at the bottom of the stack (Linux, u-boot) need to do. /Jonas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
