On Thu, Feb 10, 2011 at 10:57:36PM -0700, Colin Campbell wrote: > On 11-02-10 10:47 PM, James Lowe wrote: > >You need to run > > ../configure > >again, due to build system changes for new languages. It's /just/ > >possible that you might need to delete your build/ dir and start > >again, but running ../configure should be enough. > > > >--- > > > >Unfortunately it wasn't. > > > >I did also did a make clean ; make doc-clean and (even re-run configure) > >then started again, left it run overnight and it still failed..
Words of wisdom: don't ever try make clean make doc-clean it's a complete waste of time. If you ever suspect that "make clean" might help, then just save yourself the agony and nuke your build/ dir and start from fresh. > >Has anyone else actually done a clean doc/web build since all those > >translations were merged? I always nuke my build/ dir, and I never noticed the slightest problem. I've built the docs several times since then, including the 2.13.49, release candidate 2. > As it happens, I've been having all *sorts* of fun trying to get a > clean local build of the docs so I can finish off those patches of > Reinhold's. I can build lily both from gub and directly from the > command line in lilypond-git. > Make doc has so far choked every time > I've tried this week, even after nuking lilypond-git and the > .lilypond-fonts.cache-2. ? that's very odd. What kind of error message did you see? > I'm re-running a make doc after a sudo make install, make install has nothing to do with a doc build. There is absolutely no need for a lilypond contributor to run make install. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel