[uClibc] Re: Building gcc-3.4.1 in buildroot

Peter S. Mazinger ps.m at gmx.net
Wed Oct 27 19:30:05 UTC 2004


> On Wednesday 27 October 2004 13:15, Ivan Popov wrote:
> > On Wed, Oct 27, 2004 at 12:12:01PM +0300, Denis Vlasenko wrote:
> > > make[2]: Entering directory `/usr/src/gcc-3.4.1.obj/gcc'
> > > stage1/xgcc -Bstage1/ -B/usr/app/gcc-3.4.1/i386-pc-linux-gnu/bin/   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition     -DHAVE_CONFIG_H -DGENERATOR_FILE  -o genmodes \
> > >  genmodes.o errors.o ../libiberty/libiberty.a
> > > 
> > > 	genmodes is built
> > > 
> > > ./genmodes -h > tmp-modes.h
> > > /bin/sh: line 1: ./genmodes: No such file or directory
> > 
> > Hello Denis,
> > 
> > the message relates most probably to the hardcoded path to the implicit
> > dynamic loader. Make strings genmodes and check if the path relates to
> > a valid object.
> 
> strings yields this, among other stuff:
> 
> /lib/ld-linux.so.2
> libc.so.0
> 
> Hmmmmmm...... hehe.. symlink ld-linux.so.2 -> ld-uClibc-0.9.26.so
> did the trick ;)
> 
> Thanks!

I think you have some other problem:
1. haven't patched gcc w/ the buildroot patches and/or updated config.sub/config.guess
2. your system shows up as i386-pc-linux-gnu instead of i386-pc-linux-uclibc
3. you are missing -DUCLIBC from the compile-line you are showing above

These will definitely cause picking up the wrong interpreter (in your case 
ld-linux.so.2 instead of ld-uClibc.so.0)

Peter

-- 
Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2




More information about the uClibc mailing list