Re: make doc fails (guilev2)

[Thomas Morley]

2018-02-06 13:17 GMT+01:00 James Lowe :
> Hello,
>
> On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley  
> wrote:
>
>> Hi,
>>
>> I'm still trying to get make doc work again for my guilev2 setup.
>> It now fails at a point I'm not able to surely track down.
>>
>> The only suspicious in the log I'm pointed to is:
>>
>> Processing `./15/lily-ef5769c9.ly'
>
> ...
>
>>
>> Does a simple "programming error" abort make doc?
>
> Are you doing a make doc or a make check?

`make' and `make doc'
>
> Anyway - nothing to do with this thread really but for information - a make 
> check (which runs the reg tests after a 'make test-basline') does not abort 
> with a 'simple' programming error - you can find many times where I have said 
> that a reg test has failed by showing the reg test output itself with that 
> error in it, and this requires the make check to complete in the first place, 
> i.e. to create the file that displays error that I report!
>
> Also a make doc will not abort just on a programming error (you can find a 
> few trackers I have created where some of the MIDI or XML files in the repo 
> always generate a programming error during the make doc process) but again it 
> depends on the context I guess, some programming errors are 'more badder' 
> than others.

Thanks for clarifying, I wasn't sure about those simple `programming error's

Out of my experience with the above quoted
`modifying-the-ottava-spanner-slope.ly', I had some thoughts about
custom-grob-properties, not related to the topic of this thread.
So I'll open a new one.

Thanks,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails (guilev2)

[James Lowe]

Hello,

On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley  
wrote:

> Hi,
> 
> I'm still trying to get make doc work again for my guilev2 setup.
> It now fails at a point I'm not able to surely track down.
> 
> The only suspicious in the log I'm pointed to is:
> 
> Processing `./15/lily-ef5769c9.ly'

...

> 
> Does a simple "programming error" abort make doc?

Are you doing a make doc or a make check?

Anyway - nothing to do with this thread really but for information - a make 
check (which runs the reg tests after a 'make test-basline') does not abort 
with a 'simple' programming error - you can find many times where I have said 
that a reg test has failed by showing the reg test output itself with that 
error in it, and this requires the make check to complete in the first place, 
i.e. to create the file that displays error that I report!

Also a make doc will not abort just on a programming error (you can find a few 
trackers I have created where some of the MIDI or XML files in the repo always 
generate a programming error during the make doc process) but again it depends 
on the context I guess, some programming errors are 'more badder' than others.

regards


James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails (guilev2)

[Thomas Morley]

2018-02-05 23:59 GMT+01:00 Thomas Morley :
> 2018-02-05 23:48 GMT+01:00 David Kastrup :
>> Thomas Morley  writes:
>>
>>> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>>>

 Uh, you are aware that your log ends with:

 Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)

 The programming errors are a nuisance (and should likely get fixed) but
 this aborts for entirely different reasons.
>>>
>>> Yes, but ofcourse a segfault has a reason and the programming errors
>>> were the only other messages.
>>>
>>> Any hint to track it down?
>>
>> set ulimit -c 100
>>
>> (core dump size limit to 100 kbytes) and try again.  Then look in
>> your tree for a file called "core" and call
>>
>> gdb out/bin/lilypond path/to/core
>>
>> and then try
>>
>> backtrace
>>
>> in the debugger.  It's probably not trivial to figure out what file is
>> responsible, but at least one will be able to figure out what happens.
>>
>> --
>> David Kastrup
>
> Thanks, I'll try tomorrow.
>
> Unless I can't sleep tonight 
>
> Cheers,
>   Harm

I nuked my build-directory and started from scratch.
I now have a successfull make and make doc
No clue what happened before.

Thanks,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails (guilev2)

[Thomas Morley]

2018-02-05 23:48 GMT+01:00 David Kastrup :
> Thomas Morley  writes:
>
>> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>>
>>>
>>> Uh, you are aware that your log ends with:
>>>
>>> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>>>
>>> The programming errors are a nuisance (and should likely get fixed) but
>>> this aborts for entirely different reasons.
>>
>> Yes, but ofcourse a segfault has a reason and the programming errors
>> were the only other messages.
>>
>> Any hint to track it down?
>
> set ulimit -c 100
>
> (core dump size limit to 100 kbytes) and try again.  Then look in
> your tree for a file called "core" and call
>
> gdb out/bin/lilypond path/to/core
>
> and then try
>
> backtrace
>
> in the debugger.  It's probably not trivial to figure out what file is
> responsible, but at least one will be able to figure out what happens.
>
> --
> David Kastrup

Thanks, I'll try tomorrow.

Unless I can't sleep tonight 

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails (guilev2)

[David Kastrup]

Thomas Morley  writes:

> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>
>>
>> Uh, you are aware that your log ends with:
>>
>> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>>
>> The programming errors are a nuisance (and should likely get fixed) but
>> this aborts for entirely different reasons.
>
> Yes, but ofcourse a segfault has a reason and the programming errors
> were the only other messages.
>
> Any hint to track it down?

set ulimit -c 100

(core dump size limit to 100 kbytes) and try again.  Then look in
your tree for a file called "core" and call

gdb out/bin/lilypond path/to/core

and then try

backtrace

in the debugger.  It's probably not trivial to figure out what file is
responsible, but at least one will be able to figure out what happens.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails (guilev2)

[Thomas Morley]

2018-02-05 23:23 GMT+01:00 David Kastrup :

>
> Uh, you are aware that your log ends with:
>
> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>
> The programming errors are a nuisance (and should likely get fixed) but
> this aborts for entirely different reasons.

Yes, but ofcourse a segfault has a reason and the programming errors
were the only other messages.

Any hint to track it down?

Cheers,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails (guilev2)

[David Kastrup]

Thomas Morley  writes:

> Hi,
>
> I'm still trying to get make doc work again for my guilev2 setup.
> It now fails at a point I'm not able to surely track down.
>
> The only suspicious in the log I'm pointed to is:
>
> Processing `./15/lily-ef5769c9.ly'
> Parsing...
> Renaming input to: `modifying-the-ottava-spanner-slope.ly'
> Interpreting music...
> Preprocessing graphical objects...
> Calculating line breaks...
> Drawing systems...
> programming error: Grob `OttavaBracket' has no interface for property
> `right-bound-info'
> continuing, cross fingers
> programming error: Grob `OttavaBracket' has no interface for property
> `bound-details'
> continuing, cross fingers
> programming error: Grob `OttavaBracket' has no interface for property
> `right-bound-info'
> continuing, cross fingers
> programming error: Grob `OttavaBracket' has no interface for property
> `left-bound-info'
> continuing, cross fingers
> programming error: Grob `OttavaBracket' has no interface for property
> `bound-details'
> continuing, cross fingers
> programming error: Grob `OttavaBracket' has no interface for property
> `left-bound-info'
> continuing, cross fingers
>
> modifying-the-ottava-spanner-slope.ly contains:

Uh, you are aware that your log ends with:

Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)

The programming errors are a nuisance (and should likely get fixed) but
this aborts for entirely different reasons.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

make doc fails (guilev2)

[Thomas Morley]

Hi,

I'm still trying to get make doc work again for my guilev2 setup.
It now fails at a point I'm not able to surely track down.

The only suspicious in the log I'm pointed to is:

Processing `./15/lily-ef5769c9.ly'
Parsing...
Renaming input to: `modifying-the-ottava-spanner-slope.ly'
Interpreting music...
Preprocessing graphical objects...
Calculating line breaks...
Drawing systems...
programming error: Grob `OttavaBracket' has no interface for property
`right-bound-info'
continuing, cross fingers
programming error: Grob `OttavaBracket' has no interface for property
`bound-details'
continuing, cross fingers
programming error: Grob `OttavaBracket' has no interface for property
`right-bound-info'
continuing, cross fingers
programming error: Grob `OttavaBracket' has no interface for property
`left-bound-info'
continuing, cross fingers
programming error: Grob `OttavaBracket' has no interface for property
`bound-details'
continuing, cross fingers
programming error: Grob `OttavaBracket' has no interface for property
`left-bound-info'
continuing, cross fingers

modifying-the-ottava-spanner-slope.ly contains:

\relative c'' {
  \override Staff.OttavaBracket.stencil = #ly:line-spanner::print
  \override Staff.OttavaBracket.bound-details =
#`((left . ((Y . 0) ; Change the integer here
(attach-dir . ,LEFT)
(padding . 0)
(stencil-align-dir-y . ,CENTER)))
   (right . ((Y . 5) ; Change the integer here
 (padding . 0)
 (attach-dir . ,RIGHT)
 (text . ,(make-draw-dashed-line-markup (cons 0 -1.2))
  \override Staff.OttavaBracket.left-bound-info =
 #ly:line-spanner::calc-left-bound-info-and-text
  \override Staff.OttavaBracket.right-bound-info =
 #ly:line-spanner::calc-right-bound-info
  \ottava #1
  c1
  c'''1
}

And indeed Ottavabracket does not have the line-_spanner_-interface.

Does a simple "programming error" abort make doc?

Cheers,
  Harm

Full log attached, maybe I overlooked something.
GNU LilyPond 2.21.0
Processing `./snippet-map--7355307253113138282.ly'
Parsing...
Processing `./e1/lily-9b66810f.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Calculating line breaks... 
Drawing systems... 
Writing ./e1/lily-9b66810f-1.signature
Layout output to `./e1/lily-9b66810f.eps'...
Converting to `./e1/lily-9b66810f.pdf'...
Converting to PNG...
Layout output to `./e1/lily-9b66810f-1.eps'...
Converting to `./e1/lily-9b66810f-1.pdf'...
Writing ./e1/lily-9b66810f-systems.texi...
Writing ./e1/lily-9b66810f-systems.tex...
Writing ./e1/lily-9b66810f-systems.count...
Processing `./50/lily-71d778b9.ly'
Parsing...
Interpreting music...[8][8]
Preprocessing graphical objects...
Calculating line breaks... 
Drawing systems... 
Writing ./50/lily-71d778b9-1.signature
Layout output to `./50/lily-71d778b9.eps'...
Converting to `./50/lily-71d778b9.pdf'...
Converting to PNG...
Layout output to `./50/lily-71d778b9-1.eps'...
Converting to `./50/lily-71d778b9-1.pdf'...
Writing ./50/lily-71d778b9-systems.texi...
Writing ./50/lily-71d778b9-systems.tex...
Writing ./50/lily-71d778b9-systems.count...
Processing `./f2/lily-8a6b8f5b.ly'
Parsing...
Renaming input to: `tweaking-clef-properties.ly'
Interpreting music...[8]
Preprocessing graphical objects...
Calculating line breaks... 
Drawing systems... 
Writing header field `doctitlees' to `./f2/lily-8a6b8f5b.doctitlees'...
Writing header field `doctitleit' to `./f2/lily-8a6b8f5b.doctitleit'...
Writing header field `texidoces' to `./f2/lily-8a6b8f5b.texidoces'...
Writing header field `doctitlefr' to `./f2/lily-8a6b8f5b.doctitlefr'...
Writing header field `texidoc' to `./f2/lily-8a6b8f5b.texidoc'...
Writing header field `texidocit' to `./f2/lily-8a6b8f5b.texidocit'...
Writing header field `texidocfr' to `./f2/lily-8a6b8f5b.texidocfr'...
Writing header field `doctitlede' to `./f2/lily-8a6b8f5b.doctitlede'...
Writing header field `texidocde' to `./f2/lily-8a6b8f5b.texidocde'...
Writing header field `doctitle' to `./f2/lily-8a6b8f5b.doctitle'...
Writing ./f2/lily-8a6b8f5b-1.signature
Writing ./f2/lily-8a6b8f5b-2.signature
Layout output to `./f2/lily-8a6b8f5b.eps'...
Converting to `./f2/lily-8a6b8f5b.pdf'...
Converting to PNG...
Layout output to `./f2/lily-8a6b8f5b-1.eps'...
Layout output to `./f2/lily-8a6b8f5b-2.eps'...
Converting to `./f2/lily-8a6b8f5b-1.pdf'...
Converting to `./f2/lily-8a6b8f5b-2.pdf'...
Writing ./f2/lily-8a6b8f5b-systems.texi...
Writing ./f2/lily-8a6b8f5b-systems.tex...
Writing ./f2/lily-8a6b8f5b-systems.count...
Processing `./ad/lily-6df743ce.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Calculating line breaks... 
Drawing systems... 
Writing ./ad/lily-6df743ce-1.signature
Layout output to `./ad/lily-6df743ce.eps'...
Converting to `./ad/lily-6df743ce.pdf'...
Converting to PNG...
Layout output to `./ad/lily-6df743ce-1.eps'...
Converting to `./ad/lily-6df743ce-1.pdf'...
Writing ./ad/lily-6df743ce-systems.texi...
Writing 

Solved: make doc fails after updating dev to VERSION 2.19.38 (and later)

[Villum Sejersen]

On 16-03-2016 22:58, Carl Sorensen wrote:


LilyPond can be very finicky trying to get a clean build.  That's why we 
recommend using LilyDev.


Thanks for that advice, though it is way beyond my skill and needs. I 
never build anything else than current master, but have tried doing so 
even back in .svn-times.



I realize this is not a great answer for a Linux hacker.


I am not a hacker, not a programmer. ;) 25 years ago i - with help - was 
a system administrator on a Sun OS 1.4.x system...


I am a bit embarassed that core developers find using their time on 
questions I might have answered myself.


Many thanks to James, you and all the many other helping hands.


I've looked briefly through your logs.  Are you running a multi-processor
build (make -j3 doc)?  If so, that can make it harder to interpret the
logs.  It might be well to to a single job build (make doc).


My ancient pc is an AMD Athlon X2, so only -j2 was used. Building docs 
locally takes nearly two hours. I prefer it that way because my internet 
connection is slow (but reliable).



I'm sorry I don't have a better answer for you at this time.


Well, it made me try again several times :)

It think it worked out the third time after trying various combinations 
of autogen.sh, configure, make clean, make distclean and make doc-clean. 
Exactly how and why must here be an unanswered question...



Carl



--
med venlig hilsen
Villum Sejersen
Nørregade  1 A
DK-4500  Nykøbing Sjælland
mobil   +45   30 34  03 44


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails after updating dev to VERSION 2.19.38

[James]

Villum,

On 09/03/16 11:02, Villum Sejersen wrote:

- Original Message - From: "Villum Sejersen" <address@hidden>

To: <address@hidden> Sent: Wednesday, March 09, 2016 9:52 AM Subject: 
make doc fails after updating dev to VERSION 2.19.38


   While make [all] and make install repeatably works as usual from
   latest git sources, make doc does not compile the 2.19.38 version,
   regardless how many, how many times and which cleaning attempts I
   try before.
   The last few lines of the log file looks:



o you have xetex properly installed? -- Phil Holmes

I believe so:


If I'd probably 'make distclean' and/or 'make clean' your build 
environment (just to be sure) and then when you run the 'configure' 
command see what it lists as that will tell you if we find XeTeX 
installed or not.


Just so you know the addition of XeTeX was to get over a problem of 
missing ligatures in our default Pdf2TeX method we use to build the 
docs, but there needed to be an additional checkin (that was done 
yesterday or Monday) that stopped the doc process being borked if you 
didn't install it.


It is supposed to be 'optional'.

There is also, just for completeness, some documentation changes to the 
Contributor Guide that is currently in review that will add this note 
for other users - hopefully it will be pushed to latest master in the 
next couple of days.


James

PS I built doc this morning using latest current master to test a patch 
for the developers, so I know that it should work (with XeTeX installed 
anyway).


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails after updating dev to VERSION 2.19.38

[Villum Sejersen]

- Original Message - From: "Villum Sejersen" <address@hidden>

To: <address@hidden> Sent: Wednesday, March 09, 2016 9:52 AM Subject: 
make doc fails after updating dev to VERSION 2.19.38


   While make [all] and make install repeatably works as usual from
   latest git sources, make doc does not compile the 2.19.38 version,
   regardless how many, how many times and which cleaning attempts I
   try before. 


   The last few lines of the log file looks:



o you have xetex properly installed? -- Phil Holmes

I believe so:

root@Villums14:~# xetex --version
XeTeX 3.14159265-2.6-0.2 (TeX Live 2015/Debian) kpathsea version 6.2.1
Copyright 2015 SIL International, Jonathan Kew and Khaled Hosny.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the XeTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the XeTeX source.
Primary author of XeTeX: Jonathan Kew.
Compiled with ICU version 55.1; using 55.1
Compiled with zlib version 1.2.8; using 1.2.8
Compiled with FreeType2 version 2.5.5; using 2.5.5
Compiled with Graphite2 version 1.3.5; using 1.3.6
Compiled with HarfBuzz version 1.0.1; using 1.0.1
Compiled with libpng version 1.6.17; using 1.6.17
Compiled with poppler version 0.38.0
Compiled with fontconfig version 2.11.0; using 2.11.0


To David (sorry for danish messages):

root@Villums14:~# apt-get install texlive-xetex
Indlæser pakkelisterne... Færdig
Opbygger afhængighedstræ
Læser tilstandsoplysninger... Færdig
texlive-xetex is already the newest version (2015.20160223-1).
0 opgraderes, 0 nyinstalleres, 0 afinstalleres og 0 opgraderes ikke.


FWIW:

root@Villums14:~# uname -a
Linux Villums14 4.3.0-1-amd64 #1 SMP Debian 4.3.5-1 (2016-02-06) x86_64 
GNU/Linux


Frescobaldi: 2.18.2

Python: 2.7.11+

python-ly: 0.9.3

Qt: 4.8.7

PyQt: 4.11.4

sip: 4.17

poppler: 0.38.0

python-poppler-qt: 0.24.0

OS: Linux-4.3.0-1-amd64-x86_64-with-debian-stretch-sid


--
yours,
Villum Sejersen
Nørregade  1 A
DK-4500  Nykøbing Sjælland
mobil   +45   30 34  03 44

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails after updating dev to VERSION 2.19.38

[David Kastrup]

Villum Sejersen  writes:

> While make [all] and make install repeatably works as usual from
> latest git sources, make doc does not compile the 2.19.38 version,
> regardless how many, how many times and which cleaning attempts I try
> before.
>
> Tanks in advance for any advice...

sudo apt-get install texlive-xetex

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails after updating dev to VERSION 2.19.38

[Phil Holmes]

- Original Message - 
From: "Villum Sejersen" <v...@privat.tdcadsl.dk>

To: <lilypond-devel@gnu.org>
Sent: Wednesday, March 09, 2016 9:52 AM
Subject: make doc fails after updating dev to VERSION 2.19.38


While make [all] and make install repeatably works as usual from latest 
git sources, make doc does not compile the 2.19.38 version, regardless 
how many, how many times and which cleaning attempts I try before.



The last few lines of the log file looks:


Do you have xetex properly installed?

--
Phil Holmes

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

make doc fails after updating dev to VERSION 2.19.38

[Villum Sejersen]

While make [all] and make install repeatably works as usual from latest
git sources, make doc does not compile the 2.19.38 version, regardless
how many, how many times and which cleaning attempts I try before.

The last few lines of the log file looks:

mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
true
make[2]: Leaving directory '/usr/local/src/lilypond/build/vim'
make[2]: Entering directory '/usr/local/src/lilypond/build/input'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
make PACKAGE=LILYPOND package=lilypond -C regression WWW-1 && true
make[3]: Entering directory '/usr/local/src/lilypond/build/input/regression'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
/usr/local/src/lilypond/build/scripts/build/out/lys-to-tely
--name=./out-www/collated-files.tely --title="LilyPond Regression Tests"
--author="Han-Wen Nienhuys and Jan Nieuwenhuizen"
--input-filename=out-www/collated-files.list
/usr/bin/python -tt
/usr/local/src/lilypond/scripts/build/create-version-itexi.py >
out-www/version.itexi
LILYPOND_VERSION=2.19.38 PDFTEX=xetex PDFLATEX=xelatex /usr/bin/python
-tt /usr/local/src/lilypond/scripts/lilypond-book.py -I
/usr/local/src/lilypond/input/regression
--process='/usr/local/src/lilypond/build/out/bin/lilypond -I
/usr/local/src/lilypond/input/regression  -dbackend=eps
--formats=ps,png,pdf -djob-count=2 -dinclude-eps-fonts -dgs-load-fonts
--header=doctitle --header=doctitleca --header=doctitlecs
--header=doctitlede --header=doctitlees --header=doctitlefr
--header=doctitlehu --header=doctitleit --header=doctitleja
--header=doctitlenl --header=doctitlezh --header=texidoc
--header=texidocca --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-www --format=texi-html
--loglevel=WARN  --lily-output-dir
/usr/local/src/lilypond/build/out/lybook-db --redirect-lilypond-output
out-www/collated-files.tely
command failed: /usr/local/src/lilypond/build/out/bin/lilypond -I
/usr/local/src/lilypond/input/regression  -dbackend=eps
--formats=ps,png,pdf -djob-count=2 -dinclude-eps-fonts -dgs-load-fonts
--header=doctitle --header=doctitleca --header=doctitlecs
--header=doctitlede --header=doctitlees --header=doctitlefr
--header=doctitlehu --header=doctitleit --header=doctitleja
--header=doctitlenl --header=doctitlezh --header=texidoc
--header=texidocca --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 -I  "./"  -I
"/usr/local/src/lilypond/build/input/regression"  -I
"/usr/local/src/lilypond/input/regression" --formats=eps
-deps-box-padding=3.00  -dread-file-list -dno-strip-output-dir
"/usr/local/src/lilypond/build/out/lybook-db/snippet-names-2063213751245854722.ly"
Child returned 1
Error ignored by lilylib
Error trapped by lilypond-book
Please see
/usr/local/src/lilypond/build/out/lybook-db/snippet-names-2063213751245854722.log


Attached.

Tanks in advance for any advice...

--
yours,
Villum Sejersen
Nørregade  1 A
DK-4500  Nykøbing Sjælland
mobil   +45   30 34  03 44

GNU LilyPond 2.19.38

Forking into jobs:  (22061 22060)
logfile lilypond-multi-run-1.log (exit 1):
. 
Calculating line breaks... 
Drawing systems... 
Writing header field `texidoc' to `./91/lily-291ea81c.texidoc'...
Writing ./91/lily-291ea81c-1.signature
Writing ./91/lily-291ea81c-2.signature
Writing ./91/lily-291ea81c-3.signature
Writing ./91/lily-291ea81c-4.signature
Layout output to `./91/lily-291ea81c.eps'...
Converting to `./91/lily-291ea81c.pdf'...
Converting to PNG...
Layout output to `./91/lily-291ea81c-1.eps'...
Layout output to `./91/lily-291ea81c-2.eps'...
Layout output to `./91/lily-291ea81c-3.eps'...
Layout output to `./91/lily-291ea81c-4.eps'...
Converting to `./91/lily-291ea81c-1.pdf'...
Converting to `./91/lily-291ea81c-2.pdf'...
Converting to `./91/lily-291ea81c-3.pdf'...
Converting to `./91/lily-291ea81c-4.pdf'...
Writing ./91/lily-291ea81c-systems.texi...
Writing ./91/lily-291ea81c-systems.tex...
Writing ./91/lily-291ea81c-systems.count...
Processing `./snippet-map-2063213751245854722.ly'
Parsing...
fatal error: failed files: "55/lily-c61e089a.ly 16/lily-fb4bd50d.ly 1b/lily-703d6aa3.ly"
logfile lilypond-multi-run-0.log (exit 1):

Converting to `./29/lily-e0ac5d9b-2.pdf'...
Writing ./29/lily-e0ac5d9b-systems.texi...
Writing ./29/lily-e0ac5d9b-systems.tex...
Writing ./29/lily-e0ac5d9b-systems.count...
Processing `./94/lily-32d78681.ly'
Parsing...
Renaming input to: `/usr/local/src/lilypond/input/regression/page-breaking-min-systems-per-page2.ly'
Interpreting music...[8][16]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...

Re: make doc fails

[Phil Holmes]

FWIW, this was down to me removing the very out-of-date Czech news file from 
the build.  The simple cure for problems like this is to make doc clean and try 
again.  Failing that, delete the build directory and run make, make doc again.

--
Phil Holmes


  - Original Message - 
  From: David Nalesnik 
  To: Julien Rioux 
  Cc: LilyPond Devel 
  Sent: Sunday, March 17, 2013 2:17 AM
  Subject: Re: make doc fails


  Julien,


  On Sat, Mar 16, 2013 at 7:31 PM, Julien Rioux jri...@lyx.org wrote:

On 16/03/2013 6:27 PM, David Nalesnik wrote:

  /usr/bin/python -tt
  /home/david/lilypond-git/scripts/build/create-weblinks-itexi.py 
  out-www/weblinks.itexi
  make[3]: *** No rule to make target
  `/home/david/lilypond-git/Documentation/cs/web/news-front.itexi', needed 
by
  `out-www/web.texi'.  Stop.



Try removing Documentation/cs/out-www/web.dep and running `make doc' again. 
If it succeeds but fails at the next language, repeat for each language. 
Alternatively, if all that fails, try `make doc-clean' and running `make doc' 
again.



  I ended up deleting the file in cs/ and zh/ and that did the trick.  Thanks 
very much!


  -David 


--


  ___
  lilypond-devel mailing list
  lilypond-devel@gnu.org
  https://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

make doc fails

[David Nalesnik]

Hi all,

I'm attempting to put two snippets dealing with the measure counter up for
review, but I'm running into problems when I run make doc.  Here's the tail
end of the terminal output:

make[3]: Entering directory
`/home/david/lilypond-git/build/Documentation/cs'
/usr/bin/python -tt
/home/david/lilypond-git/scripts/build/create-version-itexi.py 
out-www/version.itexi
LILYPOND_VERSION=2.17.15 /usr/bin/python -tt
/home/david/lilypond-git/scripts/lilypond-book.py -I
/home/david/lilypond-git/Documentation/cs/ -I ./out-www -I
/home/david/lilypond-git/input -I /home/david/lilypond-git/Documentation -I
/home/david/lilypond-git/build/Documentation/snippets/out -I
/home/david/lilypond-git/input/regression/ -I
/home/david/lilypond-git/Documentation/included/ -I
/home/david/lilypond-git/build/mf/out/ -I
/home/david/lilypond-git/build/mf/out/ -I
/home/david/lilypond-git/Documentation/pictures -I
/home/david/lilypond-git/build/Documentation/pictures/./out-www -I
/home/david/lilypond-git/Documentation/cs/included -I
/home/david/lilypond-git/Documentation -I
/home/david/lilypond-git/build/Documentation/./out-www
--process='/home/david/lilypond-git/build/out/bin/lilypond -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-www
--format=texi-html --loglevel=WARN  --lily-output-dir
/home/david/lilypond-git/build/out/lybook-db --redirect-lilypond-output
/home/david/lilypond-git/Documentation/cs/learning.tely
/usr/bin/python -tt
/home/david/lilypond-git/scripts/build/create-weblinks-itexi.py 
out-www/weblinks.itexi
make[3]: *** No rule to make target
`/home/david/lilypond-git/Documentation/cs/web/news-front.itexi', needed by
`out-www/web.texi'.  Stop.
make[3]: Leaving directory `/home/david/lilypond-git/build/Documentation/cs'
make[2]: *** [WWW-1] Error 2
make[2]: Leaving directory `/home/david/lilypond-git/build/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/david/lilypond-git/build'
make: *** [doc-stage-1] Error 2
david@david-desktop ~/lilypond-git/build (dev/measure_counter_doc)$


Frankly, I have no idea if this is a problem that I've created.  (I don't
know if this is relevant, but I note that the two snippets appear in
.../build/out-www/offline-root/Documentation/snippets.pdf but not in
.../snippets-big-page.html.)

Any help would be appreciated!

Thanks,
David
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails

[Julien Rioux]

On 16/03/2013 6:27 PM, David Nalesnik wrote:

/usr/bin/python -tt
/home/david/lilypond-git/scripts/build/create-weblinks-itexi.py 
out-www/weblinks.itexi
make[3]: *** No rule to make target
`/home/david/lilypond-git/Documentation/cs/web/news-front.itexi', needed by
`out-www/web.texi'.  Stop.


Try removing Documentation/cs/out-www/web.dep and running `make doc' 
again. If it succeeds but fails at the next language, repeat for each 
language. Alternatively, if all that fails, try `make doc-clean' and 
running `make doc' again.


Regards,
Julien

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails

[David Nalesnik]

Julien,

On Sat, Mar 16, 2013 at 7:31 PM, Julien Rioux jri...@lyx.org wrote:

 On 16/03/2013 6:27 PM, David Nalesnik wrote:

 /usr/bin/python -tt
 /home/david/lilypond-git/**scripts/build/create-weblinks-**itexi.py 
 out-www/weblinks.itexi
 make[3]: *** No rule to make target
 `/home/david/lilypond-git/**Documentation/cs/web/news-**front.itexi',
 needed by
 `out-www/web.texi'.  Stop.


 Try removing Documentation/cs/out-www/web.**dep and running `make doc'
 again. If it succeeds but fails at the next language, repeat for each
 language. Alternatively, if all that fails, try `make doc-clean' and
 running `make doc' again.


I ended up deleting the file in cs/ and zh/ and that did the trick.  Thanks
very much!

-David
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[m...@apollinemike.com]

On Aug 28, 2011, at 4:33 AM, Graham Percival wrote:

 On Sun, Aug 28, 2011 at 03:19:00AM +0100, Graham Percival wrote:
 On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
 This afternoon I've done a fresh pull, make and make doc.  Make doc
 failed with this:
 
 Indeed.  It needed to run
  scripts/auxiliar/makelsr.py
 I've just done that, and will push once the build successfully
 finishes.
 
 Mike.
 
 Your commit
  Adds a Flag grob to LilyPond.
  f0978ed121192fee9bdf2453a325d98693148acf
 introduced a syntax change with no convert-ly rule.  It also broke
 compiling on git master.  I am now fixing stuff manually.  This is
 not how I was planning on spending my 3am Sunday morning.
 

Graham,

Thanks very much for your help, and I'm sorry for adding extra stuff to your 
plate at an inopportune time.  Please let me know what I could do to prevent 
this from happening again - I try to follow the review process as fastidiously 
as possible, and am always looking to be more meticulous about making sure that 
my work does not have unanticipated negative impacts.

As for the convert-ly rule, I was under the impression that these rules were 
pushed on a version-to-version basis, and all syntax changes were written as 
one rule before the rolling of the next version.  The last time I added one was 
because the versions had changed and a rule didn't exist for the version during 
which a commit of mine happened.  Please let me know how you want me to go 
about this in the future - if there could be an entry in the CG about it, 
that'd help a great deal.

Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Graham Percival]

On Sun, Aug 28, 2011 at 11:29:28AM +0200, m...@apollinemike.com wrote:
 
 Please let me know what I could do to prevent this from happening again

Since you were editing documentation, I would have liked you to
have:
1. touch Documentation/*.te??
   (this tells make to check all manuals to see if they need
recompiling)
2. make doc

If you'd done that, you would have seen the build fail.


 As for the convert-ly rule, I was under the impression that
 these rules were pushed on a version-to-version basis, and all
 syntax changes were written as one rule before the rolling of
 the next version.  The last time I added one was because the
 versions had changed and a rule didn't exist for the version
 during which a commit of mine happened.  Please let me know how
 you want me to go about this in the future - if there could be
 an entry in the CG about it, that'd help a great deal.

Hmm, we don't really have a set policy for this -- and with the
patch/review/push cycle sometimes taking more than a month, it's a
tricky issue.

For now, let's just say that syntax changes are really, really
icky, and if you absolutely need to do one, we'll talk about how
to do it safely in that specific instance.  I don't want to try to
make a general rule at the moment.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Phil Holmes]

- Original Message - 
From: Graham Percival gra...@percival-music.ca

To: Phil Holmes em...@philholmes.net; m...@apollinemike.com
Cc: Devel lilypond-devel@gnu.org
Sent: Sunday, August 28, 2011 3:33 AM
Subject: Re: Make doc fails



On Sun, Aug 28, 2011 at 03:19:00AM +0100, Graham Percival wrote:

On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
 This afternoon I've done a fresh pull, make and make doc.  Make doc
 failed with this:

Indeed.  It needed to run
  scripts/auxiliar/makelsr.py
I've just done that, and will push once the build successfully
finishes.


Mike.

Your commit
 Adds a Flag grob to LilyPond.
 f0978ed121192fee9bdf2453a325d98693148acf
introduced a syntax change with no convert-ly rule.  It also broke
compiling on git master.  I am now fixing stuff manually.  This is
not how I was planning on spending my 3am Sunday morning.


Unfortunately we cannot ask James to do a complete documentation
compile to test each patch, but as soon as I can build a release
again, I will create an automatic compiling checker.

- Graham


I think that's fixed one problem, but I can't test because another change 
appears to have created another problem:


lily.scmBacktrace:
In /home/phil/lilypond-git/build/out/share/lilypond/current/scm/lily.scm:
479: 0* [for-each #procedure ly:load # #]
In unknown file:
  ?: 1* [ly:load define-grobs.scm]
In /home/phil/lilypond-git/build/out/share/lilypond/current/scm/lily.scm:
289: 2* (let* ((file-name (%search-load-path x))) (ly:debug [~A 
file-name) ...)
293: 3* [primitive-load-path 
/home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm]
In 
/home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm:

2629: 4* (define pure-conversions-alist (quasiquote (# # # # ...)))
2630: 5* (quasiquote (# # # # ...))

/home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm:2630:3: 
In expression (quasiquote (# # # ...)):
/home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm:2630:3: 
Unbound variable: ly:stem::pure-calc-stem-end-position
command failed: /home/phil/lilypond-git/build/out/bin/lilypond [snip 
options] 
/home/phil/lilypond-git/build/out/lybook-db/snippet-names-2097757151.ly



--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[m...@apollinemike.com]

On Aug 28, 2011, at 11:46 AM, Phil Holmes wrote:

 - Original Message - From: Graham Percival 
 gra...@percival-music.ca
 To: Phil Holmes em...@philholmes.net; m...@apollinemike.com
 Cc: Devel lilypond-devel@gnu.org
 Sent: Sunday, August 28, 2011 3:33 AM
 Subject: Re: Make doc fails
 
 
 On Sun, Aug 28, 2011 at 03:19:00AM +0100, Graham Percival wrote:
 On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
  This afternoon I've done a fresh pull, make and make doc.  Make doc
  failed with this:
 
 Indeed.  It needed to run
  scripts/auxiliar/makelsr.py
 I've just done that, and will push once the build successfully
 finishes.
 
 Mike.
 
 Your commit
 Adds a Flag grob to LilyPond.
 f0978ed121192fee9bdf2453a325d98693148acf
 introduced a syntax change with no convert-ly rule.  It also broke
 compiling on git master.  I am now fixing stuff manually.  This is
 not how I was planning on spending my 3am Sunday morning.
 
 
 Unfortunately we cannot ask James to do a complete documentation
 compile to test each patch, but as soon as I can build a release
 again, I will create an automatic compiling checker.
 
 - Graham
 
 I think that's fixed one problem, but I can't test because another change 
 appears to have created another problem:
 
 lily.scmBacktrace:
 In /home/phil/lilypond-git/build/out/share/lilypond/current/scm/lily.scm:
 479: 0* [for-each #procedure ly:load # #]
 In unknown file:
  ?: 1* [ly:load define-grobs.scm]
 In /home/phil/lilypond-git/build/out/share/lilypond/current/scm/lily.scm:
 289: 2* (let* ((file-name (%search-load-path x))) (ly:debug [~A file-name) 
 ...)
 293: 3* [primitive-load-path 
 /home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm]
 In 
 /home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm:
 2629: 4* (define pure-conversions-alist (quasiquote (# # # # ...)))
 2630: 5* (quasiquote (# # # # ...))
 
 /home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm:2630:3:
  In expression (quasiquote (# # # ...)):
 /home/phil/lilypond-git/build/out/share/lilypond/current/scm/define-grobs.scm:2630:3:
  Unbound variable: ly:stem::pure-calc-stem-end-position
 command failed: /home/phil/lilypond-git/build/out/bin/lilypond [snip options] 
 /home/phil/lilypond-git/build/out/lybook-db/snippet-names-2097757151.ly
 
 

Phil,

This comes from my Stem patch.  I didn't think to touch the docs for this, but 
I will take care of it over the next two hours and post a patch for review.

Cheers,
MS


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Reinhold Kainhofer]

Am Sunday, 28. August 2011, 11:29:28 schrieb m...@apollinemike.com:
 As for the convert-ly rule, I was under the impression that these rules
 were pushed on a version-to-version basis, and all syntax changes were
 written as one rule before the rolling of the next version.

Nope. As soon as you make a syntax change, you are supposed to add the 
corresponding rule to convertrules.py. The rules are grouped by version, but 
that does not mean that you have to write all rules for one version in one go.

So, if yere is already a conv function for the latest version, simply update 
that rule with the new replacements, otherwise you simply create a new conv 
rule for the version.

Cheers,
Reinhold

-- 
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial  Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Graham Percival]

On Sun, Aug 28, 2011 at 10:46:24AM +0100, Phil Holmes wrote:
 I think that's fixed one problem, but I can't test because another
 change appears to have created another problem:
 
 Unbound variable: ly:stem::pure-calc-stem-end-position
 command failed: /home/phil/lilypond-git/build/out/bin/lilypond [snip
 options] 
 /home/phil/lilypond-git/build/out/lybook-db/snippet-names-2097757151.ly

can't reproduce.  I just did a complete doc rebuild from scratch
  7ee4165c3403cdd121621f75ed408a241621d37b
and there were no complaints.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Phil Holmes]

- Original Message - 
From: Graham Percival gra...@percival-music.ca

To: Phil Holmes m...@philholmes.net
Cc: m...@apollinemike.com; Devel lilypond-devel@gnu.org
Sent: Sunday, August 28, 2011 11:25 AM
Subject: Re: Make doc fails



On Sun, Aug 28, 2011 at 10:46:24AM +0100, Phil Holmes wrote:

I think that's fixed one problem, but I can't test because another
change appears to have created another problem:

Unbound variable: ly:stem::pure-calc-stem-end-position
command failed: /home/phil/lilypond-git/build/out/bin/lilypond [snip
options] 
/home/phil/lilypond-git/build/out/lybook-db/snippet-names-2097757151.ly


can't reproduce.  I just did a complete doc rebuild from scratch
 7ee4165c3403cdd121621f75ed408a241621d37b
and there were no complaints.

Cheers,
- Graham



I wondered the same thing.  My error message came from the previously 
interrupted build, so I'm in the process of another now.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Carl Sorensen]

On 8/28/11 3:29 AM, m...@apollinemike.com m...@apollinemike.com wrote:


 
 As for the convert-ly rule, I was under the impression that these rules were
 pushed on a version-to-version basis, and all syntax changes were written as
 one rule before the rolling of the next version.  The last time I added one
 was because the versions had changed and a rule didn't exist for the version
 during which a commit of mine happened.  Please let me know how you want me to
 go about this in the future - if there could be an entry in the CG about it,
 that'd help a great deal.

CG 10.8 has a set of steps for adding or modifying features:
10.8.1 -- write the code.
10.8.2 -- write regression tests.
10.8.3 -- Write convert-ly rule.
10.8.4 -- Automatically update documentation
10.8.5 -- Manually update documentation (if a NOT_SMART rule is used)
10.8.6 -- Edit changes.tely
10.8.7 -- Verify successful build
10.8.8 -- Verify regression tests
10.8.9 -- Post patch for comments
10.8.10 -- Push patch
10.8.11 -- Close issue

It seems like many of us (including me sometimes, and I wrote these steps in
the CG) are inclined to jump right from 10.8.2 to 10.8.9.

Please note that 10.8.4 and 10.8.5 do *not* require the programmer to make
sure the new change is documented.  They just require the programmer to make
sure the new change doesn't break the build system.

According to the CG, no patch should even be posted for review unless make
doc runs successfully.  Perhaps this rule is ignored because make doc takes
so long to run.

Mike, I think you've done a great job of contributing to LilyPond.  I'm
certainly not throwing rocks at you -- an occasional mistake is certainly a
small price to pay for all of the great contributions you've made.

Thanks,

Carl


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Phil Holmes]

- Original Message - 
From: Graham Percival gra...@percival-music.ca

To: Phil Holmes m...@philholmes.net
Cc: m...@apollinemike.com; Devel lilypond-devel@gnu.org
Sent: Sunday, August 28, 2011 11:25 AM
Subject: Re: Make doc fails



On Sun, Aug 28, 2011 at 10:46:24AM +0100, Phil Holmes wrote:

I think that's fixed one problem, but I can't test because another
change appears to have created another problem:

Unbound variable: ly:stem::pure-calc-stem-end-position
command failed: /home/phil/lilypond-git/build/out/bin/lilypond [snip
options] 
/home/phil/lilypond-git/build/out/lybook-db/snippet-names-2097757151.ly


can't reproduce.  I just did a complete doc rebuild from scratch
 7ee4165c3403cdd121621f75ed408a241621d37b
and there were no complaints.

Cheers,
- Graham



Confirmed.  A vestige of my partial build.

--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[m...@apollinemike.com]

On Aug 28, 2011, at 4:58 PM, Phil Holmes wrote:

 - Original Message - From: Graham Percival 
 gra...@percival-music.ca
 To: Phil Holmes m...@philholmes.net
 Cc: m...@apollinemike.com; Devel lilypond-devel@gnu.org
 Sent: Sunday, August 28, 2011 11:25 AM
 Subject: Re: Make doc fails
 
 
 On Sun, Aug 28, 2011 at 10:46:24AM +0100, Phil Holmes wrote:
 I think that's fixed one problem, but I can't test because another
 change appears to have created another problem:
 
 Unbound variable: ly:stem::pure-calc-stem-end-position
 command failed: /home/phil/lilypond-git/build/out/bin/lilypond [snip
 options] 
 /home/phil/lilypond-git/build/out/lybook-db/snippet-names-2097757151.ly
 
 can't reproduce.  I just did a complete doc rebuild from scratch
 7ee4165c3403cdd121621f75ed408a241621d37b
 and there were no complaints.
 
 Cheers,
 - Graham
 
 
 Confirmed.  A vestige of my partial build.
 

Good to know, and thanks for the follow-up, Phil.

Cheers,
MS


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[m...@apollinemike.com]

On Aug 28, 2011, at 12:58 PM, Carl Sorensen wrote:

 On 8/28/11 3:29 AM, m...@apollinemike.com m...@apollinemike.com wrote:
 
 
 
 As for the convert-ly rule, I was under the impression that these rules were
 pushed on a version-to-version basis, and all syntax changes were written as
 one rule before the rolling of the next version.  The last time I added one
 was because the versions had changed and a rule didn't exist for the version
 during which a commit of mine happened.  Please let me know how you want me 
 to
 go about this in the future - if there could be an entry in the CG about it,
 that'd help a great deal.
 
 CG 10.8 has a set of steps for adding or modifying features:
 10.8.1 -- write the code.
 10.8.2 -- write regression tests.
 10.8.3 -- Write convert-ly rule.
 10.8.4 -- Automatically update documentation
 10.8.5 -- Manually update documentation (if a NOT_SMART rule is used)
 10.8.6 -- Edit changes.tely
 10.8.7 -- Verify successful build
 10.8.8 -- Verify regression tests
 10.8.9 -- Post patch for comments
 10.8.10 -- Push patch
 10.8.11 -- Close issue
 
 It seems like many of us (including me sometimes, and I wrote these steps in
 the CG) are inclined to jump right from 10.8.2 to 10.8.9.
 

+1 - I missed this day of class, or if I was there, I wasn't paying attention...
I'll do my best to be as meticulous about this as possible from here on out.

 Please note that 10.8.4 and 10.8.5 do *not* require the programmer to make
 sure the new change is documented.  They just require the programmer to make
 sure the new change doesn't break the build system.
 

My changes to the stem patch don't break the build system, but I'm positive 
they lead to bizarre output in a few .ly examples.  That's why I like Graham's 
idea of some type of automatic checking.

 According to the CG, no patch should even be posted for review unless make
 doc runs successfully.  Perhaps this rule is ignored because make doc takes
 so long to run.
 

I am way guilty of this...in fact, so guilty that I don't think I've ever once 
followed it, which means that it's a miracle that we haven't hit this problem 
before the flag patch ;(
As I previously said, I'm all for coming up with some type of automated system 
so that this condition can be relaxed.

 Mike, I think you've done a great job of contributing to LilyPond.  I'm
 certainly not throwing rocks at you -- an occasional mistake is certainly a
 small price to pay for all of the great contributions you've made.
 

Thanks, Carl.
As always, I'm doing my best to (a) make sure there aren't any loose ends; and 
(b) if there are, clean them up as fast as possible.  Today has been kinda 
tight cause I'm moving to the burbs and packing boxes, but tomorrow I'll be 
able to respond thoroughly to everything that comes in.

Cheers,
MS


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Make doc fails

[Phil Holmes]

This afternoon I've done a fresh pull, make and make doc.  Make doc failed 
with this:


command failed: /home/phil/lilypond-git/build/out/bin/lilypond -dbackend=eps 
[snip lots of options] 
/home/phil/lilypond-git/build/out/lybook-db/snippet-names-828948788.ly


Then:

fatal error: failed files: 53/lily-5dc13594.ly

Looking at lily-5dc13594.ly, we see \sourcefilename 
displaying-complex-chords.ly


Finding that in the make output gives:

Renaming input to: `displaying-complex-chords.ly']
Interpreting music...
[/home/phil/lilypond-git/build/out/share/lilypond/current/fonts/otf/emmentaler-20.otf]
warning: cannot find property type-check for `flag-style' (backend-type?). 
perhaps a typing error?


This snippet was updated in Mike's recent commit 
f0978ed121192fee9bdf2453a325d98693148acf (Adds a Flag grob to LilyPond).


Looking at the source files, we've got a new displaying-complex-chords.ly in 
snippets/new and an older one in snippets/.  It's a guess here - has the 
.exe been updated so it barfs on


 \once \override Stem #'flag-style = #'no-flag

and so the new snippet has

 \once \override Flag #'style = #'no-flag

But this hasn't been updated into the snippets/ directory?

Given that \once \override Stem #'flag-style = #'no-flag used to be OK (I 
believe) should this warning be present?



--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Graham Percival]

On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
 This afternoon I've done a fresh pull, make and make doc.  Make doc
 failed with this:

Indeed.  It needed to run
  scripts/auxiliar/makelsr.py
I've just done that, and will push once the build successfully
finishes.


I noticed a bunch of changes concerning @code{#foo}.  I imagine
that this commit is reverting some changes that Werner made.  If
anybody wants to look into this, go ahead.  I am more concerned
with keeping git master in a compilable state.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make doc fails

[Graham Percival]

On Sun, Aug 28, 2011 at 03:19:00AM +0100, Graham Percival wrote:
 On Sat, Aug 27, 2011 at 05:14:00PM +0100, Phil Holmes wrote:
  This afternoon I've done a fresh pull, make and make doc.  Make doc
  failed with this:
 
 Indeed.  It needed to run
   scripts/auxiliar/makelsr.py
 I've just done that, and will push once the build successfully
 finishes.

Mike.

Your commit
  Adds a Flag grob to LilyPond.
  f0978ed121192fee9bdf2453a325d98693148acf
introduced a syntax change with no convert-ly rule.  It also broke
compiling on git master.  I am now fixing stuff manually.  This is
not how I was planning on spending my 3am Sunday morning.


Unfortunately we cannot ask James to do a complete documentation
compile to test each patch, but as soon as I can build a release
again, I will create an automatic compiling checker.

- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

`make doc' fails

[Patrick McCarty]

Hello,

I can't run `make doc' due to a compile failure on git master (as of
commit 75cdeeefba1e4762a29b5f418b8d6294a0eba18e).

The relevant snippet that fails is in fretted-strings.itely:

  \version 2.13.42

  \include predefined-ukulele-fretboards.ly

  myChords = \chordmode { a1 a:m a:aug }

  \new ChordNames {
\myChords
  }

  \new FretBoards {
\set stringTunings = #ukulele-tuning
\myChords
  }

If I revert the latest commit (75cdeee), the compile failure is
resolved.

Valentin, do you have a fix for this?


Thanks,
Patrick

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: `make doc' fails

[Patrick McCarty]

On 2010-12-11, Patrick McCarty wrote:
 
 I can't run `make doc' due to a compile failure on git master (as of
 commit 75cdeeefba1e4762a29b5f418b8d6294a0eba18e).
 
 Valentin, do you have a fix for this?

The patch below seems to work.  Is this the correct fix?


diff --git a/ly/predefined-ukulele-fretboards.ly 
b/ly/predefined-ukulele-fretboards.ly
index 827b04d..1dc5fa4 100644
--- a/ly/predefined-ukulele-fretboards.ly
+++ b/ly/predefined-ukulele-fretboards.ly
@@ -22,8 +22,7 @@
    kiwi ukulele website (http://www.kiwiukulele.co.nz/)
 
 % chord definitions require default pitchnames
-#(define prev-pitchnames pitchnames)
-#(set! pitchnames default-language)
+\languageSaveAndChange #default-language
 
 %%% a chords
 
@@ -807,4 +806,4 @@
 #ukulele-tuning
 #1-1;o;2-3;1-2;
 
-#(set! pitchnames prev-pitchnames)
+\languageRestore



Thanks,
Patrick

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: `make doc' fails

[Valentin Villenave]

On Sat, Dec 11, 2010 at 11:17 PM, Patrick McCarty pnor...@gmail.com wrote:
 The patch below seems to work.  Is this the correct fix?

Of course! Please push asap.
I ran make check but it didn't occur to me that the ukulele needed to
be modified as well. Stupid me.

Cheers,
Valentin.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: `make doc' fails

[Patrick McCarty]

On 2010-12-12, Valentin Villenave wrote:
 On Sat, Dec 11, 2010 at 11:17 PM, Patrick McCarty pnor...@gmail.com wrote:
  The patch below seems to work.  Is this the correct fix?
 
 Of course! Please push asap.

Okay, pushed.

Thanks,
Patrick

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: `make doc' fails

[Valentin Villenave]

On Sun, Dec 12, 2010 at 12:19 AM, Patrick McCarty pnor...@gmail.com wrote:
 Okay, pushed.

Thanks! That was embarrassing.

Cheers,
Valentin.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: make doc fails on git

[Graham Percival]

On Thu, Dec 09, 2010 at 10:09:50AM -0700, Carl Sorensen wrote:
 I've got commit 16bdb67bb1ce1f52380b36e264869c2b61aa3553

I'm guessing that you fxied this in e7477, since git master looks
fine to me in 1ba780.  I just rebuilt everything from scratch with
no problems.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

make doc fails on git

[Carl Sorensen]

I've got commit 16bdb67bb1ce1f52380b36e264869c2b61aa3553

I did 

make clean  make

make doc-clean

make doc


I get this error:

Interpreting music...
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-20.otf
]
elapsed time: 0.01 seconds
Element count 113 (spanners 11)
Preprocessing graphical objects...
Grob count 221
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-11.otf
]
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-13.otf
]
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-14.otf
]
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-16.otf
]
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-18.otf
]
[/Users/Carl/lilypond/out/share/lilypond/current/fonts/otf/emmentaler-23.otf
]
[century_schoolbook_l_serif_3.0673828125command failed:
/Users/Carl/lilypond/out/bin/lilypond -dbackend=eps --formats=ps,png,pdf
-dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlede
--header=doctitlees --header=doctitlefr --header=doctitlehu
--header=doctitleit --header=doctitleja --header=doctitlenl --header=texidoc
--header=texidocde --header=texidoces --header=texidocfr --header=texidochu
--header=texidocit --header=texidocja --header=texidocnl
-dcheck-internal-types -ddump-signatures -danti-alias-factor=2 -I
/Users/Carl/lilypond/out/lybook-db  -I
/Users/Carl/lilypond/Documentation/fr  -I
/Users/Carl/lilypond/Documentation/fr  -I
/Users/Carl/lilypond/Documentation/fr/out-www  -I
/Users/Carl/lilypond/input  -I  /Users/Carl/lilypond/Documentation  -I
/Users/Carl/lilypond/Documentation/snippets  -I
/Users/Carl/lilypond/input/regression  -I
/Users/Carl/lilypond/Documentation/included  -I
/Users/Carl/lilypond/mf/out  -I  /Users/Carl/lilypond/mf/out  -I
/Users/Carl/lilypond/Documentation/pictures  -I
/Users/Carl/lilypond/Documentation/pictures/out-www  -I
/Users/Carl/lilypond/Documentation/fr/included  -I
/Users/Carl/lilypond/Documentation  -I
/Users/Carl/lilypond/Documentation/out-www --formats=eps  --verbose
-deps-box-padding=3.00  -dread-file-list -dno-strip-output-dir
/Users/Carl/lilypond/out/lybook-db/snippet-names-416147378.ly
Child was terminated by signal 10
make[3]: *** [out-www/notation.texi] Error 1
make[2]: *** [WWW-1] Error 2
rm out-www/weblinks.itexi
make[1]: *** [WWW-1] Error 2
make: *** [doc-stage-1] Error 2


Thanks,

Carl




___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: gub make doc fails

[Han-Wen Nienhuys]

Erik Sandberg wrote:

Hi,

gub seems to work fairly well now. However, there are some problems: make doc 
fails on the following snippet, seems to be a GC problem. A portion of the 
output is attached.


You can trouble shoot this in GDB - just set a breakpoint on abort().

Also, the patches I applied yesterday (updating \midi {\tempo}) are needed to 
finish make doc, but the autotester never complained about those files. Does 
this mean that there's a problem with the autotester?


I switched off the daily 'make doc-clean' routine, because it took too 
much time when trying to ship. Maybe I should reinstate.


--

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

gub make doc fails

[Erik Sandberg]

Hi,

gub seems to work fairly well now. However, there are some problems: make doc 
fails on the following snippet, seems to be a GC problem. A portion of the 
output is attached.

Also, the patches I applied yesterday (updating \midi {\tempo}) are needed to 
finish make doc, but the autotester never complained about those files. Does 
this mean that there's a problem with the autotester?

% 
% ly snippet:
% 
\sourcefileline 3262
\include gregorian-init.ly
\score {
  \transpose c c' {
% Punctum
\[ b \]
\noBreak s^\markup {a} \noBreak

% Punctum Inclinatum
\[ \inclinatum b \]
\noBreak s^\markup {b}
  }
\layout { \neumeDemoLayout }}


-- 
Erik
Invoking `gs   -dNOSAFER   -dEPSCrop  -dCompatibilityLevel=1.4  -dNOPAUSE -dBATCH -r1200  -sDEVICE=pdfwrite -sOutputFile=lily-1235349200-1.pdf -c .setpdfwrite -f lily-1235349200-1.eps'...GPL Ghostscript 8.50 (2005-12-31)
Copyright (C) 2005 artofcode LLC, Benicia, CA.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
WARNING: /Unicode /Decoding resource is not accessible but it is useful for generating ToUnicode CMap.

Layout output to `lily-1235349200.eps'...
Converting to `lily-1235349200.pdf'...
Invoking `gs   -dNOSAFER   -dEPSCrop  -dCompatibilityLevel=1.4  -dNOPAUSE -dBATCH -r1200  -sDEVICE=pdfwrite -sOutputFile=lily-1235349200.pdf -c .setpdfwrite -f lily-1235349200.eps'...GPL Ghostscript 8.50 (2005-12-31)
Copyright (C) 2005 artofcode LLC, Benicia, CA.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
WARNING: /Unicode /Decoding resource is not accessible but it is useful for generating ToUnicode CMap.

Converting to PNG...[/media/hda2/home/erik/lily/32gub/gub/target/linux/build/lilypond-HEAD/Documentation/user/out-www/lily-1235349200.eps]Invoking `gs  -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile=lily-1235349200.png -r202 lily-1235349200.eps -c quit'...
GPL Ghostscript 8.50 (2005-12-31)
Copyright (C) 2005 artofcode LLC, Benicia, CA.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Invoking `convert -scale 50.0% lily-1235349200.png.old lily-1235349200.png'...]
Processing `/media/hda2/home/erik/lily/32gub/gub/target/linux/build/lilypond-HEAD/Documentation/user/out-www/lily-2011765195.ly'
Parsing...[/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/init.ly[/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/declarations-init.ly[/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/music-functions-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/nederlands.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/drumpitch-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/chord-modifiers-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/script-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/scale-definitions-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/grace-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/midi-init.ly[/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/performer-init.ly]][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/paper-defaults.ly[/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/titling-init.ly]][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/engraver-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/dynamic-scripts-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/spanners-init.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/property-init.ly]][/media/hda2/home/erik/lily/32gub/gub/target/linux/build/lilypond-HEAD/Documentation/user/out-www/lily-2011765195.ly[/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/lilypond-book-preamble.ly][/media/hda2/home/erik/lily/32gub/gub/target/linux/installer-HEAD/usr/bin/../share/lilypond/current/ly/gregorian-init.ly]scm_unprotect_object called on unprotected object
command failed: /media/hda2