DejaGNU testsuite does not build in toolchain

Bernd Pol bernd.pol at online.de
Wed Jan 17 17:53:56 PST 2007


Dan Nicholson schrieb am 17.01.2007 23:47:
> On 1/17/07, Bernd Pol <bernd.pol at online.de> wrote:
>> Hi all,
>>
>> while building the tool chain according to SVN-20070109, ch. 5.10,
>> DejaGNU refused to build its test suite (make check):
>>
>> ------------------------------------
>> make[4]: Entering directory `/mnt/lfs/sources/dejagnu-1.4.4/testsuite/libdejagnu'
>> if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"dejagnu\" -DVERSION=\"1.4.4\"  -I. -I.    -I../.. -g -g -O2 -MT unit.o -MD -MP -MF ".deps/unit.Tpo" \
>>   -c -o unit.o `test -f 'unit.cc' || echo './'`unit.cc; \
>> then mv -f ".deps/unit.Tpo" ".deps/unit.Po"; \
>> else rm -f ".deps/unit.Tpo"; exit 1; \
>> fi
>> g++ -I../.. -g -g -O2   -o unit  unit.o
>> /lib/libc.so.6: undefined reference to `_dl_out_of_memory at GLIBC_PRIVATE'
>> collect2: ld returned 1 exit status
>> make[4]: *** [unit] Error 1
>> make[4]: Leaving directory `/mnt/lfs/sources/dejagnu-1.4.4/testsuite/libdejagnu'
>> ------------------------------------
> 
> For some reason, you are still using your host's glibc instead of the
> new one you built in /tools. See where it says /lib/libc.so.6, ... At
> that point, you should be using the libc.so in /tools/lib. Something
> has gone wrong in your toolchain adjustment in Ch. 5.7, I think.
> 
> I believe the problem is that you're still using the binutils ld with
> the old LIB_PATH. What's the result of this command?
> 
> $ /tools/bin/ld --verbose | grep SEARCH_DIR
> 
> I get
> 
> SEARCH_DIR("/tools/i686-pc-linux-gnu/lib"); SEARCH_DIR("/tools/lib");

I get exactly the same reading. There is something weird going on.
I tried rebuilding the toolchain again from scratch, just in case.
No change.

Scanning config.log and the Makefiles gives no clue either.
Only references to /tools as it should be.

"make check", or "make -k check" keeps breaking. However, when I try
to catch the make output using e.g.:

(make -k check 2>%1 | tee testrun.log && exit $PIPESTATUS )

no obvious error occurs. Telling from this log not even a linker seems
to be called this turn. Does logging cause side effects upon make?
Nevertheless it tries to run "unix" tests via expect (seemingly 
successfully) while logging. Without logging all test runs break.

Possibly this affects DejaGNU testsuite only? Tomorrow I'll check what
happens in pass 2 gcc building.

Bernd





More information about the lfs-dev mailing list