lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: screech-and-boink.ly


From: David Kastrup
Subject: Re: screech-and-boink.ly
Date: Sat, 30 Jun 2012 17:29:20 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

David Kastrup <address@hidden> writes:

make clean all

again delivers

LILYPOND_VERSION=2.15.41 /usr/bin/python ../scripts/lilypond-book.py -I ./ -I 
./out -I ../input -I /usr/local/tmp/lilypond/Documentation -I 
/usr/local/tmp/lilypond/Documentation/snippets/out -I ../input/regression/ -I 
/usr/local/tmp/lilypond/Documentation/included/ -I 
/usr/local/tmp/lilypond/mf/out/ -I /usr/local/tmp/lilypond/mf/out/ -I 
/usr/local/tmp/lilypond/Documentation/pictures -I 
/usr/local/tmp/lilypond/Documentation/pictures/./out --process='true 
-dbackend=eps --formats=ps,png,pdf  -dinclude-eps-fonts -dgs-load-fonts 
--header=doctitle --header=doctitlecs --header=doctitlede --header=doctitlees 
--header=doctitlefr --header=doctitlehu --header=doctitleit --header=doctitleja 
--header=doctitlenl --header=doctitlezh --header=texidoc --header=texidoccs 
--header=texidocde --header=texidoces --header=texidocfr --header=texidochu 
--header=texidocit --header=texidocja --header=texidocnl --header=texidoczh 
-dcheck-internal-types -ddump-signatures -danti-alias-factor=2' --output=./out 
--format=texi --loglevel=WARN  --skip-lily-check --lily-output-dir 
/usr/local/tmp/lilypond/out/lybook-db --redirect-lilypond-output usage.tely
langdefs.py: warning: lilypond-doc gettext domain not found.
lilypond-book.py: error: file not found: screech-and-boink.ly

make[1]: *** [out/usage.texi] Error 1
make[1]: Leaving directory `/usr/local/tmp/lilypond/Documentation'
make: *** [all] Error 2

That's not pretty.  I start to suspect that some of the recent commits
introduced a "race condition" that is only _avoided_ by using a
multi-job make (like Patchy does).

I'll clean _and_ reconfigure now, and if that does not help, we have a
problem.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]