[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: issues with nptl-only libc



On Wed, 10 Nov 2004, Andreas Jochens wrote:

On 04-Nov-10 12:24, Mattias Wadenstein wrote:
On Wed, 10 Nov 2004, Andreas Jochens wrote:

On 04-Nov-10 11:21, Mattias Wadenstein wrote:
Would it be hard to give legacy support for old-style linux threads? This
has turned up several times as a serious issue now..

Which packages are affected? There was a problem with mysql-dfsg which
has been resolved. If there are other packages which have problems,
I would rather like to fix those packages.

Running an amd64 chroot on a woody host system with a woody kernel.

An amd64 chroot will not work at all when you are running a woody kernel.
No woody kernel has amd64 support. You really need an amd64 kernel
to run amd64 binaries. Only 2.6 kernels have proper support for amd64.
AFAIK upstream did not backport any amd64 changes to the 2.4 kernel
series since a long time ago.

What I meant was a recompiled kernel close to the woody 2.4 one. In my experience, running woody on a 2.6 kernel is not very smooth. Yes, I know that for running a proper amd64 system, you want a 2.6 kernel. This doesn't always mesh well with reality though.

GotoBLAS is "Pthreads NOT NPTL", with NPTL being "work in progress" since
some time ago. I suspect this might go for several other pieces of
non-free software. This is a critical issue for us at work.

If you could describe your setup and the specific problems you have with it,
I will try to find a solution.

Just saying that we have to support running software that does not support NPTL, including building against binary-only libs.

Programs which have been compiled and linked for the use with
linuxthreads should usually also work with nptl at runtime. This is
exactly what happens on i386 if you run any 2.6 kernel. An i386
system uses the nptl thread library '/lib/tls/libpthread-0.60.so' if you
run a 2.6 kernel and the linuxthreads library '/lib/libpthread-0.10.so'
if you run a 2.4 kernel (with the same binaries).

Ok, so this should work then? I'll schedule an upgrade of a node to check it out.

The hard 2.6 kernel requirement does hurt though.

/Mattias Wadenstein



Reply to: