> Unless someone is going to make a concerted and dedicated development
> effort to do the necessary full analysis and backport all of the
> necessary changes, I would suggest to simply not enable TLS for the
> sparc64 glibc build at this time so at least we have something which
> works.
That work
From: Clint Adams <[EMAIL PROTECTED]>
Date: Sun, 11 Dec 2005 17:41:55 -0500
> Replacing Aurelien's patch with this one fixes the
> /lib64/libc.so.6: error while loading shared libraries: unexpected reloc type
> 0x4f
> problem, and "/lib64/libc.so.6 --version" works fine.
>
> However, 64-bit bina
On Wed, Nov 30, 2005 at 08:14:43PM -0800, David S. Miller wrote:
> Package: libc6-sparc64
> Version: 2.3.5-8
> Severity: normal
>
> There are some critical things missing in the sparc64 TLS support code
> in the current debian glibc tree, for example none of the TLS
> relcation support is in sysde
> There are some critical things missing in the sparc64 TLS support code
> in the current debian glibc tree, for example none of the TLS
> relcation support is in sysdeps/sparc/sparc64/dl-machine.h, and
> therefore so no binary linked against 64-bit libc can execute.
>
> Not even "/lib64/libc.so.6
Package: libc6-sparc64
Version: 2.3.5-8
Severity: normal
There are some critical things missing in the sparc64 TLS support code
in the current debian glibc tree, for example none of the TLS
relcation support is in sysdeps/sparc/sparc64/dl-machine.h, and
therefore so no binary linked against 64-bit
5 matches
Mail list logo
