Thanks, Ken. It is the most recent 'book' [?]
It appears I was missing the symlink to /tools. Corrected that and used a fresh untar of gcc and it worked correctly. Thanks for pointing out the areas to check!!! Much appreciated. Phil. ________________________________ From: lfs-support <[email protected]> on behalf of [email protected] <[email protected]> Sent: Tuesday, July 18, 2017 2:00:01 PM To: [email protected] Subject: lfs-support Digest, Vol 761, Issue 1 Send lfs-support mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.linuxfromscratch.org/listinfo/lfs-support or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of lfs-support digest..." Today's Topics: 1. Issue building first pass of GCC (Phil Rigby) 2. Re: Issue building first pass of GCC (Ken Moffat) ---------------------------------------------------------------------- Message: 1 Date: Mon, 17 Jul 2017 20:40:35 +0000 From: Phil Rigby <[email protected]> To: "[email protected]" <[email protected]> Subject: [lfs-support] Issue building first pass of GCC Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" Hi everyone, trying to build a LFS system for the first time, followed the handbook up to the point of GCC, running the "make" and getting this: ... ... ... else \ set -e; for ml in `cat fixinc_list`; do \ sysroot_headers_suffix=`echo ${ml} | sed -e 's/;.*$//'`; \ multi_dir=`echo ${ml} | sed -e 's/^[^;]*;//'`; \ fix_dir=include-fixed${multi_dir}; \ if ! true && test ! -d `echo /mnt/lfs${sysroot_headers_suffix}/mnt=/lfs/tools/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`; then \ echo The directory that should contain system headers does not exist: >&2 ; \ echo " `echo /mnt/lfs${sysroot_headers_suffix}/mnt=/lfs/tools/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`" >&2 ; \ tooldir_sysinc=`echo "/mnt/lfs/tools/lib/gcc/x86_64-lfs-linux-gnu/6.3.0/../../../../x86_64-lfs-linux-gnu/sys-include" | sed -e :a -e "s,[^/]*/\.\.\/,," -e ta`; \ if test "x`echo /mnt/lfs${sysroot_headers_suffix}/mnt=/lfs/tools/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`" = "x${tooldir_sysinc}"; \ then sleep 1; else exit 1; fi; \ fi; \ /bin/sh ../../gcc/../mkinstalldirs ${fix_dir}; \ chmod a+rx ${fix_dir} || true; \ (TARGET_MACHINE='x86_64-lfs-linux-gnu'; srcdir=`cd ../../gcc; ${PWDCMD-pwd}`; \ SHELL='/bin/sh'; MACRO_LIST=`${PWDCMD-pwd}`/macro_list ; \ gcc_dir=`${PWDCMD-pwd}` ; \ export TARGET_MACHINE srcdir SHELL MACRO_LIST && \ cd ../build-x86_64-pc-linux-gnu/fixincludes && \ /bin/sh ./fixinc.sh "${gcc_dir}/${fix_dir}" \ `echo /mnt/lfs${sysroot_headers_suffix}/mnt=/lfs/tools/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta` ); \ rm -f ${fix_dir}/syslimits.h; \ if [ -f ${fix_dir}/limits.h ]; then \ mv ${fix_dir}/limits.h ${fix_dir}/syslimits.h; \ else \ cp ../../gcc/gsyslimits.h ${fix_dir}/syslimits.h; \ fi; \ chmod a+r ${fix_dir}/syslimits.h; \ done; \ fi make[3]: Entering directory '/mnt/lfs/sources/gcc-6.3.0/build/prev-gcc' make[3]: *** No rule to make target 'real-install-headers-tar'. Stop. make[3]: Leaving directory '/mnt/lfs/sources/gcc-6.3.0/build/prev-gcc' make[2]: *** [Makefile:2909: stmp-fixinc] Error 2 make[2]: Leaving directory '/mnt/lfs/sources/gcc-6.3.0/build/gcc' make[1]: *** [Makefile:4119: all-gcc] Error 2 make[1]: Leaving directory '/mnt/lfs/sources/gcc-6.3.0/build' make: *** [Makefile:864: all] Error 2 Googling doesn't help with any possible resolutions and I've tried this a few times by changing the ./configure parameters and it hasn't made any difference... can anyone assist? Thanks! Phil. (If it helps, I'm using Gentoo as the host Linux environment to build the LFS.) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfromscratch.org/pipermail/lfs-support/attachments/20170717/aa90324f/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 17 Jul 2017 22:54:13 +0100 From: Ken Moffat <[email protected]> To: LFS Support List <[email protected]> Subject: Re: [lfs-support] Issue building first pass of GCC Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 On Mon, Jul 17, 2017 at 08:40:35PM +0000, Phil Rigby wrote: > Hi everyone, trying to build a LFS system for the first time, followed the > handbook up to the point of GCC, running the "make" and getting this: Hi Phil, it might help if you mention which version of the book you are using (I'll assume 8.0), although this error is so uncommon that I suspect you have done something wrong. Also, we normally jsut call it the book - to me 'the handbook' sounds very BSD-ish : nothing wrong with that, but our books are only ever a snapshot of what we thought was good at the time. > > > ... > > ... > > ... > I wonder if the initial error was somewhere before this ? One of the matches google found was caused by omitting libgmp.la, libmpfr.la, libmpc.la - see version-check.sh and library-check.sh at the bottom of section 2.2. > else \ > set -e; for ml in `cat fixinc_list`; do \ > sysroot_headers_suffix=`echo ${ml} | sed -e 's/;.*$//'`; \ > multi_dir=`echo ${ml} | sed -e 's/^[^;]*;//'`; \ > fix_dir=include-fixed${multi_dir}; \ > if ! true && test ! -d `echo > /mnt/lfs${sysroot_headers_suffix}/mnt=/lfs/tools/include | sed -e :a -e > 's,[^/]*/\.\.\/,,' -e ta`; then \ > echo The directory that should contain system headers does not exist: > >&2 ; \ This part looked worrying to me, but only because I don't read my logs line-by-line if I don't need to :) > echo " `echo /mnt/lfs${sysroot_headers_suffix}/mnt=/lfs/tools/include > | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`" >&2 ; \ BUT, I see that mine (in 8.0, gcc-6.3.0) was slightly different: if ! true && test ! -d `echo /mnt/lfs${sysroot_headers_suffix}/tools/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`; then \ echo The directory that should contain system headers does not exist: >&2 ; \ Specifically, mine echoes /mnt/lfs${sysroot_headers_suffix}/tools/include but yours echoed /mnt/lfs${sysroot_headers_suffix}/mnt=/lfs/tools/include I would expect sysroot_headers_suffix to not be set at this stage, so mine just references /mnt/lfs/tools/include, but yours is trying to reference /mnt/lfs/mnt=/lfs/tools/include : that looks like garbage somewhere in the configure options. Or perhaps a typo. I can understand why you try to change things to fix it yourself, but for LFS itself, particularly on released versions of the book, the instructions in the book should be good enough to get it to build. When you have succeeded once in doing it by the book, and if you then use parts of BLFS, it is of course fine to try changing the instructions - with my usual comment that if it breaks you get to keep both pieces. [...] > make[3]: Entering directory '/mnt/lfs/sources/gcc-6.3.0/build/prev-gcc' > make[3]: *** No rule to make target 'real-install-headers-tar'. Stop. I suspect that when things go wrong, the build often falls through until it tries to make that target. So other errors, such as what I mentioned at the start, might also end with that same error message. But running the checks on the host system requirements is still important, it can save a lot of broken partial builds. Summary: Please check the host system requirements, just in case. Then check you have set the variables correctly (4.4, 5.3). then, using freshly untarred source, retry gcc pass 1 (or start over if some of your variables were wrongly set). ?en -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment ------------------------------ Subject: Digest Footer -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page ------------------------------ End of lfs-support Digest, Vol 761, Issue 1 *******************************************
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
