Don Armstrong wrote:
severity 678604 important
umm, armhf is now a release architecture and lilypond has built there in the past by my reading of the rc policy that makes this rc.
The problem is that metafont segfaults on armhf. This looks to be some odd kind of architecture specific problem in armhf's malloc, which I've asked for assistance with on debian-arm, but have received none.[1]
hmm, unfortunately i'm not an expert on either libc internals or tex stuff :(
Have you tried building metafont without optimisation and/or in arm mode ( -marm ) if so did it make any difference?
Finally, please don't post the entire build log to the BTS. It's easily available from the buildd webpage (and in this case, is totally uniformative.)
What I posted was not a complete build-log it was the diff between a succesful log from armel and a failed log from armhf.
1: http://lists.debian.org/debian-arm/2012/05/msg00102.html
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
