Mailinglist Archive: opensuse-ppc (23 mails)
| < Previous | Next > |
Re: [suse-ppc] glibc TLS (Thread-Local Storage) support is not available on SLES10-rc1 PPC
- From: Olaf Hering <olh@xxxxxxx>
- Date: Mon, 10 Jul 2006 08:39:13 +0200
- Message-id: <20060710063913.GA1497@xxxxxxx>
On Mon, Jun 19, Tony Reix wrote:
> When compiling the glibc on ppc64 (Power5) (SLES9 or SLES10), TLS
> (Thread-Local Storage) support is not available. (See details below).
>
> Can you help understanding the problem ?
> When being in the directory where are the source code of the glibc.
> Example here below: 2.4
> (Same problem with 2.3.4 and 2.3.6 .)
>
>
> $ ./configure --enable-add-ons=nptl --with-tls --with-__thread
> ....
> checking for powerpc64 TLS support... no
configure uses uname -m to make assumptions about what code gcc will
generate. But this kind of guessing does not work on ppc and sparc because
the gcc defaults to 32bit output.
Either use 'powerpc32 ./configure ...' to fool configure and build a
32bit glibc.
Or use 'CC='gcc -m64 ./configure ...' to tell gcc to generate 64bit
code. You will need some of the -devel-64bit.rpm packages for 64bit
libraries.
> When compiling the glibc on ppc64 (Power5) (SLES9 or SLES10), TLS
> (Thread-Local Storage) support is not available. (See details below).
>
> Can you help understanding the problem ?
> When being in the directory where are the source code of the glibc.
> Example here below: 2.4
> (Same problem with 2.3.4 and 2.3.6 .)
>
>
> $ ./configure --enable-add-ons=nptl --with-tls --with-__thread
> ....
> checking for powerpc64 TLS support... no
configure uses uname -m to make assumptions about what code gcc will
generate. But this kind of guessing does not work on ppc and sparc because
the gcc defaults to 32bit output.
Either use 'powerpc32 ./configure ...' to fool configure and build a
32bit glibc.
Or use 'CC='gcc -m64 ./configure ...' to tell gcc to generate 64bit
code. You will need some of the -devel-64bit.rpm packages for 64bit
libraries.
| < Previous | Next > |