Compiling and installing glibc [/lib/tls/libc.so.6]
 

Hi,
I have a server running Redhat EL 4.x.
I am using ACE library for system related functionalities. To support one specific requirement I made change in libc.
The ACE library uses the /lib/tls/libc.so.6.

Now I have to compile and install that libc.so.6 under /lib/tls/.

I came to know that the libraries under /lib/tls are build with NPTL support.
So, need clarification on how to compile and install the libc under /lib/tls/.

I downloaded the glibc version 2.3.4 (need changes on top of this version).
Configured the source and build directories.


../configure --prefix=/usr/test-libc --enable-add-ons=nptl ----is this the correct one?
And also please tell me how to install the library under /lib/tls/

Thanks for your time and help.

-Naresh.

The installed glibc-2.3.4 is compiled '--with-tls'
and with NTPL. AFAIK.
Please have a look into glibc.spec ( line 9 + 11 )
in the source package glibc-2.3.4-2.43.src.rpm

EDIT : The files, you are missing, are in the package
glibc-2.3.4-2.43.i686.rpm

Just install that, and you have /lib/tls/libc* etc. etc.
.....

Thanks for the reply.
But my problem is building and installing the libc.

I have the files /lib/tls/libc*.

What I want is,
I have some changes to do in the source files of libc.
And now I need to build the library libc and install the same.

Thanks for your time and help.

building and installing a DIFFERENT libc than the rest of the OS is built on ?
-- this can be done , but it is not advised .

Correct me if I am wrong.
As this is library, installing different one and using that to build new applications is a legal thing.
If things are done properly that should not harm the os.

After building glibc sources do I need to copy libc.so.6 on to the system or the new libc-2.xx.x inside the /lib folder?

You probably want to install the new library in a completely separate space. New applications linked against it will use it, while allowing existing applications to use the existing library. The potentially negative implications of getting something wrong in overwriting the system-wide libc would be scarey in the extreme, to me.
--- rod.