[uClibc]uclibc buildroot woes

[Erik Andersen]

On Tue May 06, 2003 at 12:46:36PM -0600, Jeremy Jones wrote:
> Trying to generate a uclibc system from the buildroot scripts, I'm
> bumping into a couple problems.  The first: binutils in gcc_target. 
> This may be due to something I lack in my host distribution... anyway
> here's the last few lines before bombing:
[-------------snip--------------]
> `/usr/src/buildroot/build_i386/binutils-target/bfd/doc'
> /usr/src/buildroot/build_i386/staging_dir/bin/i386-uclibc-gcc -c -I..
> -I/usr/src/buildroot/toolchain_build_i386/binutils-2.13.2.1/bfd/doc/..
> -I/usr/src/buildroot/toolchain_build_i386/binutils-2.13.2.1/bfd/doc/../../include -I/usr/src/buildroot/toolchain_build_i386/binutils-2.13.2.1/bfd/doc/../../intl -I../../intl  -g -O2 /usr/src/buildroot/toolchain_build_i386/binutils-2.13.2.1/bfd/doc/chew.c
> /usr/src/buildroot/build_i386/staging_dir/bin/i386-uclibc-gcc -o chew
> chew.o
> ./chew -f
> /usr/src/buildroot/toolchain_build_i386/binutils-2.13.2.1/bfd/doc/doc.str </usr/src/buildroot/toolchain_build_i386/binutils-2.13.2.1/bfd/doc/../aoutx.h >aoutx.tmp
> /bin/sh: ./chew: No such file or directory
> make[3]: *** [s-aoutx] Error 127

This is a bug in the gcc build, it is trying to run a target
binary on the build system.  The simplest way to fix it is to add
in an '/lib/ld-linux.so.0' symlink to your uClibc shared lib
loader, allowing your target binaries to also run on your host
system.   The real fix is for me (or even better someone else ;)
to teach gcc to behave itself and not run target binaries on the
host.  It looks like this 'chew' program is intended to be a host
binary, not a target binary, so probably just a simple
Makefile.in fix is needed.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--