This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: linuxthreads releases
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Daniel Jacobowitz" <drow at false dot org>
- Cc: libc-ports at sourceware dot org
- Date: Sat, 7 Oct 2006 23:15:15 -0400
- Subject: Re: linuxthreads releases
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Cxf9Rt9Ow4H97ALy/VqQHx14x+fW3dp03KXlmKRByqCs7jluaBAHwErh1gGJWqlsZZCEWkW9jAze/rjmXrpQssddXdg+TzmxPdEXHP7qhpe2HD0q23tOYULQHRAnRAyMEiNClWEsd9nroyb8i0Y07M261UbusBl3eogBNZGCZt8=
- References: <200610061320.14858.vapier@gentoo.org> <20061006191621.GA11541@nevyn.them.org>
On 10/6/06, Daniel Jacobowitz <drow@false.org> wrote:
On Fri, Oct 06, 2006 at 01:20:14PM -0400, Mike Frysinger wrote:
> since there was no glibc-2.4 linuxthreads release, i assumed there werent
> going to be anymore ever ... are there any real plans for linuxthreads ? the
> 2.5 release of it makes me curious ...
> -mike
There was not a glibc 2.4 linuxthreads tarball due to some bad timing.
The timing was easier this time.
I hope we don't have to keep making LinuxThreads releases. Once HPPA
NPTL is ready (is it?) and someone has done an m68k port, I fully
intend to stop taking care of it. The BSD guys still use it; I don't
know what will come of that.
The HPPA NPTL port requires a number of patches to libc/nptl for S_G_U
cases which are not handled. After applying those patches I'm down to
the following set of failures:
make[2]: *** [/libc/math/test-double.out] Error 1
make[2]: *** [/libc/math/test-idouble.out] Error 1
make[1]: *** [math/tests] Error 2
make[2]: [/libc/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/libc/nptl/tst-cond17.out] Error 1
make[2]: *** [/libc/nptl/tst-cancel24] Error 1
make[2]: *** [/libc/nptl/tst-oddstacklimit.out] Error 139
make[2]: *** [/libc/nptl/tst-cancelx4.out] Error 1
make[2]: *** [/libc/nptl/tst-cancelx5.out] Error 1
make[2]: *** [/libc/nptl/tst-cancelx20.out] Error 1
make[2]: *** [/libc/nptl/tst-cancelx21.out] Error 1
make[2]: *** [/libc/nptl/tst-cleanupx4.out] Error 1
make[1]: *** [nptl/tests] Error 2
make[2]: *** [/libc/rt/tst-timer.out] Error 139
make[2]: *** [/libc/rt/tst-mqueue3.out] Error 1
make[2]: *** [/libc/rt/tst-timer4.out] Error 1
make[2]: *** [/libc/rt/tst-timer5.out] Error 1
make[2]: *** [/libc/rt/tst-cputimer1.out] Error 1
make[2]: *** [/libc/rt/tst-cputimer2.out] Error 1
make[2]: *** [/libc/rt/tst-cputimer3.out] Error 1
make[1]: *** [rt/tests] Error 2
make[2]: *** [/libc/elf/tst-pie1.out] Error 139
make[2]: *** [/libc/elf/tst-audit2.out] Error 139
make[2]: *** [/libc/elf/tst-addr1.out] Error 1
make[2]: *** [/libc/elf/check-textrel.out] Error 1
make[1]: *** [elf/tests] Error 2
make: *** [check] Error 2
The cancellation failures are nothing I know how to fix, and will
probably require some investigation. For example I get a lot of:
"cleanup handler not called for `foo`"
Where `foo` is some function like read for which a cleanup handler
should have been called.
Cheers,
Carlos.