Hidden error(?) during build

michael michael@araneidae.co.uk
Sun Jan 4 13:07:00 GMT 2009

Building powerpc-405-linux-gnu I noticed one error message (I've elided 
the path for clarity):

[ERROR]    .../powerpc-405-linux-gnu/build/build-libc/elf/ld.so.1: 1: Syntax error: "(" unexpected

This is building on Ubuntu; building on RHEL I get the slightly more 
illuminating message (but not flagged as an error):

[ALL  ]    /bin/sh: .../powerpc-405-linux-gnu/build/build-libc/elf/ld.so.1: cannot execute binary file

The line in the log file above this error message is equivalent to the 
following code (refactored and elided to make it actually readable):



for spec in $(
        LC_ALL=C GETCONF_DIR=/dev/null $PP/elf/ld.so.1 \
            --library-path $LIBPATH $PP/posix/getconf \
    /usr/bin/install -c $PP/posix/getconf $SR/usr/libexec/getconf/$spec.new
    mv -f $SR/usr/libexec/getconf/$spec.new $SR/usr/libexec/getconf/$spec

Ah: now all is clear.  *Somebody* is trying to execute the target ld.so.1 
-- that's not going to work, now is it?

I don't know whether this actually matters, and whether the offending code 
is in crosstool-ng itself, or is part of glibc (I guess my money isss with 
glibc).  Still, it's a bit bothersome.  The built toolchain actually seems 
to work just fine -- I think the only side effect here is that 
sys-root/usr/libexec/getconf is empty -- but something odd to notice!

For unsubscribe information see http://sourceware.org/lists.html#faq

More information about the crossgcc mailing list