On Wed, Apr 21, 2010 at 04:19:37PM -0400, Boris Shingarov wrote: > Maybe that's just a missed dependency. It occurs on "make install" > after a successful "make all". The error message is this:
That's the same message that Francisco sent, which started this whole thing. > I wouldn't even care about this at all -- because I am not experiencing > this problem on my development machine -- if not the outcry of my users > who today can not use any of what I wrote in the past weeks. Well, we need somebody who sees those errors to do more investigation. Does the source for 2.13.18 work? If not, what about 2.13.17 ? If not, what about 2.13.16 ? etc. If we know what range of commits we need to examine, we have a better chance at finding the problem. I'm doing 1 hour of lilypond work a day. I suppose I could download lilybuntu and try to recreate the problem and do this investigation myself, but that would mean putting other lilypond things on hold, and I'm not willing to do that. I estimate that I would only get around to testing lilybuntu sometime next week. If this issue is more urgent to you -- anybody, not just Boris -- then please do these tests and give us a range of dates / commits when it failed. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel