On Sat, Jul 11, 2009 at 11:41 AM, Carlos O'Donell<[email protected]> wrote: > On Sat, Jul 11, 2009 at 11:01 AM, Luk Claes<[email protected]> wrote: >> Do you have an idea why petsc fails on hppa? It's one of the blockers of >> the petsc/openmpi/suitesparse transition. > > I'm sbuild-ing petsc, I'll tell you what I find.
I can reproduce this. I'm seeing the same failure as the autobuilder, and I've seen at least one python sigsegv (note that there is a discussion on linux-parisc about a bug in the kernel related to corrupting memory protection bits). I've enabled core dumps in the buildd chroot so I can examine crashes post-mortem. https://buildd.debian.org/fetch.cgi?&pkg=petsc&ver=3.0.0.dfsg-5.1&arch=hppa&stamp=1246867119&file=log ~~~ make[1]: Entering directory `/build/buildd/petsc-3.0.0.dfsg' /build/buildd/petsc-3.0.0.dfsg/conf/variables:118: /build/buildd/petsc-3.0.0.dfsg/linux-gnu-c-debug/conf/petscvariables: No such file or directory /build/buildd/petsc-3.0.0.dfsg/conf/rules:982: /build/buildd/petsc-3.0.0.dfsg/linux-gnu-c-debug/conf/petscrules: No such file or directory make[1]: *** No rule to make target `/build/buildd/petsc-3.0.0.dfsg/linux-gnu-c-debug/conf/petscrules'. Stop. make[1]: Leaving directory `/build/buildd/petsc-3.0.0.dfsg' make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ~~~ I'll build this by hand to inspect why it fails. Cheers, Carlos. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
