On Wed, Feb 15, 2012 at 4:18 PM, Phil Holmes <[email protected]> wrote: > ----- Original Message ----- From: "Reinhold Kainhofer" > <[email protected]> > To: "Julien Rioux" <[email protected]> > Cc: <[email protected]> > Sent: Wednesday, February 15, 2012 3:11 PM > Subject: Re: Fw: GDP Docs compilation FAILED (2012.02.14-01:39) > > > >> On 14/02/2012 15:48, Julien Rioux wrote: >>> >>> Reinhold Kainhofer <reinhold <at> kainhofer.com> writes: >>>>> >>>>> Dissecting... >>>>> Converting MusicXML file `./out-www/suffix-lyxml.xml'... >>>>> >>>>> lilypond-book.py: error: `musicxml2ly --out=- - ' failed (0) >>>>> lilypond-book.py: error: The error log is as follows: >>>>> musicxml2ly: Reading MusicXML from Standard input ... >>> >>> I've pushed a potential fix to staging. >> >> >> The cronjob successfully finished last night. >> >> Cheers, >> Reinhold > > >
Great! > FWIW, make, make doc on master shouldn't be afflicted with problems in a > multi-cpu environment, because currently most of the pushes from staging to > master are done on my 4 CPU/hyperthreaded machine - effectively 8 CPUs. I > know David also does some pushes, but I believe he's also now running a > multi-CPU build. > > -- > Phil Holmes > > In this case it was a dblatex-less environment that broke it: The problem did not occur on systems that have dblatex installed. The `ifeq' conditions in make/lilypond-book-vars.make are the source of the differing behavior. There are more conditionals in the Makefiles like this, unfortunately, and it is not feasible to test all possible build environments. Regards, Julien _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
