On Sun, May 21, 2006 at 03:42:47PM +0000, Aurelien Jarno wrote: > > Is > >there any chance, that the old compatibility will be restored? I also > >read this in the mentioned BTS entry: > > > >"Well since glibc 2.3.6-7, all our "flavours" of the glibc now have TLS > >enabled, since it is needed by libstdc++. So I doubt it will work." > > > >Is there any way to disable TLS before running problematic programs? > > Disabling TLS will render our system unusable, as it would make your > system unable to run C++ programs (which include for example apt).
See my earlier message (for #368022) for an alternative. I also want to correct this statement. I've identified the problematic case. It only happens because: 1. perl is dynamically linked to libpthread.so 2. perl is not linked to libstdc++.so 3. a perl module dynamically loads libstdc++.so later The problem case is "the threads library has already been loaded, but no library using TLS has been loaded, when someone tries to dlopen a library with TLS" - much rarer than what you describe. -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
