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.
All information is a must, every time a new question is asked,
takes a lot of time to find it ... again.
________________________________________________________________
Glibc : This is crucial
Quote:
The following lines need to be added to 'config.cache'
for Glibc to support NPTL:
I'm not using LFS. But I am getting the same error while trying to build glibc-2.9 for Slackware. So I'm not sure where I'm supposed to add these two lines for this to work.
Quote:
The following lines need to be added to 'config.cache'
for Glibc to support NPTL:
Do I just add these to my SlackBuild for glibc? And if so, at what point should they be added? Before or after configure has been run? Or does this go before the patches are applied?
Thank you for this previous post!
Xavian-Anderson Macpherson
Shingoshi
Following the relevant page in CLFS, those commands would be executed after the patches are applied and before the configuration command from that page is executed (being sure to include the "--cache-file=config.cache" option as specified).
I'm not sure if these instructions will be equally valid for glibc-2.9, though. You're also probably better off asking about this in the Slackware forum, since Slackware's preferred build methods are likely to be at least somewhat different from those of (C)LFS. YMMV.
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,513
Rep:
@ Shingoshi
Why change glibc ? ? Please see the "Slackbook".
> > Somewhere in the Slackware documentation it is said that :
If you do a regular upgrade of 'glibc', ( with a Slackware
'glibc package' ), all other packages must be updated too !
Building glibc is quite tricky and has a number of pitfalls, not the least
of which include :
* Never install over a live system. The connection between the individual
parts of the glibc shared libraries is special. The libc.so shared library
uses private interfaces in ld.so and vice versa. On a live system with
dynamically linked applications if a new libc.so replaces an old one with a
different internal ABI your system will be broken. libpthread.so, libm.so, and
librt.so have similar problems. At a minimum, install into a separate chroot
environment.
* There is a high possibility you will end up creating a different public
ABI. If you were to begin distributing binaries they would at a minimum not
work, and at best create a lot of confusion.
If you find yourself needing to build a customised version of glibc, you are
best to use the framework offered by your distribution (i.e. the rpm or deb
package build facilities).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
