Am Thursday, 22. September 2011, 09:58:05 schrieb David Kastrup: > Reinhold Kainhofer <reinh...@kainhofer.com> writes: > > I only get such a problem if I call "make -j3" (or something other > > >1). I have never experienced it with "make", so my guess would be > > that the dependencies of our texinfo files are not complete. > > That would probably mean that one make process determines that a > dependency is available and up to date and proceeds on this assumption, > and then another make process removes that file as a sideeffect of > building a different target before the first make process has finished > working with the file.
Exactly. Make copies the *.texi file from the source to the build dir, runs extract-texi-filenames.py and then removes it again... I haven't looked into which stepmake snippet has these rules, but that's what I understand from the output of make. Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
