Phil Holmes | 30 Jun 2012 17:23
Favicon

Updates to LSR make - problem?

Mike has raised a problem that he has had a make fail while trying to 
compile master.  The failing line is:

LILYPOND_VERSION=2.15.41 /usr/bin/python 
/home/mikesol/lilypond-git/scripts/lilypond-book.py -I 
/home/mikesol/lilypond-git/Documentation/ -I ./out -I 
/home/mikesol/lilypond-git/input -I 
/home/mikesol/lilypond-git/Documentation -I 
/home/mikesol/lilypond-git/build/Documentation/snippets/out -I 
/home/mikesol/lilypond-git/input/regression/ -I 
/home/mikesol/lilypond-git/Documentation/included/ -I 
/home/mikesol/lilypond-git/build/mf/out/ -I 
/home/mikesol/lilypond-git/build/mf/out/ -I 
/home/mikesol/lilypond-git/Documentation/pictures -I 
/home/mikesol/lilypond-git/build/Documentation/pictures/./out --process='true 
 -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle 
 --header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr 
 --header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl 
 --header=doctitlezh --header=texidoc --header=texidoccs --header=texidocde  
--header=texidoces --header=texidocfr --header=texidochu --header=texidocit  
--header=texidocja --header=texidocnl --header=texidoczh -dcheck-internal-types 
 -ddump-signatures -danti-alias-factor=2' --output=./out --format=texi --loglevel=WARN 
 --skip-lily-check --lily-output-dir 
/home/mikesol/lilypond-git/build/out/lybook-db --redirect-lilypond-output 
/home/mikesol/lilypond-git/Documentation/usage.tely
lilypond-book.py: error: file not found: screech-and-boink.ly

This is an example of a snippet which is found in a "general" manual - in 
this case lilypond-book.itely, which is included in usage.tely  It should be 
found, since we have the switch
(Continue reading)

Graham Percival | 30 Jun 2012 17:39
Picon
Favicon

Re: Updates to LSR make - problem?

On Sat, Jun 30, 2012 at 04:23:02PM +0100, Phil Holmes wrote:
> in the call to lilypond-book.  However, on Mike's machine,
> build/Doc/snippets/out does not exist - so the makesnippets script
> hasn't run (or hasn't completed properly).  Do we have a missing
> dependency or something?

makesnippets appears to have gotten onto staging by mistake; it
patch on rietveld has not addressed your concerns.  Presumably it
was only intended to go to dev/jmanderau.

I suggest reverting recent build commits until git master can
compile ok, then we can start looking at the pieces to see which
parts are good to commit (and in what order!), and which pieces
need further examination.

- Graham
Graham Percival | 30 Jun 2012 17:43
Picon
Favicon

Re: Updates to LSR make - problem?

On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote:
> I suggest reverting recent build commits until git master can
> compile ok,

NB: I'm making this suggestion as a normal developer, not as
project manager.  If anybody really likes build scripts, sees the
problem, and can fix it quickly (recalling one anonymous survey
commenting that "in the old days everybody could fix everything"
(or something like that)), then by all means go ahead without
reverting anything.

I don't have the energy to enjoy dealing with crises in git
master; my preference is to reject anything that's questionable
and have a very placid and calm git master.  Ideally by rejecting
questionable material during the countdown phase.

But if younger and more enthusiastic developers can fix it
quickly, then go ahead.

- Graham
David Kastrup | 30 Jun 2012 17:52
X-Face
Picon
Picon

Re: Updates to LSR make - problem?

Graham Percival <graham <at> percival-music.ca> writes:

> On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote:
>> I suggest reverting recent build commits until git master can
>> compile ok,
>
> NB: I'm making this suggestion as a normal developer, not as
> project manager.  If anybody really likes build scripts, sees the
> problem, and can fix it quickly (recalling one anonymous survey
> commenting that "in the old days everybody could fix everything"
> (or something like that)), then by all means go ahead without
> reverting anything.

I am currently trying a revert of
commit e6a5019c531bbc6663e0eebc645409148dbd8931
Author: John Mandereau - LilyPond development <john.mandereau <at> gmail.com>
Date:   Thu Jun 28 18:32:18 2012 +0200

    Clean fonts and docs makefiles, trying to fix 'make -j' race conditions

    On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo),
    "make -j3 all" repeatedly calls fontforge before needed .pfb files are
    generated and makeinfo/extract_texi_filenames/texi2omf before .texi
    file has been generated/copied.  Fix this by using order prerequisites
    and adding targets to WWW-1 (first stage of doc build); order (rather
    than ordinary) prerequisites avoid having always outdated targets,
    which would trigger compilation at install.

    Remove a rule for Info manual that is no longer needed and which might
    short-circuit .dep file generation.
(Continue reading)

Phil Holmes | 30 Jun 2012 17:55
Favicon

Re: Updates to LSR make - problem?

----- Original Message ----- 
From: "David Kastrup" <dak <at> gnu.org>
To: <lilypond-devel <at> gnu.org>
Sent: Saturday, June 30, 2012 4:52 PM
Subject: Re: Updates to LSR make - problem?

> Graham Percival <graham <at> percival-music.ca> writes:
>
>> On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote:
>>> I suggest reverting recent build commits until git master can
>>> compile ok,
>>
>> NB: I'm making this suggestion as a normal developer, not as
>> project manager.  If anybody really likes build scripts, sees the
>> problem, and can fix it quickly (recalling one anonymous survey
>> commenting that "in the old days everybody could fix everything"
>> (or something like that)), then by all means go ahead without
>> reverting anything.
>
> I am currently trying a revert of
> commit e6a5019c531bbc6663e0eebc645409148dbd8931
> Author: John Mandereau - LilyPond development <john.mandereau <at> gmail.com>
> Date:   Thu Jun 28 18:32:18 2012 +0200
>
>    Clean fonts and docs makefiles, trying to fix 'make -j' race conditions
>
>    On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo),
>    "make -j3 all" repeatedly calls fontforge before needed .pfb files are
>    generated and makeinfo/extract_texi_filenames/texi2omf before .texi
>    file has been generated/copied.  Fix this by using order prerequisites
(Continue reading)

Phil Holmes | 30 Jun 2012 18:00
Favicon

Re: Updates to LSR make - problem?

----- Original Message ----- 
From: "Phil Holmes" <mail <at> philholmes.net>
To: <lilypond-devel <at> gnu.org>; "David Kastrup" <dak <at> gnu.org>
Sent: Saturday, June 30, 2012 4:55 PM
Subject: Re: Updates to LSR make - problem?

> ----- Original Message ----- 
> From: "David Kastrup" <dak <at> gnu.org>
> To: <lilypond-devel <at> gnu.org>
> Sent: Saturday, June 30, 2012 4:52 PM
> Subject: Re: Updates to LSR make - problem?
>
>
>> Graham Percival <graham <at> percival-music.ca> writes:
>>
>>> On Sat, Jun 30, 2012 at 04:39:08PM +0100, Graham Percival wrote:
>>>> I suggest reverting recent build commits until git master can
>>>> compile ok,
>>>
>>> NB: I'm making this suggestion as a normal developer, not as
>>> project manager.  If anybody really likes build scripts, sees the
>>> problem, and can fix it quickly (recalling one anonymous survey
>>> commenting that "in the old days everybody could fix everything"
>>> (or something like that)), then by all means go ahead without
>>> reverting anything.
>>
>> I am currently trying a revert of
>> commit e6a5019c531bbc6663e0eebc645409148dbd8931
>> Author: John Mandereau - LilyPond development <john.mandereau <at> gmail.com>
>> Date:   Thu Jun 28 18:32:18 2012 +0200
(Continue reading)

David Kastrup | 30 Jun 2012 18:10
Picon
Picon

Re: Updates to LSR make - problem?

"Phil Holmes" <mail <at> philholmes.net> writes:

> See my previous note.  Please try reverting "Get texidoc translations
> out of snippets source files" first - I can give a cogent reason for
> why this is causing the problem.

My computer agrees.  Pushing the revert.

--

-- 
David Kastrup

Gmane