Re: Make broken on master [fixed]

2009-07-29 Thread Werner LEMBERG
> I really hope I got it right in the commit I just pushed to master > and lilypond/translation. It works now, thanks. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make broken on master [fixed]

2009-07-29 Thread John Mandereau
Le mercredi 29 juillet 2009 à 21:15 +0200, Werner LEMBERG a écrit : > > > make -np &> make-db.log > > Attached. Thanks, it shows the same problem as Francisco. I really hope I got it right in the commit I just pushed to master and lilypond/translation. Sorry for the 4-days build breaking, John

Re: Make broken on master [fixed]

2009-07-29 Thread John Mandereau
Le mercredi 29 juillet 2009 à 20:23 +0200, John Mandereau a écrit : > This is exactly what the CHAIN_RULE trick in make/ly-*.make is supposed > to do: it generates rules that ensure no several lilypond-book instances > ever run simultaneously. ...and the generated rules chain must in particular sp

Re: Make broken on master [fixed]

2009-07-29 Thread John Mandereau
Le mercredi 29 juillet 2009 à 20:26 +0200, Francisco Vila a écrit : > Besides, Why 'make' should bother about tely files? Isn't it supposed > to make the binary only? It builds Info documentation without images, which is a least a useful validation test for documentation in English, as makeinfo er

Re: Make broken on master [fixed]

2009-07-29 Thread Francisco Vila
2009/7/29 John Mandereau : > make -np &> make-db.log http://www.paconet.org/make-db.log Besides, Why 'make' should bother about tely files? Isn't it supposed to make the binary only? -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com _

Re: Make broken on master [fixed]

2009-07-29 Thread John Mandereau
Le mercredi 29 juillet 2009 à 20:13 +0200, Werner LEMBERG a écrit : > One of the most important constraints of Makefiles: You must not rely > on the order of targets within a single rule. If necessary, you have > to add more rules to enforce a certain order. This is exactly what the CHAIN_RULE tr

Re: Make broken on master [fixed]

2009-07-29 Thread John Mandereau
Le mercredi 29 juillet 2009 à 20:05 +0200, Francisco Vila a écrit : > What makes our setup so different that makes this fail? I think John > should in theory obtain the same result. > > I don't bother removing the whole directory contents despite of having > untracked stuff inside, because I've zi

Re: Make broken on master [fixed]

2009-07-29 Thread Werner LEMBERG
>> It still fails for me on my GNU/Linux box (using git e306bf5d from >> today, checked out cleanly in a separate directory with `git >> clone'). The first documentation file processed is snippets.tely, >> then followed by notation.tely which aborts since identifiers.tely >> is missing. >> >> Some

Re: Make broken on master [fixed]

2009-07-29 Thread Francisco Vila
2009/7/29 Werner LEMBERG : >> Duh, I tracked down the problem; sorry for the delay, I would have >> solved it earlier if I wasn't an idiot or with more complete make >> logs, as I didn't got this failure on my machine, probably because >> of the typical order make compiles Lily docs on it. > > It s

Re: Make broken on master [fixed]

2009-07-29 Thread Werner LEMBERG
> Duh, I tracked down the problem; sorry for the delay, I would have > solved it earlier if I wasn't an idiot or with more complete make > logs, as I didn't got this failure on my machine, probably because > of the typical order make compiles Lily docs on it. It still fails for me on my GNU/Linux

Re: Make broken on master [fixed]

2009-07-28 Thread John Mandereau
Le mardi 28 juillet 2009 à 11:42 +0200, Francisco Vila a écrit : > 2009/7/28 Graham Percival : > >> > >> rm -rf * && git reset --hard > > > Duh, I tracked down the problem; sorry for the delay, I would have solved it earlier if I wasn't an idiot or with more complete make logs, as I didn't got th