Hi Gianfranco, >> I am aware s390x is failing. I have been trying to port it, and it no longer >> segfaults (thanks to the pexport-endian.diff patch from upstream), but one >> part of the >build step (the compiler bootstrapping itself) exits with code >> 1, without printing anything. That’s on my list of things to talk to >> upstream about. > > I'm not sure I can help here... for sure you have to patch configure.ac, but > other than that some code might be needed swell.
There’s hardly any platform-specific code for the interpreter (i386/amd64 use
their own native code by default written in assembly). Looking at how poly gets
built, any uncaught exception in that build step gets caught and it exits
silently; my guess is an exception is being thrown somewhere.
>> x32 fails because there’s some hand-written assembly that isn’t aware of x32
>> (it assumes i386 and amd64 are the only two cases).
>
> ok
Getting a version that uses the interpreter should be fairly easy, but ideally
it would use almost all the same assembly as i386/amd64, which requires adding
another pre-built compiler. I don’t know what the bootstrap process is for
doing that, so that’s definitely another one for me to talk to upstream about.
>> Interestingly armel has failed a test case for floating-point (funnily
>> enough I had just that test failed when I was testing ppc64el and it turned
>> out to be a bug >in qemu!), so I’ll need to look into that. Previous uploads
>> weren’t running the tests as part of the build, so I don’t know if this is a
>> regression or not. armhf >has built successfully though...
>
> ok (I'll point you to a solution if possible)
I’m trying to set up a system in qemu; hopefully it’s reproducible there.
>> I’m currently a student, so one package is more than enough, although
>> certainly one day I would consider applying to be a Debian Maintainer.
>> Having said that, for a package in debian-science, there’s hardly any
>> inconvenience on my part.
>
> wonderful :)
>
> BTW you can apply as DM also if you want to maintain only one package,
> assuming you will in the future try to be more involved :)
Ok, I wasn’t sure whether it was encouraged for just one package. I certainly
need more experience though before applying.
mips{,el} have now built on the buildds, so it is just armel and s390x that are
the only failing release architectures.
Regards,
James
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
