On Wed, 2011-03-16 at 09:52 +0100, Paul Menzel wrote: > I am sorry. But I could not find an error message anywhere in > `log.do_compile`. Please find the log file attached.
One of libtool's less endearing features is that it runs the compiler for shared objects with errors directed to /dev/null. I guess this is to avoid getting repeated warnings for objects that are compiled both shared and nonshared, but it does make it more tedious to debug this kind of crash. Anyway, the line in question is this one from your log file: arm-oe-linux-uclibceabi-libtool: compile: arm-oe-linux-uclibceabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi -DHAVE_CONFIG_H -I. -I.. -DASN1_BUILDING -I./../gl -I./../gl -I./.. -fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os -pipe -g -MT coding.lo -MD -MP -MF .deps/coding.Tpo -c coding.c -o coding.o >/dev/null 2>&1 If you run that compile command manually with the ">/dev/null 2>&1" bit removed then you should be able to see the errors. Given that it's apparently happening only with -fPIC enabled I would suspect that it's an ice of some kind, rather than being uclibc's fault directly, but once we have the error message it should be fairly obvious what's gone wrong. p. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
