On Sat, May 13, 2006 at 10:41:18PM +0200, [EMAIL PROTECTED] wrote: > i meen i found the right log-file in: > > gcc-build/x86_64-unknown-linux-gnu/libmudflap/config.log > . > . > configure:2292: checking for C compiler default output file name > configure:2295: /mnt/lfs/sources/gcc-build/./gcc/xgcc > -B/mnt/lfs/sources/gcc-build/./gcc/ -B/cross- > tools/x86_64-unknown-linux-gnu/bin/ > -B/cross-tools/x86_64-unknown-linux-gnu/lib/ -isystem /cross-to > ols/x86_64-unknown-linux-gnu/include -isystem > /cross-tools/x86_64-unknown-linux-gnu/sys-include -O2 > -g -O2 conftest.c >&5 > /cross-tools/bin/x86_64-unknown-linux-gnu-ld: crt1.o: No such file: No > such file or directory > collect2: ld returned 1 exit status > configure:2298: $? = 1
Strange. At this point you have only installed the headers and cross-binutils, but gcc is failing because the tests for libmudflap try to use the cross- version of ld. That clearly cannot work in the static gcc. I've only built pure64 from an older pure64 recently, but I've built ppc and ppc64 from x86 so I feel fairly confident that our instructions will work. I'm looking again at my logs - the static gcc doesn't show any references to mudflap except tree-mudflap.o, but the final gcc shows it configuring in libmudflap and then compiling various mf-*.c files linked against libmudflap. I think somewhere you have deviated from the book, either by putting something wrong into the build variables LFS_HOST and LFS_TARGET, or perhaps by omitting one of the patches or seds for gcc. Also, what is your host's processor and distro ? I assume you are running an x86_64 as 32-bit, the i486 reference in your initial post makes me wonder if the distro is old. Ken -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://ninja.linux-phreak.biz/mailman/listinfo/clfs-support
