Hi, Sorry for the delay.
On 2010-11-04, Julien Rioux wrote: > On 04/11/2010 7:34 PM, Patrick McCarty wrote: > >Are you compiling LilyPond from scratch > > by the way for my builds initially I did > > git clone git://git.sv.gnu.org/lilypond.git lilypond > ./autogen.sh > ./configure.sh > make > sudo make install You don't need the ./configure in there, since ./autogen.sh automatically invokes the configure script. But it doesn't hurt to run the script twice :) > Since then I have been doing > > git pull > make > sudo make install > > I suppose I don't need to make clean each time I pull? Or should I? Sometimes I find that a `make' doesn't catch all of the changes to python scripts (e.g. lilypond-book), so I would do a `make clean' or `make bin-clean' just to be safe. The bin-clean target doesn't clean the font build directory, so this saves some compilation time. If you want to start again with a pristine git checkout (I don't know if this is in the Contributor's Guide yet), the following command sequence usually works for me. make doc-clean make distclean git clean -f -x Then proceed with ./autogen.sh , etc. to rebuild. Let me know if you still have problems after trying this. Thanks, Patrick _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
