I ran the build again after fixing /bin/sh to be a link to /bin/bash. I formatted the lfs partition and re-downloaded the sources before running the build again, but it occurred to me after the fact that I didn't delete the lfs programs from /tools/bin. So maybe that was dumb.
I did get the same error about x86_64_linux-gnu-ranlib, however. I guess the proper next step is to try to use the lfs livecd environment instead of my normal desktop. Before I do that I will probably try removing the installed programs and rebuilding again, but if it still runs up to the same error I dunno what else I could try short of switching to a known clean environment. Here's the host system requirements script that I ran before the most recent attempt, where the installation of Libstdc++-4.81 failed on make install with .... x86_64-lfs-linux-gnu-ranlib: command not found despite $PATH being /tools/bin:/bin:/usr/bin and /tools/bin containing x86-64-lfs-linux-gnu-ranlib. :~$ version-check.sh bash, version 4.2.45(1)-release /bin/sh -> /bin/bash Binutils: (GNU Binutils for Ubuntu) 2.23.2 bison (GNU Bison) 2.5 /usr/bin/yacc -> /usr/bin/bison.yacc bzip2, Version 1.0.6, 6-Sept-2010. Coreutils: 8.20 diff (GNU diffutils) 3.2 find (GNU findutils) 4.4.2 GNU Awk 4.0.1 /usr/bin/awk -> /usr/bin/gawk gcc (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3 g++ (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3 (GNU libc) 2.18 grep (GNU grep) 2.14 gzip 1.5 Linux version 3.8.0-23-generic (buildd@batsu) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013 m4 (GNU M4) 1.4.16 GNU Make 3.81 patch 2.6.1 Perl version='5.14.2'; GNU sed version 4.2.1 tar (GNU tar) 1.26 Texinfo: makeinfo (GNU texinfo) 4.13 xz (XZ Utils) 5.1.0alpha g++ compilation OK If I'm missing any obvious discrepancies, I apologize for bothering the mailing list. Since this problem is kind of weird and doesn't seem to have an immediate rational explanation, I was kind of hoping for some insights on why this might crop up, so I could fix it and add it as a little notch to my belt. :) I am still hoping that it is just caused by a simple error on my part, but I haven't been able to find one, yet. So yeah, if deleting the installed programs and rebuilding with fixed /bin/sh does not eliminate the error and no more useful data comes up, I'll just try the livecd. But I sure hope I get to find out what exactly is going wrong eventually... On Thu, Jan 16, 2014 at 8:32 PM, William Harrington <kb0...@berzerkula.org>wrote: > > On Jan 16, 2014, at 5:56 PM, Louis Rine wrote: > > > Ah, I was wondering if dash would make a difference. I will fix that > > and try again. Thank you. :) > > It does, and that is why the host system requirements states: > > Bash-3.2 (/bin/sh should be a symbolic or hard link to bash) > > But that may not be your only issue. > > I suggest you check the host system requirements. > > Sincerely, > > William Harrington > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page >
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
