On 15/10/08 at 04:16 -0400, Michael Casadevall wrote: > Working with lucas, I've successfully been able to build ruby1.9. The > issue is related to NPTL support in the kernel. NPTL on HPPA is > extremely unstable it seems, and currently causes anything that uses > to threads to go boom under some cirmstances. Some versions of the > kernel however appear to work. I had a successful build with a machine > with the following uname > > Linux gsyprf11 2.6.22.19 #1 SMP Sat Apr 5 18:55:33 PDT 2008 parisc64 GNU/Linux > > The test suite passes successfully, although it does take an extremely > long time to build. cpuinfo is as follows: > > processor : 0 > cpu family : PA-RISC 2.0 > cpu : PA8700 (PCX-W2) > cpu MHz : 750.000000 > model : 9000/800/A500-7X > model name : Crescendo 750 W2 > hversion : 0x00005e30 > sversion : 0x00000491 > I-cache : 768 KB > D-cache : 1536 KB (WB, direct mapped) > ITLB entries : 240 > DTLB entries : 240 - shared with ITLB > bogomips : 1495.04 > software id : 824930630 > > processor : 1 > cpu family : PA-RISC 2.0 > cpu : PA8700 (PCX-W2) > cpu MHz : 750.000000 > model : 9000/800/A500-7X > model name : Crescendo 750 W2 > hversion : 0x00005e30 > sversion : 0x00000491 > I-cache : 768 KB > D-cache : 1536 KB (WB, direct mapped) > ITLB entries : 240 > DTLB entries : 240 - shared with ITLB > bogomips : 1495.04 > software id : 824930630 > > I uploaded the results to ~ncommander-guest/ruby1.9 on alioth. The > 219kb build.log is available. Built with debuild -B -b > Michael
Following Michael's steps, I successfully built ruby1.9 on mkhppa3, one of Thibaut Varene's boxes, using the following kernel: Linux mkhppa3 2.6.22.19 #1 SMP Tue Oct 14 14:22:05 CEST 2008 parisc64 GNU/Linux Before that, I tried to build using lenny's 2.6.26. I ran into several WARN_ON()s and hard locks, and never managed to build ruby1.9 on hppa using lenny's kernel. This kernel is clearly not ready for a release, but it's not my call to make... After the build, ruby's test suite mostly passed (some thread tests just blocked, so there's still a problem with threading on hppa). So I had to disable it in debian/rules. I think that the status is "good enough" for lenny/hppa. And this should allow to build the other missing packages too. Dato, is it fine if I upload those binaries to unstable? How should I proceed to make them migrate to testing? I think they will magically appear in testing since the source is already in testing, but I'm not sure now. Thanks a lot to Michael for hinting about 2.6.22.19 :-) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
