Re: hppa release status

[Pierre Habouzit <madcoder@debian.org>]

[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]

On Tue, Jun 10, 2008 at 09:44:55PM +0000, Helge Deller wrote:
> CC'ed: parisc-linux kernel development list
> 
> Andreas Barth wrote:
> >during the upload of python2.5, the build failed on hppa due to stalls
> >in the test suite, see http://bugs.debian.org/483042 and
> >http://buildd.debian.org/fetch.cgi?&pkg=python2.5&ver=2.5.2-5&arch=hppa&stamp=1211583145&file=log
> >(Matthias "fixed" that bug by disabling the testsuite, not something 
> >that makes
> >us happy.)
> >After that happened, we asked on #parisc if someone could take a look,
> >and we were told that linuxthreads is currently unmaintained for hppa,
> >and the issue could only be fixed by moving to nptl and we need to do an
> >(incompatible) abi change in glibc. Such a change would be really
> >unfortunate, and we hope that every other roads have been evaluated
> >first (like trying to understand why python on linuxthreads fails on
> >hppa but not on e.g. kfreebsd). We also would like to be sure that ntpl
> >is really better than linuxthreads for python2.5 before a transition.
> 
> My personal feeling is, that a switch to NPTL is probably the best
> solution. Even if this involves a abi change.
> Maybe experts on NPTL could comment here?

  The NPTL in glibc works well afaict, the downside is the ABI bump,
because doing the archive-wide rebuild as a 66% chance to hurt the port
so bad that it will not be ready in time for lenny. This is a last
resort measure, and everything _must_ be tried before, because even
"losing" a week trying to fix linuxthreads is way faster than rebuilding
the whole archive which is rather a matter of months and risking no HPPA
at all in the end.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]