Lilypond has built successfully now so I'm going to go ahead and close
this bug.
https://launchpad.net/ubuntu/+source/lilypond/2.16.0-1~exp+2
** Changed in: lilypond (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I would guess at a resource problem as well. The log indicates that
LilyPond is run with -djob-count=8, meaning that it will fork into 8
copies for building documentation. That is excessive if you are
building with limited memory, like in a virtual machine.
--
You received this bug notification
>From my duplicate bug 1017390 (which, due to a temporal shift error, was
reported ten days earlier):
“The failing build logs all show lilypond exiting with signal 11 for no
apparent reason. I’m guessing this indicates that it hit the build
servers’ memory limit. The lilypond package builds fine o
** Attachment added: "amd64 build log"
https://bugs.launchpad.net/bugs/1021570/+attachment/3214637/+files/buildlog_ubuntu-quantal-amd64.lilypond_2.14.2-3_FAILEDTOBUILD.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
