This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: glibc2.3.2, linux 2.4.18, and TLS
Justin,
Thanks for the information. Unfortunately, I need to get this to work
with glibc 2.3.2 because I need to install it on a system with a 2.4.18
kernel and no NPTL. When you said you'd gotten this working with "the
latest", I thought you meant "the latest 2.3.2" (which I was assuming
might have included patches that were released for 2.3.2).
I'm assuming I need to stick with 2.3.2 because a) NPTL was added to glibc
in 2.3.3, and b) my understanding is that NPTL-based glibc won't work with
a 2.4.18 kernel. I've read of patches to add NPTL support to "2.4
kernels", but haven't been able to find any such patch for 2.4.18.
Thanks,
Bryan
From:
"Justin P. Mattock" <justinmattock@gmail.com>
To:
Bryan Williams/Atlanta/IBM@IBMUS
Cc:
libc-help@sourceware.org
Date:
01/26/2010 06:29 PM
Subject:
Re: glibc2.3.2, linux 2.4.18, and TLS
Sent by:
libc-help-owner@sourceware.org
On 01/26/10 14:19, Bryan Williams wrote:
> First, please forgive the screwed-up format of my response... I'm using
a
> Notes client and can't get it to format my reply correctly.
>
> I just tried grabbing a copy of the 2.3.2 source from ftp.gnu.org and
> built it with the same configure command line I used before. When I try
> to use the compiled library, for example by doing an ls, I get the
error
> :
>
> ls: relocation error: /usr/local/tls/lib/libc.so.6: symbol
> __libc_stack_end, version GLIBC_PRIVATE not defined in file link time
> reference.
>
> In the version I built earlier using our local set of patches, the above
> error does not occur because one of the patches removes __libc_stack_end
> from the GLIBC_PRIVATE section of ld. In addition, the libraries I just
> built contain no tls_ symbols. Also, looking at the configure script,
it
> appears to me that the --with-t,ls option is a no-op -- it sets a
variable
> that is not referenced anywhere else in the script. Could you tell me
> what configure command line you're using, plus any environment variable
> settings? Also, can you confirm that the tls_ functions are actually
> present in the library you built?
>
> Thanks,
> Bryan
>
>
over here I built gnutls,
then used this to build libc:
CFLAGS="-m64 -mtune=core2 -march=core2 -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="${CFLAGS}" MAKEOPTS="{-j3}" ../glibc/configure --prefix=/usr
--disable-profile --enable-add-ons --enable-kernel=2.6.0
--libexecdir=/usr/lib/glibc --libdir=/usr/lib --with-selinux
--with-tls(or whatever the enable option is for tls)
keep in mind this is the latest: 2.11.90, not sure for 2.3.2
hope this helps.
Justin P. Mattock