> Paul, > > AFAICS the commands for the Linux API headers in 7.7 were: > > make mrproper > make INSTALL_HDR_PATH=dest headers_install > >followed by a find command and then a cp >Which of these gives you an ld error ? > >ĸen
Thanks for responding, Ken. Your mind hasn't already tied itself in Gordian Knots. ;-) Here's what I get; it's the CH5/Stage1 gcc that croaks (as I mentioned in the original posting about trying to compile a dummy.c). I expect my email client will word-wrap this--Sorry!: CLEAN include/generated CLEAN include/generated/uapi/linux/version.h CHK include/generated/uapi/linux/version.h UPD include/generated/uapi/linux/version.h HOSTCC scripts/basic/fixdep /tools/lib/gcc/i686-pc-linux-gnu/4.9.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory /tools/lib/gcc/i686-pc-linux-gnu/4.9.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find crti.o: No such file or directory collect2: error: ld returned 1 exit status make[1]: *** [scripts/basic/fixdep] Error 1 scripts/Makefile.host:91: recipe for target 'scripts/basic/fixdep' failed make: *** [scripts_basic] Error 2 Makefile:451: recipe for target 'scripts_basic' failed I think the fixdep makefile is innocent. It's the Stage1 gcc. ld isn't finding crt1.o, but as shown previously it's in /tools/lib, and ld knows to look there. All that's happened is the FHS is built and the temporary symlinks are in. There's not that much there yet to confuddle things! But don't let me lead you down the path that confuses me. Apologies to all, this should be in the LFS mailing list. Just noticed. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - Choose from over 50 domains or use your own -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
