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 sysdeps/sparc/sparc64/dl-machine.h, and > therefore so no binary linked against 64-bit libc can execute. > > Not even "/lib64/libc.so.6 --version" will work, it will fail > because the dynamic linker doesn't understand the TLS relocations > present in the /libc64/libc.so.64 binary. > > If this sparc TLS support has been backported, this back has missed > significant chunks of the necessary changes and now all 64-bit > binaries fail to execute on the system.
This is a known problem. It was _not_ backported; rather, binutils was updated to one which supported sparc64 TLS, and glibc's configury automatically started enabling it. An upload to fix this has been waiting on a pile of failures to build, also because of the new binutils. Sorry. > I would suggest trying to execute a "Hello World" program, post-build, > to avoid major errors like this. There is no way that any of the > testsuite executed properly. Perhaps it was "built" successfully, but > none of the programs linking against libc could have executed properly > due to this bug. We run the testsuite. Sparc64 is a special case, however, because we can't assume that the buildd can run sparc64 binaries - in practice it can, of course, I'm sure we could do better than we do. -- Daniel Jacobowitz CodeSourcery, LLC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
