The problem is happening with 18. I believe there is no issue with 17, because the last large bunch of my work was based off a pull *after* 17, and it has been installing fine; so the offending change has to be somewhere between 17 and 18; but I'll go double-check 17.
On Wed, 21 Apr 2010 17:59:43 -0400, Boris Shingarov wrote: Must be something else. > I upgraded texinfo (and related packages) from 4.11.dfsg.1-4 (which it > is in lilybuntu) to 4.13a.dfsg.1-4ubuntu1, it diesn't make a difference. > Doing lilypond version dichotomy now. > > On Wed, 21 Apr 2010 14:00:29 -0700, Patrick McCarty wrote: > On Wed, Apr 21, 2010 at 1:44 PM, Graham Percival > > <gra...@percival-music.ca> wrote: > > > On Wed, Apr 21, 2010 at 04:19:37PM -0400, Boris Shingarov wrote: > > >> 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. > > > > Graham, > > > > FWIW, I just did a clean build, testing `make install' and `make doc' > > too, and I did not run into any build failures. > > > > I have texinfo 4.13a installed on my machine. > > > > Thanks, > > Patrick > > > > > > > > > _______________________________________________ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel > > _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel