Re: [Lilypond-auto] Issue 4371 in lilypond: examples need explicit \relative c'' {} to copy and paste correctly

[lilypond]

Comment #18 on issue 4371 by address@hidden: examples need explicit \relative  
c'' {} to copy and paste correctly
https://code.google.com/p/lilypond/issues/detail?id=4371

To add to comment #17: it may indeed be caused by Keith's patch if the  
change of the snippet causes its snippet hash to change, letting it be  
processed earlier than before at a time where a parallel make thread has  
not yet delivered example.eps.  Now 34/lily-293eccba.ly is not awfully  
early in the alphabet, but on your multi-processor setup, it might end up  
early in the list for _one_ processor.

And indeed, the log file extract
Forking into jobs:  (20535 20534 20533 20532 20531 20530 20529)
logfile lilypond-multi-run-2.log (exit 1):
lily-2051c1e0-systems.tex...
Writing ./d9/lily-2051c1e0-systems.count...
Processing `./34/lily-293eccba.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
fatal error: cannot find file: `./context-example.eps' (load path:  
`/home/jlowe/
lilypond-git/build/out/share/lilypond/current/fonts/svg/:/home/jlowe/lilypond-gi

would indicate that exactly this is happening.  You could probably fix it  
by changing _any_ character in the snippet, giving it a different hash code.

But it would seem better to change the dependencies such that the snippets  
will not get compiled before the copying of context-example.eps has  
happened.  Or, probably easier, make sure that the Documentation/pictures  
source directory is in the search path for compiling snippets, making it  
unnecessary to copy the file at all.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings