Trouble installing glibc-2.7 on Fedora 2.6.21-1.3194
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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
* 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).
I learned by private correspondence that the build problem you describe was fixed by adding to my configuration the specification CFLAGS=" -march=i686 -O2" It is necessary to specify the architecture (whatever yours is) in configuring recent versions of glibc. As I recall, it's needed for versions 2.6 and later. I think you also need to specify a level of optimization in the CFLAGS. At least it doesn't hurt to use -O2, the gcc default. All the other comments in response to your question seem to be irrelevant.
Please note, your reported problem is in building glibc, not installing it. There are other problems with switching out basic system software and keeping things working. Commands like cd failed with errors after I tried installing on a test system. Don't install until you really really know how to do it. Good luck.
Originally Posted by im4linux
I am installing glibc on my Fedora box. I have downloaded and untarred the glibc-2.7 tarball, untarred, created a compile subdirectory and run ../configure --prefix=/usr.
I get no error messages from the above.
When I run make however, I get stopped near the end (I assume) of the compile with the error: