Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ch. 6.14 was Installing glibc-2.3.1.
Ch. 6.63 is also Installing glibc-2.3.1.
Ok, is this an instance where I should delete my previous /packages/temp6/glibc-build directory and recreate it to re-build from the glibc-2.3.1 directory? Maybe I need to do a rm -rf /packages/temp6/glibc*. And completely start over for the glibc part there.
I assume that some of the files in the glibc directories were modified back in 6.14, and need to be purged before doing the ./configure, make, and make install again from 6.63.
Or, are the files that are now in those directories needed for this new ./configure, etc...?
Yes, I would remove your glibc build directory from the previous compile (6.14).
The reason you compile it twice is a safeguard. It makes sure that glibc is built as the developers intended it to be; without the patch you applied earlier. That ALSO means you need to delete you glibc source tree. When you applied the patch, your source files were modified. So if you simply built it from another build directory, you'd still be including the patch, which is NOT what you want.
So, kill both glibc-build, and the glibc source tree. Or, at the very least, extract and compile the source in a different directory.
Ok. Dang. It's ok if anybody wants to beat me over the head with a heavy RTFM.
The text of the book says basically exactly what Dark Helmet said:
Quote:
At the beginning of this chapter you installed Glibc and applied a patch to it. Part of this patch was undoing some changes to make static binaries compiled against Glibc-2.2 work. However, this is not what the Glibc developers intended and we don't need to keep this modified Glibc around. So we reinstall Glibc here to remove this patch.
A second reason to install Glibc again is because it's considered cleaner. The first Glibc was installed using programs compiled on your host distribution which sometimes has the effect of tainting Glibc. While this isn't a problem with the other packages compiled early in this chapter, for Glibc we want to be sure it's 100% OK
Nah.... you're doing fine. The book moves at a pretty steady pace, and after a while, you begin to typing the commands without fully reading the text (at least that's how I was/am).
You're almost finished though! It's just the kernel that's left. That can be daunting, but it's definitely do-able.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.