|
From: Tom H. <to...@co...> - 2009-10-09 14:57:48
|
On 09/10/09 15:43, Brandon Rioja wrote: > I’m getting some problems, still. > > This is the error: > > /opt/montavista/cge50/montavista/cge/devkit/ppc/85xx/bin/ppc_85xx-gcc > -Wno-long-long -Wno-pointer-sign -Wdeclaration-after-statement > -fno-stack-protector -o memcheck-ppc32-linux -static > -Wl,-defsym,valt_load_address=0x38000000 -nodefaultlibs -nostartfiles -u > _start -m32 -Wl,-T,../valt_load_address_ppc32_linux.lds > memcheck_ppc32_linux-mc_leakcheck.o > memcheck_ppc32_linux-mc_malloc_wrappers.o memcheck_ppc32_linux-mc_main.o > memcheck_ppc32_linux-mc_translate.o memcheck_ppc32_linux-mc_machine.o > memcheck_ppc32_linux-mc_errors.o ../coregrind/libcoregrind-ppc32-linux.a > ../VEX/libvex-ppc32-linux.a -lgcc > > /opt/montavista/cge50/montavista/cge/devkit/ppc/85xx/bin/../lib/gcc/powerpc-montavista-linux-gnuspe/4.2.0/libgcc.a(divdf3.o): > In function `__divdf3': > > /home/build/BUILD/gcc-4.2.0/objdir/gcc/../../gcc/config/soft-fp/divdf3.c:44: > undefined reference to `abort' It looks like your libgcc has references to the abort() function in the C library but we (deliberately) don't link the with the C library. libgcc is supposed to be low level support routines for gcc generated code to call and shouldn't really be calling C library routines like that as it stops you being able to compile code that doesn't link with the C library. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |