On Wed, 24 Mar 2021 17:07:57 +0100 Patrick Frisch <patr...@frischux.de> wrote:
> Am 24.03.21 um 13:12 schrieb Scott Andrews: > > > > echo $LFS > > > > Looks like it wasn't set > > > > > > > > No, $LFS is set almost always to /mnt/lfs, as it was in this case, > but the cause for the error was found already. Point 1: If $LFS was set then the api headers could not have been installed on the host. Point 2: You were running the build under the root user or using sudo, and $LFS was unset otherwise the api headers could not have been installed on the host Point 3: If $LFS was set and the directory in /mnt/lfs was missing then the cp would have failed because the directories are not there Point 4: You are scripting the build and don't check for errors > > Do you have a reason why you have two real directories for /lib and > /lib64, on most systems I know they already symlinked the two, so > you don't have to make this strange empty link in the first place. > I don't have /lib64 on my host nor do I have on my build > And I remember, that I had some issues in the past, because gcc > searches some libs in /lib64 or vice versa. So I remember that I > did a LFS build with the two libs symlinked (ln -sf /lib /lib64), > so I didn't have to fiddle with single library linking, and it > worked :-) > > bye,P. > -- 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
