make doc

[Jean-Charles Malahieude]

Hi Phil,

I don't know if this is in relation with your work on 
extract_texi_filenames.py and don't remember if it was spitted before.


Many of the calls to this script, especially each time it will process 
an out-www/web.texi I get something weird with "searchpath":


No such file: file.itexi
Search path: .:./out-www:.

I'm in sync with 54b02666750062788185bd3f99e644d621e348c2

and about to push some xref-fixes on the French version.
If interested, the 10 Mo of logs are available.

Cheers,
Jean-Charles

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

'make doc' fails

[Arnout Engelen]

Hi,

'make doc' succeeds on the latest stable release, but not on the latest
development release (2.13.21) or latest git checkout. 


I'm afraid the console output got a bit truncated, but here it goes anyway:


Solving 1 page-breaking chunks...
[century_schoolbook_l_serif_3.443359375]
[monospace_3.443359375][1: 3 or 4 pages]
Drawing systems...
[century_schoolbook_l_serif_italic_4.337890625]
[century_schoolbook_l_serif_italic_3.0673828125]
Element count 5546
Element count 2501
Element count 6274
Layout output to `./ee/lily-37358517.eps'...
Converting to `./ee/lily-37358517.pdf'...
Invoking `gs  -dNOSAFER -dEPSCrop -dCompatibilityLevelsDEVICE=pdfwrite
-sOutputFile="./ee/lily-37358517.pdf"37358517.eps"'...GPL Ghostscript 8.71
(2010-02-10)
Copyright (C) 2010 Artifex Software, Inc.  All rights 
This software comes with NO WARRANTY: see the file PUB

Converting to PNG...[././ee/lily-37358517.eps]
Invoking `gs  -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlg16m
-sOutputFile="./ee/lily-37358517.png" -r202 "./ee
GPL Ghostscript 8.71 (2010-02-10)
Copyright (C) 2010 Artifex Software, Inc.  All rights 
This software comes with NO WARRANTY: see the file PUB
Invoking `pngtopnm ./ee/lily-37358517.png.old | pnmscaopng -compression 9
2>/dev/null > ./ee/lily-37358517.p
pngtopnm: EOF / write error writing a row of pixels
GS exited with status: 256command failed: /home/arnoutd -I ./ -I ./out-www -I
../../input -I /home/arnouten/home/arnouten/dev/lilypond/Documentation/snippets
-I ./arnouten/dev/lilypond/Documentation/included/ -I /hom -I
/home/arnouten/dev/lilypond/mf/out/ -I /home/arnoupictures -I
/home/arnouten/dev/lilypond/Documentation/s --formats=ps,png,pdf 
-dinclude-eps-fonts -dgs-load-r=doctitlede --header=doctitlees
--header=doctitlefr -titleit --header=doctitleja --header=doctitlenl
--head-header=texidoces --header=texidocfr --header=texidochexidocja
--header=texidocnl -dcheck-internal-types -ddtor=2 -I 
"/home/arnouten/dev/lilypond/out/lybook-db" nd/input/regression"  -I 
"/home/arnouten/dev/lilypondarnouten/dev/lilypond/input/regression/out-www"  -I
 "ut"  -I  "/home/arnouten/dev/lilypond/Documentation" 
d/Documentation/snippets"  -I 
"/home/arnouten/dev/lilhome/arnouten/dev/lilypond/Documentation/included" 
-Imf/out"  -I  "/home/arnouten/dev/lilypond/mf/out"  -I ocumentation/pictures" 
-I  "/home/arnouten/dev/lilypoww" --formats=eps  --verbose 
-deps-box-padding=3.-output-dir  "/home/arnouten/dev/lilypond/out/lybook-d
Child returned 1
make[3]: *** [out-www/collated-files.texi] Error 1
make[3]: Leaving directory `/home/arnouten/dev/lilypon
make[2]: *** [WWW-1] Error 2
make[2]: Leaving directory `/home/arnouten/dev/lilypon
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/arnouten/dev/lilypon
make: *** [doc-stage-1] Error 2



Kind regards,

Arnout Engelen


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

Re: make doc

[Graham Percival]

On Sun, Jul 31, 2011 at 06:29:33PM +0200, Jean-Charles Malahieude wrote:
> No such file: file.itexi
> Search path: .:./out-www:.

Extremely normal; happens all the time.  :(

Cheers,
- Graham

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

Re: make doc

[Jean-Charles Malahieude]

Le 01/08/2011 05:11, Graham Percival disait :

On Sun, Jul 31, 2011 at 06:29:33PM +0200, Jean-Charles Malahieude wrote:

No such file: file.itexi
Search path: .:./out-www:.


Extremely normal; happens all the time.  :(



Sorry to have disturbed, I had not noticed this manner to label the path.

Cheers,
Jean-Charles

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

RE: make doc

[James Lowe]

Hello,

)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Jean-Charles Malahieude
)Sent: 01 August 2011 18:07
)To: Graham Percival
)Cc: Lily Bugs; lilypond-devel
)Subject: Re: make doc
)
)Le 01/08/2011 05:11, Graham Percival disait :
)> On Sun, Jul 31, 2011 at 06:29:33PM +0200, Jean-Charles Malahieude
)wrote:
)>> No such file: file.itexi
)>> Search path: .:./out-www:.
)>
)> Extremely normal; happens all the time.  :(
)>
)
)Sorry to have disturbed, I had not noticed this manner to label the path.
)
---

Don't worry once we've done GOP 5, 'super Phil' will fix our doc build process 
- I have every confidence ;)

James

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

make doc problem

[Jean-Charles Malahieude]

Hi all!

Not only that I can no longer use "-j" on a first build (it is OK
on the next builds), which means 40' for a "make doc LANGS='fr' and
about 2 hours for all languages, I now have to "make doc-clean" in
order to view a corrected typo. I've tried a "touch masterfile.tely"
before "make doc" but it doesn't change anything.

Does anybody else experiment this as well?

Cheers,
Jean-Charles

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

Re: 'make doc' fails

[Graham Percival]

On Sun, May 16, 2010 at 09:38:45PM +, Arnout Engelen wrote:
> Invoking `pngtopnm ./ee/lily-37358517.png.old | pnmscaopng -compression 9
> 2>/dev/null > ./ee/lily-37358517.p
> pngtopnm: EOF / write error writing a row of pixels
> GS exited with status: 256command failed: /home/arnoutd -I ./ -I ./out-www -I
> ../../input -I 
> /home/arnouten/home/arnouten/dev/lilypond/Documentation/snippets

Interesting; it worked over here (otherwise I couldn't have
uploaded the release).

What version of ghostscript and netpbm do you have?


also, does this happen near the beginning of the docs?  Hmm,
actually, I see this is inside the snippets.  What happens if you
try

  cd Documentation/snippets/
  for f in *.ly; do lilypond $f ; done;

?  Do all the snippets compile that way?  If not, knowing the
failing snippet name would help.

(actually, faster solution: the file
  out/lybook-db/ee/lily-37358517.ly
might contain hints about the original filename)


Cheers,
- Graham


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

Re: make doc problem

[Phil Holmes]

- Original Message - 
From: "Jean-Charles Malahieude" 
To: "Lily Bugs" ; "lilypond-devel" 
; "Julien Rioux" 

Sent: Sunday, January 22, 2012 6:19 PM
Subject: make doc problem



Hi all!

Not only that I can no longer use "-j" on a first build (it is OK
on the next builds), which means 40' for a "make doc LANGS='fr' and
about 2 hours for all languages, I now have to "make doc-clean" in
order to view a corrected typo. I've tried a "touch masterfile.tely"
before "make doc" but it doesn't change anything.

Does anybody else experiment this as well?

Cheers,
Jean-Charles



I've run a few with -j9 CPU_COUNT=9 this afternoon with no problems.  The 
only oddity I've noticed is that make doc make doc now seems to rebuild a 
lot of files the second run.


--
Phil Holmes



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

Re: make doc problem

[Julien Rioux]

On 22/01/2012 1:19 PM, Jean-Charles Malahieude wrote:

Hi all!

Not only that I can no longer use "-j" on a first build (it is OK
on the next builds), which means 40' for a "make doc LANGS='fr' and
about 2 hours for all languages, I now have to "make doc-clean" in
order to view a corrected typo. I've tried a "touch masterfile.tely"
before "make doc" but it doesn't change anything.

Does anybody else experiment this as well?

Cheers,
Jean-Charles


Hi Jean-Charles,

I can't run -j, I have a single core. Can you please report more 
precisely why you can no longer use it?


The second issue I have not seen. If I correct a typo in a file in 
Documentation then make doc will rebuild it. OK I should check 
Documentation/fr right now...


Regards,
Julien

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

Re: make doc problem

[Julien Rioux]

On 22/01/2012 1:30 PM, Phil Holmes wrote:

I've run a few with -j9 CPU_COUNT=9 this afternoon with no problems. The
only oddity I've noticed is that make doc make doc now seems to rebuild
a lot of files the second run.

--
Phil Holmes




I've hit a roadblock with issue 2125 which attempted to fix that make 
doc; make doc problem. With that patch, on my machine the second make 
doc reports `nothing to be done'. So it works on my machine but not 
yours and I haven't quite figured it out yet.


Regards,
Julien

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

Re: make doc problem

[Phil Holmes]

- Original Message - 
From: "Julien Rioux" 

To: "Phil Holmes" 
Cc: "Jean-Charles Malahieude" ; "LilyPond Bugs" 
; "LilyPond Devel" 

Sent: Sunday, January 22, 2012 6:35 PM
Subject: Re: make doc problem



On 22/01/2012 1:30 PM, Phil Holmes wrote:

I've run a few with -j9 CPU_COUNT=9 this afternoon with no problems. The
only oddity I've noticed is that make doc make doc now seems to rebuild
a lot of files the second run.

--
Phil Holmes




I've hit a roadblock with issue 2125 which attempted to fix that make doc; 
make doc problem. With that patch, on my machine the second make doc 
reports `nothing to be done'. So it works on my machine but not yours and 
I haven't quite figured it out yet.


Regards,
Julien



Please shout if you want logfiles or testing.  I can run tests fairly 
quickly if I've got my lily machine up and running.


--
Phil Holmes



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

Re: make doc problem

[Julien Rioux]

On 22/01/2012 1:32 PM, Julien Rioux wrote:

The second issue I have not seen. If I correct a typo in a file in
Documentation then make doc will rebuild it. OK I should check
Documentation/fr right now...



When I edit Documentation/fr/essay/literature.itely and issue a make doc 
from within build/Documentation/fr then Documentation/fr/essay.tely is 
recompiled. I can see the result in Documentation/fr/out-www/essay/* and 
in Documentation/out-www/essay.fr.* [1]


Please report in more details the problems that you encounter, e.g. 
which file are you modifying and how are you calling make.


Thanks,
Regards,
Julien

[1] Big side note: It doesn't work flawlessly: notation.tely and a bunch 
of other manuals are also recompiled when they shouldn't, since I didn't 
touch any of their source files. This problem I trace back to the 
CHAIN_RULE in make/ly-rules.make, which I didn't dare touch up to now. 
This rule states that web depends on usage depends on notation depends 
on... etc. so that only one instance of lilypond-book is running at once 
on any given manual. As a side-effect it means that manuals depend on 
each other when that isn't in fact the case.


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

Re: make doc problem

[Jean-Charles Malahieude]

Le 22/01/2012 19:32, Julien Rioux disait :

On 22/01/2012 1:19 PM, Jean-Charles Malahieude wrote:

Hi all!

Not only that I can no longer use "-j" on a first build (it is OK
on the next builds), [...]



I can't run -j, I have a single core. Can you please report more
precisely why you can no longer use it?



I make a clean and let you now...

--
Jean-Charles

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

Re: make doc problem

[Julien Rioux]

On 22/01/2012 2:11 PM, Jean-Charles Malahieude wrote:

What I've done to check is:
open Documentation/fr/usage/running.itely

add the five X at the beginning of the first text line

XCe chapitre passe en revue ce qui se passe lorsque vous lancez
LilyPond.

save it and "make -j3 doc LANGS='fr'"

File out-www/offline-root/Documentation/usage/running-lilypond.fr.html
still shows
"Ce chapitre passe en revue ce qui se passe lorsque vous lancez LilyPond."

--
Jean-Charles


You're right, I forgot that I caused that. Give me a moment I will push 
the fix to staging...


Regards,
Julien

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

Re: make doc problem

[Julien Rioux]

On 22/01/2012 2:15 PM, Julien Rioux wrote:

On 22/01/2012 2:11 PM, Jean-Charles Malahieude wrote:

What I've done to check is:
open Documentation/fr/usage/running.itely

add the five X at the beginning of the first text line

XCe chapitre passe en revue ce qui se passe lorsque vous lancez
LilyPond.

save it and "make -j3 doc LANGS='fr'"

File out-www/offline-root/Documentation/usage/running-lilypond.fr.html
still shows
"Ce chapitre passe en revue ce qui se passe lorsque vous lancez
LilyPond."

--
Jean-Charles


You're right, I forgot that I caused that. Give me a moment I will push
the fix to staging...

Regards,
Julien


Done: 930dbeff8f5d31faa9654365c8ed84a30e489e83

Hope this fixes it for you as well.

Thanks,
Julien

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

Re: make doc problem

[David Kastrup]

Julien Rioux  writes:

> I can't run -j, I have a single core.

This is factually incorrect.  You can run -j just fine, but you can't
expect much of a speedup.  On a single-core machine,

make -j 2

typically gives you a speedup of maybe 15% (given sufficient memory)
since the CPU can keep busy on processing a second job when the other
job is waiting for the disk to provide new input.

More importantly, you'll get to see the same kind of problems that the
true multi-core people experience when using -j.

So very much recommended for testing.

-- 
David Kastrup


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

Re: make doc problem

[Jean-Charles Malahieude]

Le 22/01/2012 20:22, Julien Rioux disait :

On 22/01/2012 2:15 PM, Julien Rioux wrote:

On 22/01/2012 2:11 PM, Jean-Charles Malahieude wrote:

What I've done to check is:
open Documentation/fr/usage/running.itely

add the five X at the beginning of the first text line

XCe chapitre passe en revue ce qui se passe lorsque vous lancez
LilyPond.

save it and "make -j3 doc LANGS='fr'"

File out-www/offline-root/Documentation/usage/running-lilypond.fr.html
still shows
"Ce chapitre passe en revue ce qui se passe lorsque vous lancez
LilyPond."

--
Jean-Charles


You're right, I forgot that I caused that. Give me a moment I will push
the fix to staging...

Regards,
Julien


Done: 930dbeff8f5d31faa9654365c8ed84a30e489e83

Hope this fixes it for you as well.



Yes, many thanks!

--
Jean-Charles


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

Re: make doc problem

[Julien Rioux]

On 22/01/2012 2:38 PM, David Kastrup wrote:

Julien Rioux  writes:


I can't run -j, I have a single core.


This is factually incorrect.  You can run -j just fine, but you can't
expect much of a speedup.  On a single-core machine,

make -j 2

typically gives you a speedup of maybe 15% (given sufficient memory)
since the CPU can keep busy on processing a second job when the other
job is waiting for the disk to provide new input.

More importantly, you'll get to see the same kind of problems that the
true multi-core people experience when using -j.

So very much recommended for testing.



Thanks, you're quite right CPU is not the limiting factor for the build. 
Disk access and usage of swap when compiling 
input/regression/collated-files slows down the build to a crawl for me.


--
Julien

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

Re: make doc problem

[David Kastrup]

Julien Rioux  writes:

> Thanks, you're quite right CPU is not the limiting factor for the
> build. Disk access and usage of swap when compiling
> input/regression/collated-files slows down the build to a crawl for
> me.

If it is really usage of swap: getting more memory will be by far the
cheapest method of speeding up your computer much more than buying a
faster CPU ever could.

-- 
David Kastrup


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

Re: make doc problem

[Phil Holmes]

"Julien Rioux"  wrote in message 
news:4f1c6a79.3040...@physics.utoronto.ca...

On 22/01/2012 2:38 PM, David Kastrup wrote:

Julien Rioux  writes:


I can't run -j, I have a single core.


This is factually incorrect.  You can run -j just fine, but you can't
expect much of a speedup.  On a single-core machine,

make -j 2

typically gives you a speedup of maybe 15% (given sufficient memory)
since the CPU can keep busy on processing a second job when the other
job is waiting for the disk to provide new input.

More importantly, you'll get to see the same kind of problems that the
true multi-core people experience when using -j.

So very much recommended for testing.



Thanks, you're quite right CPU is not the limiting factor for the build. 
Disk access and usage of swap when compiling 
input/regression/collated-files slows down the build to a crawl for me.


--
Julien


As a general rule, CPU is very much the limiting factor on make and make 
doc.  With my "single cpu" virtual machine on my Windows box, the CPU is 
stuck at 100%.  With my multi-core Ubuntu box, most of the time all 8 CPUs 
run 100%, with memory never over 1.5 Gigs.  This is using a fairly large 
SSD, but I'm 99% certain that, all other things being equal, CPU is king 
when building lily.


--
Phil Holmes
Bug Squad




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

Re: make doc problem

[Reinhold Kainhofer]

On 22/01/2012 20:58, Julien Rioux wrote:
> Thanks, you're quite right CPU is not the limiting factor for the
> build. Disk access and usage of swap when compiling
> input/regression/collated-files slows down the build to a crawl for me.

The problem here is that lilypond builds up memory from 400MB to ~1GB
without releasing...
Most of these allocations don't seem to be memory leaks, but rather due
to guile.

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


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

Re: make doc problem

[Phil Holmes]

- Original Message - 
From: "Reinhold Kainhofer" 

To: "Julien Rioux" 
Cc: ; 
Sent: Thursday, January 26, 2012 4:13 PM
Subject: Re: make doc problem



On 22/01/2012 20:58, Julien Rioux wrote:

Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.


The problem here is that lilypond builds up memory from 400MB to ~1GB
without releasing...
Most of these allocations don't seem to be memory leaks, but rather due
to guile.

Cheers,
Reinhold


It only takes that amount of memory for big builds.  I've never seen much 
over 1 Gig total memory during a make with 8 CPUs all running lilypond.


--
Phil Holmes



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

Re: make doc problem

[Julien Rioux]

On 22/01/2012 2:58 PM, Julien Rioux wrote:

Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.



Could we redistribute the regression test input files into subfolders of 
say ~50 files each, possibly sorting them into categories if it makes sense?


--
Julien

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

Re: make doc problem

[Julien Rioux]

On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:

On 22/01/2012 20:58, Julien Rioux wrote:

Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.


The problem here is that lilypond builds up memory from 400MB to ~1GB
without releasing...
Most of these allocations don't seem to be memory leaks, but rather due
to guile.

Cheers,
Reinhold



Is it a bug? We're talking about lilypond running with the 
-dread-input-files flag here. Once a snippet has been processed and 
lilypond moves on to the next one, there is no reason to hold onto the 
memory used by the previous snippet, right?


--
Julien

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

Re: make doc problem

[Graham Percival]

On Thu, Jan 26, 2012 at 05:57:43PM -0500, Julien Rioux wrote:
> On 22/01/2012 2:58 PM, Julien Rioux wrote:
> >Thanks, you're quite right CPU is not the limiting factor for the build.
> >Disk access and usage of swap when compiling
> >input/regression/collated-files slows down the build to a crawl for me.
> 
> Could we redistribute the regression test input files into
> subfolders of say ~50 files each, possibly sorting them into
> categories if it makes sense?

Wanted to do that for ages, but that's not something to get into
now.  But this shouldn't be an issue -- don't we split it into
lists of IIRC 300 files?  We had some kind of emergency bugfix
like that.
... yeah, see make/lysdoc-rules.make

You may want to look into that; perhaps changing the division from
300 to 50 would speed up the build?

- Graham

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

Re: make doc problem

[Julien Rioux]

On 26/01/2012 6:14 PM, Graham Percival wrote:

On Thu, Jan 26, 2012 at 05:57:43PM -0500, Julien Rioux wrote:

On 22/01/2012 2:58 PM, Julien Rioux wrote:

Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.


Could we redistribute the regression test input files into
subfolders of say ~50 files each, possibly sorting them into
categories if it makes sense?


Wanted to do that for ages, but that's not something to get into
now.  But this shouldn't be an issue -- don't we split it into
lists of IIRC 300 files?  We had some kind of emergency bugfix
like that.
... yeah, see make/lysdoc-rules.make

You may want to look into that; perhaps changing the division from
300 to 50 would speed up the build?

- Graham


The `echo' command-line is broken down into 300-file chunks. They all 
still end up into one collated-files.tely


Anyway, it kind of sounds like a workaround or an emergency action as 
you say. Were the memory released at each snippet then it shouldn't be 
an issue.


Cheers,
Julien

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

Re: make doc problem

[Phil Holmes]

- Original Message - 
From: "Julien Rioux" 

To: 
Cc: 
Sent: Thursday, January 26, 2012 11:00 PM
Subject: Re: make doc problem



On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:

On 22/01/2012 20:58, Julien Rioux wrote:

Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.


The problem here is that lilypond builds up memory from 400MB to ~1GB
without releasing...
Most of these allocations don't seem to be memory leaks, but rather due
to guile.

Cheers,
Reinhold



Is it a bug? We're talking about lilypond running with 
the -dread-input-files flag here. Once a snippet has been processed and 
lilypond moves on to the next one, there is no reason to hold onto the 
memory used by the previous snippet, right?


--
Julien



I'm trying to look at memory usage on my Ubuntu box.  If I watch the build 
using System Monitor, I rarely see more than a gig used.  However, using 
"free" even my dormant machine is now showing 3 Gigs used.  Is this because 
I have around 2 Gigs marked as "cache"?  Is the actual in-use memory 
used-cache?


--
Phil Holmes



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

Re: make doc problem

[Phil Holmes]

- Original Message - 
From: "Phil Holmes" 

To: ; "Julien Rioux" 
Cc: 
Sent: Friday, January 27, 2012 1:38 PM
Subject: Re: make doc problem


- Original Message - 
From: "Julien Rioux" 

To: 
Cc: 
Sent: Thursday, January 26, 2012 11:00 PM
Subject: Re: make doc problem



On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:

On 22/01/2012 20:58, Julien Rioux wrote:

Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.


The problem here is that lilypond builds up memory from 400MB to ~1GB
without releasing...
Most of these allocations don't seem to be memory leaks, but rather due
to guile.

Cheers,
Reinhold



Is it a bug? We're talking about lilypond running with 
the -dread-input-files flag here. Once a snippet has been processed and 
lilypond moves on to the next one, there is no reason to hold onto the 
memory used by the previous snippet, right?


--
Julien



I'm trying to look at memory usage on my Ubuntu box.  If I watch the build 
using System Monitor, I rarely see more than a gig used.  However, using 
"free" even my dormant machine is now showing 3 Gigs used.  Is this 
because I have around 2 Gigs marked as "cache"?  Is the actual in-use 
memory used-cache?



Here's a graph of used-cache, which fits well with my observations of system 
monitor.  My machine when lying dormant having finished make/make doc uses 
970 MiB memory.  The peak I saw during make doc was 2.4 Gig.  So make doc 
takes around 1.4 Gigs when doing its greatest processing with 8 parallel 
processors.  Is this too much for your machine, Julien?  If it's a desktop, 
4 Gigs of memory is about £30 now, which might be a simpler solution than 
messing with how make doc runs.


--
Phil Holmes

<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

make doc-stage-1 barfs

[Ian Hulin]

Hi all I'm running make doc-stage-1 after

$ cd build
$ git checkout master
$ ../configure --disable-optimising
$ make
$ make test-baseline
$ git checkout T2026-1
$ make test-clean
$ make check
$ make doc-clean
Make doc-clean fails with:
.
.
.
/home/ian/src/lilypond/stepmake/stepmake/generic-targets.make:140:
warning: ignoring old commands for target `install'
rm -rf ./out-www
make PACKAGE=LILYPOND package=lilypond -C bin clean &&  make
PACKAGE=LILYPOND package=lilypond -C stepmake clean && true
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/bin'
rm -rf ./out-www
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/bin'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/stepmake'
rm -rf ./out-www
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/stepmake'
make[2]: Leaving directory `/home/ian/src/lilypond/build/stepmake'
make[2]: Entering directory `/home/ian/src/lilypond/build/Documentation'
out-www/version.dep:1: *** missing separator.  Stop.
make[2]: Leaving directory `/home/ian/src/lilypond/build/Documentation'
make[1]: *** [clean] Error 2
make[1]: Leaving directory `/home/ian/src/lilypond/build'
make: *** [doc-clean] Error 2
ian@nanny-ogg ~/src/lilypond/build (T2026-1)$
$ make doc-stage-1
This also fails with the following log tail.
.
.
.
writing: /home/ian/src/lilypond/build/./out-www/xref-maps/INSTALL.xref-map
make PACKAGE=LILYPOND package=lilypond -C bin WWW-1 &&  make
PACKAGE=LILYPOND package=lilypond -C stepmake WWW-1 && true
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/bin'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/bin'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/bin'
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/bin'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/stepmake'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/stepmake'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/stepmake'
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/stepmake'
make[2]: Leaving directory `/home/ian/src/lilypond/build/stepmake'
make[2]: Entering directory `/home/ian/src/lilypond/build/Documentation'
out-www/version.dep:1: *** missing separator.  Stop.
make[2]: Leaving directory `/home/ian/src/lilypond/build/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/ian/src/lilypond/build'
make: *** [doc-stage-1] Error 2
ian@nanny-ogg ~/src/lilypond/build (T2026-1)$

Any pointers on how to do a docs build without this happening? Is there
a known problem with the makefiles here, and if so how do I work round it?

Cheers,

Ian


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

Re: make doc-stage-1 barfs

[Julien Rioux]

On 11/01/2012 3:58 PM, Ian Hulin wrote:

Hi all I'm running make doc-stage-1 after

$ cd build
$ git checkout master
$ ../configure --disable-optimising
$ make
$ make test-baseline
$ git checkout T2026-1
$ make test-clean
$ make check
$ make doc-clean
Make doc-clean fails with:
.
.
.
/home/ian/src/lilypond/stepmake/stepmake/generic-targets.make:140:
warning: ignoring old commands for target `install'
rm -rf ./out-www
make PACKAGE=LILYPOND package=lilypond -C bin clean&&   make
PACKAGE=LILYPOND package=lilypond -C stepmake clean&&  true
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/bin'
rm -rf ./out-www
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/bin'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/stepmake'
rm -rf ./out-www
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/stepmake'
make[2]: Leaving directory `/home/ian/src/lilypond/build/stepmake'
make[2]: Entering directory `/home/ian/src/lilypond/build/Documentation'
out-www/version.dep:1: *** missing separator.  Stop.
make[2]: Leaving directory `/home/ian/src/lilypond/build/Documentation'
make[1]: *** [clean] Error 2
make[1]: Leaving directory `/home/ian/src/lilypond/build'
make: *** [doc-clean] Error 2
ian@nanny-ogg ~/src/lilypond/build (T2026-1)$
$ make doc-stage-1
This also fails with the following log tail.
.
.
.
writing: /home/ian/src/lilypond/build/./out-www/xref-maps/INSTALL.xref-map
make PACKAGE=LILYPOND package=lilypond -C bin WWW-1&&   make
PACKAGE=LILYPOND package=lilypond -C stepmake WWW-1&&  true
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/bin'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*'>  ./out-www/.gitignore
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/bin'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/bin'
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/bin'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/stepmake'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*'>  ./out-www/.gitignore
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/stepmake'
make[3]: Entering directory `/home/ian/src/lilypond/build/stepmake/stepmake'
true
make[3]: Leaving directory `/home/ian/src/lilypond/build/stepmake/stepmake'
make[2]: Leaving directory `/home/ian/src/lilypond/build/stepmake'
make[2]: Entering directory `/home/ian/src/lilypond/build/Documentation'
out-www/version.dep:1: *** missing separator.  Stop.
make[2]: Leaving directory `/home/ian/src/lilypond/build/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/ian/src/lilypond/build'
make: *** [doc-stage-1] Error 2
ian@nanny-ogg ~/src/lilypond/build (T2026-1)$

Any pointers on how to do a docs build without this happening? Is there
a known problem with the makefiles here, and if so how do I work round it?

Cheers,

Ian


Various .dep files are created to track dependencies on files. They are 
being read by make, which expects a particular syntax. In the case of 
the file /home/ian/src/lilypond/build/Documentation/out-www/version.dep 
there is a syntax error in it. To get further you can safely delete the 
file. It would also be interesting to see its content, if you may share 
that file here, as I don't see a version.dep in my local build dir.


Regards,
Julien


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

Re: make doc-stage-1 barfs

[Ian Hulin]

Hi Julien,
On 11/01/12 21:48, Julien Rioux wrote:
> On 11/01/2012 3:58 PM, Ian Hulin wrote:
>> Hi all I'm running make doc-stage-1 after
>> 
>> $ cd build $ git checkout master $ ../configure
>> --disable-optimising $ make $ make test-baseline $ git checkout
>> T2026-1 $ make test-clean $ make check $ make doc-clean Make
>> doc-clean fails with: . . . 
>> /home/ian/src/lilypond/stepmake/stepmake/generic-targets.make:140:
>>
>> 
warning: ignoring old commands for target `install'
>> rm -rf ./out-www make PACKAGE=LILYPOND package=lilypond -C bin
>> clean&&   make PACKAGE=LILYPOND package=lilypond -C stepmake
>> clean&&  true make[3]: Entering directory
>> `/home/ian/src/lilypond/build/stepmake/bin' rm -rf ./out-www 
>> true make[3]: Leaving directory
>> `/home/ian/src/lilypond/build/stepmake/bin' make[3]: Entering
>> directory `/home/ian/src/lilypond/build/stepmake/stepmake' rm -rf
>> ./out-www true make[3]: Leaving directory 
>> `/home/ian/src/lilypond/build/stepmake/stepmake' make[2]: Leaving
>> directory `/home/ian/src/lilypond/build/stepmake' make[2]:
>> Entering directory `/home/ian/src/lilypond/build/Documentation' 
>> out-www/version.dep:1: *** missing separator.  Stop. make[2]:
>> Leaving directory `/home/ian/src/lilypond/build/Documentation' 
>> make[1]: *** [clean] Error 2 make[1]: Leaving directory
>> `/home/ian/src/lilypond/build' make: *** [doc-clean] Error 2 
>> ian@nanny-ogg ~/src/lilypond/build (T2026-1)$ $ make doc-stage-1 
>> This also fails with the following log tail. . . . writing: 
>> /home/ian/src/lilypond/build/./out-www/xref-maps/INSTALL.xref-map
>>
>> 
make PACKAGE=LILYPOND package=lilypond -C bin WWW-1&&   make
>> PACKAGE=LILYPOND package=lilypond -C stepmake WWW-1&&  true 
>> make[3]: Entering directory
>> `/home/ian/src/lilypond/build/stepmake/bin' mkdir -p ./out-www 
>> touch ./out-www/dummy.dep echo '*'>  ./out-www/.gitignore 
>> make[3]: Leaving directory
>> `/home/ian/src/lilypond/build/stepmake/bin' make[3]: Entering
>> directory `/home/ian/src/lilypond/build/stepmake/bin' true 
>> make[3]: Leaving directory
>> `/home/ian/src/lilypond/build/stepmake/bin' make[3]: Entering
>> directory `/home/ian/src/lilypond/build/stepmake/stepmake' mkdir
>> -p ./out-www touch ./out-www/dummy.dep echo '*'>
>> ./out-www/.gitignore make[3]: Leaving directory 
>> `/home/ian/src/lilypond/build/stepmake/stepmake' make[3]:
>> Entering directory 
>> `/home/ian/src/lilypond/build/stepmake/stepmake' true make[3]:
>> Leaving directory 
>> `/home/ian/src/lilypond/build/stepmake/stepmake' make[2]: Leaving
>> directory `/home/ian/src/lilypond/build/stepmake' make[2]:
>> Entering directory `/home/ian/src/lilypond/build/Documentation' 
>> out-www/version.dep:1: *** missing separator.  Stop. make[2]:
>> Leaving directory `/home/ian/src/lilypond/build/Documentation' 
>> make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory
>> `/home/ian/src/lilypond/build' make: *** [doc-stage-1] Error 2 
>> ian@nanny-ogg ~/src/lilypond/build (T2026-1)$
>> 
>> Any pointers on how to do a docs build without this happening? Is
>> there a known problem with the makefiles here, and if so how do I
>> work round it?
>> 
>> Cheers,
>> 
>> Ian
> 
> Various .dep files are created to track dependencies on files. They
> are being read by make, which expects a particular syntax. In the
> case of the file
> /home/ian/src/lilypond/build/Documentation/out-www/version.dep 
> there is a syntax error in it. To get further you can safely delete
> the file. It would also be interesting to see its content, if you
> may share that file here, as I don't see a version.dep in my local
> build dir.
> 
> Regards, Julien
No, it looks like Documentation/out-www/version.dep was never created.

It looks like I've been able to work round the problem by backing up
the old build directory, recreating it with makedir, doing
$ ../configure --disable-optimising
$ make
and *then* doing the
$ make doc
*before* attempting to do
$ make check

Doc build is currently chuntering through the French and Dutch
versions of the web pictures as I type.

Look like make check does something to fool make doc it has provided
Documentation/out-www/version.dep when in fact it hasn't.

Cheers,

Ian


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

Issue 1832 in lilypond: make doc broken

[lilypond]

Status: Accepted
Owner: 
Labels: Type-Critical Regression

New issue 1832 by philehol...@googlemail.com: make doc broken
http://code.google.com/p/lilypond/issues/detail?id=1832

On at least 2 Ubuntu systems (Phil and Colin) make doc no longer works - it  
ends with this output:


/home/phil/lilypond-git/build/out/lybook-db  
--load-custom-package=book-musicxml-testsuite.py

out-www/collated-files.tely
langdefs.py: warning: lilypond-doc gettext domain not found.
Traceback (most recent call last):
  File "/home/phil/lilypond-git/scripts/lilypond-book.py", line 693, in

main ()
  File "/home/phil/lilypond-git/scripts/lilypond-book.py", line 624, in main
files = do_options ()
  File "/home/phil/lilypond-git/scripts/lilypond-book.py", line 610, in
do_options
print imp.load_source ("book_custom_package%s" % nr, i)
IOError: [Errno 2] No such file or directory
make[4]: *** [out-www/collated-files.texi] Error 1
make[4]: Leaving directory
`/home/phil/lilypond-git/build/input/regression/musicxml'

This is a change in input/regression/musicxml/GNUmakefile:

LILYPOND_BOOK_FLAGS += --load-custom-package=book-musicxml-testsuite.py
 added with commit cfcb9efdbd7c6600fc89fc912ba80529010b31e7 .  Reinhold is  
aware of the problem, but with more than one user affected it should be  
tracked.  Docs can be made temporarily by commenting out the added line in  
the GNUmakefile




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

Issue 2416 in lilypond: make doc documentation

[lilypond]

Status: Accepted
Owner: 
Labels: Type-Documentation

New issue 2416 by philehol...@gmail.com: make doc documentation
http://code.google.com/p/lilypond/issues/detail?id=2416

Following the work by (mainly) Julien, make doc is now in pretty good  
shape.  Changing a documentation file and re-running make doc should  
regenerate the document that uses that file.  make doc clean should allow a  
further make doc to be run satisfactorily.


http://lilypond.org/doc/v2.15/Documentation/contributor/generating-documentation

does not acknowledge the improvements and should be updated.


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

run make doc without regtest? (issue 4180)

[Federico Bruni]

I cannot compile 'make doc' because of issue 4180.
IIUC the regtests are run automatically before compiling the 
documentation? How can I avoid that?


Thanks
Federico


%% Generated by lilypond-book.py
%% Options: [exampleindent=10.16\mm,indent=0\mm,line-width=160\mm]
\include "lilypond-book-preamble.ly"


% 
% Start cut-&-pastable-section
% 



\paper {
  indent = 0\mm
  line-width = 160\mm
  % offset the left padding, also add 1mm as lilypond creates cropped
  % images with a little space on the right
  line-width = #(- line-width (* mm  3.00) (* mm 1))
}

\layout {
  
}





% 
% ly snippet:
% 
\sourcefilename "time-signature-single-digit.ly"
\sourcefileline 0
\version "2.19.16"

\header {
  texidoc = "The single-digit time signature style prints the numerator only."
}

\new Staff {
  \relative d' {
\override Staff.TimeSignature.style = #'single-digit
\time 1/2 d2
\time 2/4 d2
\time 3/4 d2.
\time 8/1024 d128
\time 9/1 d1
  }
}



% 
% end ly snippet
% 
Log level set to 287
GNU LilyPond 2.19.16
Relocation : from cwd: argv0=out/bin/lilypond
PATH=/home/fede/lilypond-git/out/bin (prepend)
Setting PATH to /home/fede/lilypond-git/out/bin:/home/fede/lilypond-git/scripts/auxiliar:/home/fede/git-cl:/home/fede/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/fede/node_modules/beautiful-docs/bin
Relocation: compile datadir=, new datadir=/home/fede/lilypond-git/out/share/lilypond//current
Relocation: framework_prefix=/home/fede/lilypond-git/out/bin/..
Setting INSTALLER_PREFIX to /home/fede/lilypond-git/out/bin/..
PATH=/home/fede/lilypond-git/out/bin/../bin (prepend)
Setting PATH to /home/fede/lilypond-git/out/bin/../bin:/home/fede/lilypond-git/out/bin:/home/fede/lilypond-git/scripts/auxiliar:/home/fede/git-cl:/home/fede/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/fede/node_modules/beautiful-docs/bin
Setting GUILE_MIN_YIELD_1 to 65
Setting GUILE_MIN_YIELD_2 to 65
Setting GUILE_MIN_YIELD_MALLOC to 65
Setting GUILE_INIT_SEGMENT_SIZE_1 to 10485760
Setting GUILE_MAX_SEGMENT_SIZE to 104857600

LILYPOND_DATADIR="/usr/local/share/lilypond/2.19.16"
LOCALEDIR="/usr/local/share/locale"

Effective prefix: "/home/fede/lilypond-git/out/share/lilypond/current"
PATH="/home/fede/lilypond-git/out/bin/../bin:/home/fede/lilypond-git/out/bin:/home/fede/lilypond-git/scripts/auxiliar:/home/fede/git-cl:/home/fede/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/fede/node_modules/beautiful-docs/bin"
[]
Guile 1.8
[/home/fede/lilypond-git/out/share/lilypond/current/scm/lily-library.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/output-lib.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/markup-macros.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/parser-ly-from-scheme.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/file-cache.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/define-event-classes.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/define-music-callbacks.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/define-music-types.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/define-note-names.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/c++.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/chord-entry.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/skyline.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/markup.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/define-markup-commands.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/stencil.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/modal-transforms.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/chord-generic-names.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/chord-ignatzek-names.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/music-functions.scm
[/home/fede/lilypond-git/out/share/lilypond/current/scm/define-music-display-methods.scm]
]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/part-combiner.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/autochange.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/define-music-properties.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/time-signature-settings.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/auto-beam.scm]
[/home/fede/lilypond-git/out/share/lilypond/current/scm/chord-name

make info fails without preceding make doc

[David Kastrup]

dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 info
Making Documentation/out-www/lilypond-changes.info < texi
Making Documentation/out-www/lilypond-learning.info < texi
Making Documentation/out-www/en/notation.texi < tely
Making Documentation/out-www/lilypond-usage.info < texi
lilypond-book.py: error: file not found: en/hyphenation.itexi


-- 
David Kastrup

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

Re: Issue 1832 in lilypond: make doc broken

[lilypond]

Updates:
Status: Fixed
Owner: reinhold...@gmail.com
Labels: fixed_2_15_9

Comment #1 on issue 1832 by reinhold...@gmail.com: make doc broken
http://code.google.com/p/lilypond/issues/detail?id=1832

Fixed with commit 9593f0a4fb415a05a4cbaad3ed1f2880ecb62cab
Phil confirms that this really fixes his problem.


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

Re: Issue 1832 in lilypond: make doc broken

[lilypond]

Updates:
Status: Verified

Comment #2 on issue 1832 by colinpkc...@gmail.com: make doc broken
http://code.google.com/p/lilypond/issues/detail?id=1832

Verified on 64-bit Ubuntu


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

Re: Issue 2416 in lilypond: make doc documentation

[lilypond]

Comment #1 on issue 2416 by julien.r...@gmail.com: make doc documentation
http://code.google.com/p/lilypond/issues/detail?id=2416

I did some of this in issue 2395.


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

Re: run make doc without regtest? (issue 4180)

[Trevor Daniels]

Federico Bruni wrote Friday, December 26, 2014 10:01 PM

>I cannot compile 'make doc' because of issue 4180.
> IIUC the regtests are run automatically before compiling the 
> documentation? How can I avoid that?

This regtest , time-signature-single-digit.ly, was added as part of commit
586a6d331e22d0e1a255068f07c534d219c7c902
(see Issue 4176.)

It causes LilyPond 2.19.15 to crash in Frescobaldi:

Starting lilypond-windows.exe 2.19.15 [time-signature-single-digit.ly]...
Processing 
`c:/users/trevor/appdata/local/temp/frescobaldi-i1jfd6/tmpskecnk/time-signature-single-digit.ly'
Parsing...
Renaming input to: `time-signature-single-digit.ly'
Interpreting music...
Exited with return code -1073741571.

Was this regtest never executed before being committed?!

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

Re: run make doc without regtest? (issue 4180)

[Federico Bruni]

Il giorno ven 26 dic 2014 alle 23:32, Trevor Daniels 
 ha scritto:
This regtest , time-signature-single-digit.ly, was added as part of 
commit

586a6d331e22d0e1a255068f07c534d219c7c902
(see Issue 4176.)

It causes LilyPond 2.19.15 to crash in Frescobaldi:

[...]

Was this regtest never executed before being committed?!


Well, at least by the automatic doc build:
https://code.google.com/p/lilypond/issues/detail?id=4176#c2

It seems that it doesn't occur in any situation:
http://lists.gnu.org/archive/html/bug-lilypond/2014-10/msg00071.html

For me it's very annoying because I need to run 'make doc' to check a 
lot of translation updates which I'd like to commit in the next days.


If anyone knows how to avoid regtests in 'make doc' it would help a lot.



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

Re: run make doc without regtest? (issue 4180)

[Trevor Daniels]

Federico,

You could revert commit 586a6d331e22d0e1a255068f07c534d219c7c902 locally or 
temporarily remove that regtest from your local repository while you run your 
"make doc" tests.

Trevor
  - Original Message - 
  From: Federico Bruni 
  To: Trevor Daniels 
  Cc: Lilypond bug 
  Sent: Friday, December 26, 2014 10:47 PM
  Subject: Re: run make doc without regtest? (issue 4180)


  Il giorno ven 26 dic 2014 alle 23:32, Trevor Daniels  
ha scritto:

This regtest , time-signature-single-digit.ly, was added as part of commit 
586a6d331e22d0e1a255068f07c534d219c7c902 (see Issue 4176.) It causes LilyPond 
2.19.15 to crash in Frescobaldi: [...] Was this regtest never executed before 
being committed?!


  Well, at least by the automatic doc build:
  https://code.google.com/p/lilypond/issues/detail?id=4176#c2


  It seems that it doesn't occur in any situation:
  http://lists.gnu.org/archive/html/bug-lilypond/2014-10/msg00071.html


  For me it's very annoying because I need to run 'make doc' to check a lot of 
translation updates which I'd like to commit in the next days.


  If anyone knows how to avoid regtests in 'make doc' it would help a lot.


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

Re: run make doc without regtest? (issue 4180)

[Federico Bruni]

Il giorno sab 27 dic 2014 alle 0:02, Trevor Daniels 
 ha scritto:
You could revert commit 586a6d331e22d0e1a255068f07c534d219c7c902 
locally or temporarily remove that regtest from your local repository 
while you run your "make doc" tests.




Sure, I did not even think about the easiest solution :)
Thanks
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: run make doc without regtest? (issue 4180)

[David Kastrup]

Federico Bruni  writes:

> I cannot compile 'make doc' because of issue 4180.
> IIUC the regtests are run automatically before compiling the
> documentation? How can I avoid that?

The regtest images and descriptions are part of the docs and web pages.
So it's not a matter of some spurious rules doing too much but actually
affects the output.  Better to just revert the problematic commit.

-- 
David Kastrup


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

Re: run make doc without regtest? (issue 4180)

[Keith OHara]

Federico Bruni  gmail.com> writes:

> Il giorno ven 26 dic 2014 alle 23:32, Trevor Daniels 
>  treda.co.uk> ha scritto:
> > 
> > Was this regtest never executed before being committed?!
> 
> Well, at least by the automatic doc build:
> https://code.google.com/p/lilypond/issues/detail?id=4176#c2
> 
> It seems that it doesn't occur in any situation:
> http://lists.gnu.org/archive/html/bug-lilypond/2014-10/msg00071.html
> 

It seems that we knew about these problems, bug then added the 
regression tests anyway.  

We have bug-reports, so it seems we lose no information if we avoid these
issues in the regression test, but the last time I tried that I got



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

Re: run make doc without regtest? (issue 4180)

[David Kastrup]

Keith OHara  writes:

> Federico Bruni  gmail.com> writes:
>
>> Il giorno ven 26 dic 2014 alle 23:32, Trevor Daniels 
>>  treda.co.uk> ha scritto:
>> > 
>> > Was this regtest never executed before being committed?!
>> 
>> Well, at least by the automatic doc build:
>> https://code.google.com/p/lilypond/issues/detail?id=4176#c2
>> 
>> It seems that it doesn't occur in any situation:
>> http://lists.gnu.org/archive/html/bug-lilypond/2014-10/msg00071.html
>> 
>
> It seems that we knew about these problems, bug then added the 
> regression tests anyway.  
>
> We have bug-reports, so it seems we lose no information

Bug reports or an actual issue in the tracker?

> if we avoid these issues in the regression test, but the last time I
> tried that I got
> 

There was no attempt of even making a tracker issue that time as far as
I can tell, it was strictly a sweep-under-the-rug approach.

I consider it reasonable to reduce a regtest to trigger the issue it is
intended for, but if it shows an unrelated problem, we should not remove
it without creating an issue report for it.

-- 
David Kastrup


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

Re: run make doc without regtest? (issue 4180)

[Keith OHara]

David Kastrup  gnu.org> writes:

> Keith OHara  oco.net> writes:
> 
> > It seems that we knew about these problems, bug then added the 
> > regression tests anyway.  
> >
> > We have bug-reports, so it seems we lose no information
> 
> Bug reports or an actual issue in the tracker?
> 

Well, there is of course the bug report in the issue title,
but Federico's example and log seem to point more to the bug reported
in another thread here, now issue 4231

> > if we avoid these issues in the regression test, but the last time I
> > tried that I got
> > 
> 
> There was no attempt of even making a tracker issue that time as far as
> I can tell, it was strictly a sweep-under-the-rug approach.

The tracker issue from 2011 was linked in the email linked above.

A new regtest had triggered a previously-tracked issue, and somebody
with and email starting 'dak' complained on the bug-lilypond. 
I pointed to the tracker item, and suggested to change the regtest.
Then a message from 'dak' posted to the tracker item complained that
the error in the regtest hindered regression testing.  So I put the
known work-around into the offending regtest, and somebody with the 
email staring 'dak' reverted the work-around.

Let's see what happens this time.


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

Re: run make doc without regtest? (issue 4180)

[David Kastrup]

Keith OHara  writes:

> David Kastrup  gnu.org> writes:
>
>> Keith OHara  oco.net> writes:
>> 
>> > It seems that we knew about these problems, bug then added the 
>> > regression tests anyway.  
>> >
>> > We have bug-reports, so it seems we lose no information
>> 
>> Bug reports or an actual issue in the tracker?
>> 
>
> Well, there is of course the bug report in the issue title,
> but Federico's example and log seem to point more to the bug reported
> in another thread here, now issue 4231
>
>> > if we avoid these issues in the regression test, but the last time I
>> > tried that I got
>> > 
>> 
>> There was no attempt of even making a tracker issue that time as far as
>> I can tell, it was strictly a sweep-under-the-rug approach.
>
> The tracker issue from 2011 was linked in the email linked above.

Yes, I remember now.  Reported in June.  No attempt of fixing it,
messing up a whole number of regtests and making them unreliable.
Several unrelated regtests were purposefully _complicated_ (adding
stemlets) in order not to trigger the problem.  I called this the wrong
approach in November and started debugging the problem in order to
figure out what was wrong, reporting on my findings.  It was you who
actually found the fix.

Do you want to state that you would have considered it better to keep
obfuscating regtests by adding stemlets and thus avoid looking for the
underlying problem?

With regard to large rationals, the underlying problem is well-known and
separated out and we are not talking about artificial complication of
regtests in ways nobody understands.

If you don't see a difference here, it would seem good for the overall
stability of the code base that other voices get heard as well.

> A new regtest had triggered a previously-tracked issue, and somebody
> with and email starting 'dak' complained on the bug-lilypond. 
> I pointed to the tracker item, and suggested to change the regtest.
> Then a message from 'dak' posted to the tracker item complained that
> the error in the regtest hindered regression testing.  So I put the
> known work-around into the offending regtest, and somebody with the 
> email staring 'dak' reverted the work-around.
>
> Let's see what happens this time.

Even if you make it appear you'd rather have them silenced.

-- 
David Kastrup


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

Re: run make doc without regtest? (issue 4180)

[Keith OHara]

Trevor Daniels  treda.co.uk> writes:

> You could revert commit 586a6d331e22d0e1a255068f07c534d219c7c902 locally

I've boldly reverted the commit, removing those two regtests from staging
so we don't have build errors.

I suspect it is actually issue 4231 that caused the problem, because
4180 would give an error message that was not seen in Federico' log, and
should not have happened with the (now-removed) time-sig-single-digit.ly


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

Re: make info fails without preceding make doc

[David Kastrup]

David Kastrup  writes:

> dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 info
> Making Documentation/out-www/lilypond-changes.info < texi
> Making Documentation/out-www/lilypond-learning.info < texi
> Making Documentation/out-www/en/notation.texi < tely
> Making Documentation/out-www/lilypond-usage.info < texi
> lilypond-book.py: error: file not found: en/hyphenation.itexi

Well, it is not like make doc works either:

dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 doc
Making latt1095.tfm in TeX Live (mktextfm)
Making Documentation/out-www/en/notation.texi < tely
Making Documentation/out-www/ca/notation.texi < tely
Making Documentation/out-www/de/notation.texi < tely
Making Documentation/out-www/es/notation.texi < tely
Making Documentation/out-www/fr/learning.texi < tely
Making Documentation/out-www/fr/notation.texi < tely
Making Documentation/out-www/it/notation.texi < tely
Making Documentation/out-www/it/usage.texi < tely
Making larm1095.tfm in TeX Live (mktextfm)
Making Documentation/out-www/fr/web.texi (copy)
Making Documentation/out-www/en/changes.xref-map < texi
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/en/notation.texi] 
Error 1
make[2]: *** Waiting for unfinished jobs
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/ca/notation.texi] 
Error 1
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/de/notation.texi] 
Error 1
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/es/notation.texi] 
Error 1
lilypond-book.py: error: file not found: en/hyphenation.itexi

lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/fr/notation.texi] 
Error 1
make[2]: *** [../make/lilypond-book-rules.make:6: out-www/it/notation.texi] 
Error 1
make[1]: *** 
[/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:150: WWW] Error 
2
make: *** [/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:155: 
doc] Error 2


-- 
David Kastrup

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

Re: make info fails without preceding make doc

[Jean Abou Samra]

Le 21/09/2021 à 21:12, David Kastrup a écrit :

David Kastrup  writes:


dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 info
Making Documentation/out-www/lilypond-changes.info < texi
Making Documentation/out-www/lilypond-learning.info < texi
Making Documentation/out-www/en/notation.texi < tely
Making Documentation/out-www/lilypond-usage.info < texi
lilypond-book.py: error: file not found: en/hyphenation.itexi

Well, it is not like make doc works either:

dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 doc
Making latt1095.tfm in TeX Live (mktextfm)
Making Documentation/out-www/en/notation.texi < tely
Making Documentation/out-www/ca/notation.texi < tely
Making Documentation/out-www/de/notation.texi < tely
Making Documentation/out-www/es/notation.texi < tely
Making Documentation/out-www/fr/learning.texi < tely
Making Documentation/out-www/fr/notation.texi < tely
Making Documentation/out-www/it/notation.texi < tely
Making Documentation/out-www/it/usage.texi < tely
Making larm1095.tfm in TeX Live (mktextfm)
Making Documentation/out-www/fr/web.texi (copy)
Making Documentation/out-www/en/changes.xref-map < texi
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/en/notation.texi] 
Error 1
make[2]: *** Waiting for unfinished jobs
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/ca/notation.texi] 
Error 1
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/de/notation.texi] 
Error 1
lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/es/notation.texi] 
Error 1
lilypond-book.py: error: file not found: en/hyphenation.itexi

lilypond-book.py: error: file not found: en/hyphenation.itexi

make[2]: *** [../make/lilypond-book-rules.make:6: out-www/fr/notation.texi] 
Error 1
make[2]: *** [../make/lilypond-book-rules.make:6: out-www/it/notation.texi] 
Error 1
make[1]: *** 
[/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:150: WWW] Error 
2
make: *** [/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:155: 
doc] Error 2



You did clean everything beforehand? Commit 79114c78d1 changed
documentation generation to create a new file, but the doc
build infrastructure only knows about the dependency via
internals.texi, which has not changed.

Best,
Jean

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

Re: make info fails without preceding make doc

[David Kastrup]

David Kastrup  writes:

> David Kastrup  writes:
>
>> dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 info
>> Making Documentation/out-www/lilypond-changes.info < texi
>> Making Documentation/out-www/lilypond-learning.info < texi
>> Making Documentation/out-www/en/notation.texi < tely
>> Making Documentation/out-www/lilypond-usage.info < texi
>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>
> Well, it is not like make doc works either:
>
> dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 doc
> Making latt1095.tfm in TeX Live (mktextfm)
> Making Documentation/out-www/en/notation.texi < tely
> Making Documentation/out-www/ca/notation.texi < tely
> Making Documentation/out-www/de/notation.texi < tely
> Making Documentation/out-www/es/notation.texi < tely
> Making Documentation/out-www/fr/learning.texi < tely
> Making Documentation/out-www/fr/notation.texi < tely
> Making Documentation/out-www/it/notation.texi < tely
> Making Documentation/out-www/it/usage.texi < tely
> Making larm1095.tfm in TeX Live (mktextfm)
> Making Documentation/out-www/fr/web.texi (copy)
> Making Documentation/out-www/en/changes.xref-map < texi
> lilypond-book.py: error: file not found: en/hyphenation.itexi
>
> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/en/notation.texi] 
> Error 1
> make[2]: *** Waiting for unfinished jobs
> lilypond-book.py: error: file not found: en/hyphenation.itexi
>
> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/ca/notation.texi] 
> Error 1
> lilypond-book.py: error: file not found: en/hyphenation.itexi
>
> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/de/notation.texi] 
> Error 1
> lilypond-book.py: error: file not found: en/hyphenation.itexi
>
> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/es/notation.texi] 
> Error 1
> lilypond-book.py: error: file not found: en/hyphenation.itexi
>
> lilypond-book.py: error: file not found: en/hyphenation.itexi
>
> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/fr/notation.texi] 
> Error 1
> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/it/notation.texi] 
> Error 1
> make[1]: ***
> [/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:150:
> WWW] Error 2
> make: ***
> [/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:155:
> doc] Error 2

I am reverting

commit 79114c78d12a24b6089af0375dcac5b739c29a0c
Author: Jean Abou Samra 
Date:   Tue Aug 31 17:49:30 2021 +0200

Doc: Better hyphenation in PDF output for camel-case names

Node names from the Internals Reference often appear in non-typewriter
fonts in "See also" section, where TeX would break them at ugly places.
Autogenerate a file containing hyphenation exceptions for Texinfo to
avoid this.

in my local tree for now.  Has anybody tried this with an in-tree build?

-- 
David Kastrup

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

Re: make info fails without preceding make doc

[David Kastrup]

Jean Abou Samra  writes:

> Le 21/09/2021 à 21:12, David Kastrup a écrit :
>> David Kastrup  writes:
>>
>>> dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 info
>>> Making Documentation/out-www/lilypond-changes.info < texi
>>> Making Documentation/out-www/lilypond-learning.info < texi
>>> Making Documentation/out-www/en/notation.texi < tely
>>> Making Documentation/out-www/lilypond-usage.info < texi
>>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>> Well, it is not like make doc works either:
>>
>> dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 doc
>> Making latt1095.tfm in TeX Live (mktextfm)
>> Making Documentation/out-www/en/notation.texi < tely
>> Making Documentation/out-www/ca/notation.texi < tely
>> Making Documentation/out-www/de/notation.texi < tely
>> Making Documentation/out-www/es/notation.texi < tely
>> Making Documentation/out-www/fr/learning.texi < tely
>> Making Documentation/out-www/fr/notation.texi < tely
>> Making Documentation/out-www/it/notation.texi < tely
>> Making Documentation/out-www/it/usage.texi < tely
>> Making larm1095.tfm in TeX Live (mktextfm)
>> Making Documentation/out-www/fr/web.texi (copy)
>> Making Documentation/out-www/en/changes.xref-map < texi
>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>>
>> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/en/notation.texi] 
>> Error 1
>> make[2]: *** Waiting for unfinished jobs
>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>>
>> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/ca/notation.texi] 
>> Error 1
>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>>
>> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/de/notation.texi] 
>> Error 1
>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>>
>> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/es/notation.texi] 
>> Error 1
>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>>
>> lilypond-book.py: error: file not found: en/hyphenation.itexi
>>
>> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/fr/notation.texi] 
>> Error 1
>> make[2]: *** [../make/lilypond-book-rules.make:6: out-www/it/notation.texi] 
>> Error 1
>> make[1]: ***
>> [/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:150:
>> WWW] Error 2
>> make: ***
>> [/usr/local/tmp/lilypond/stepmake/stepmake/generic-targets.make:155:
>> doc] Error 2
>
>
> You did clean everything beforehand? Commit 79114c78d1 changed
> documentation generation to create a new file, but the doc
> build infrastructure only knows about the dependency via
> internals.texi, which has not changed.

./autogen.sh --noconf
./config.status --recheck
make clean

Several times.

-- 
David Kastrup

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

Re: make info fails without preceding make doc

[Jean Abou Samra]

Le 21/09/2021 à 21:24, David Kastrup a écrit :

I am reverting

commit 79114c78d12a24b6089af0375dcac5b739c29a0c
Author: Jean Abou Samra 
Date:   Tue Aug 31 17:49:30 2021 +0200

 Doc: Better hyphenation in PDF output for camel-case names
 
 Node names from the Internals Reference often appear in non-typewriter

 fonts in "See also" section, where TeX would break them at ugly places.
 Autogenerate a file containing hyphenation exceptions for Texinfo to
 avoid this.

in my local tree for now.  Has anybody tried this with an in-tree build?


I always build in-tree.



./autogen.sh --noconf
./config.status --recheck
make clean

Several times.


Also with the bulldozering git clean -xdf?

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

Re: make info fails without preceding make doc

[David Kastrup]

Jean Abou Samra  writes:

> Le 21/09/2021 à 21:24, David Kastrup a écrit :
>> I am reverting
>>
>> commit 79114c78d12a24b6089af0375dcac5b739c29a0c
>> Author: Jean Abou Samra 
>> Date:   Tue Aug 31 17:49:30 2021 +0200
>>
>>  Doc: Better hyphenation in PDF output for camel-case names
>>   Node names from the Internals Reference often appear in
>> non-typewriter
>>  fonts in "See also" section, where TeX would break them at ugly places.
>>  Autogenerate a file containing hyphenation exceptions for Texinfo to
>>  avoid this.
>>
>> in my local tree for now.  Has anybody tried this with an in-tree build?
>
> I always build in-tree.
>
>
>> ./autogen.sh --noconf
>> ./config.status --recheck
>> make clean
>>
>> Several times.
>
> Also with the bulldozering git clean -xdf?

I have enough stuff in my normal work tree that I won't.  If "make
clean" does not work, that is not what I consider useful.

-- 
David Kastrup

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

Re: make info fails without preceding make doc

[Jean Abou Samra]

Le 21/09/2021 à 22:03, David Kastrup a écrit :

Jean Abou Samra  writes:


Le 21/09/2021 à 21:24, David Kastrup a écrit :

I am reverting

commit 79114c78d12a24b6089af0375dcac5b739c29a0c
Author: Jean Abou Samra 
Date:   Tue Aug 31 17:49:30 2021 +0200

  Doc: Better hyphenation in PDF output for camel-case names
   Node names from the Internals Reference often appear in
non-typewriter
  fonts in "See also" section, where TeX would break them at ugly places.
  Autogenerate a file containing hyphenation exceptions for Texinfo to
  avoid this.

in my local tree for now.  Has anybody tried this with an in-tree build?

I always build in-tree.



./autogen.sh --noconf
./config.status --recheck
make clean

Several times.

Also with the bulldozering git clean -xdf?

I have enough stuff in my normal work tree that I won't.
If "make
clean" does not work, that is not what I consider useful.


Have you also tried make doc-clean? Otherwise, consider
git clean in the Documentation/ folder.



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

Re: make info fails without preceding make doc

[David Kastrup]

Jean Abou Samra  writes:

> Le 21/09/2021 à 22:03, David Kastrup a écrit :
>> Jean Abou Samra  writes:
>>
>>> Le 21/09/2021 à 21:24, David Kastrup a écrit :
>>>> I am reverting
>>>>
>>>> commit 79114c78d12a24b6089af0375dcac5b739c29a0c
>>>> Author: Jean Abou Samra 
>>>> Date:   Tue Aug 31 17:49:30 2021 +0200
>>>>
>>>>   Doc: Better hyphenation in PDF output for camel-case names
>>>>Node names from the Internals Reference often appear in
>>>> non-typewriter
>>>>   fonts in "See also" section, where TeX would break them at ugly 
>>>> places.
>>>>   Autogenerate a file containing hyphenation exceptions for Texinfo to
>>>>   avoid this.
>>>>
>>>> in my local tree for now.  Has anybody tried this with an in-tree build?
>>> I always build in-tree.
>>>
>>>
>>>> ./autogen.sh --noconf
>>>> ./config.status --recheck
>>>> make clean
>>>>
>>>> Several times.
>>> Also with the bulldozering git clean -xdf?
>> I have enough stuff in my normal work tree that I won't.
>> If "make
>> clean" does not work, that is not what I consider useful.
>
> Have you also tried make doc-clean? Otherwise, consider
> git clean in the Documentation/ folder.

"make doc-clean" appears to work better.  I find it somewhat surprising
that it should not have been implied by "make clean".

-- 
David Kastrup

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

Re: make info fails without preceding make doc

[Federico Bruni]

Il giorno mar 21 set 2021 alle 22:48:04 +0200, David Kastrup 
 ha scritto:
"make doc-clean" appears to work better.  I find it somewhat 
surprising

that it should not have been implied by "make clean".


IIRC it's implied by make distclean




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

Re: make info fails without preceding make doc

[David Kastrup]

Federico Bruni  writes:

> Il giorno mar 21 set 2021 alle 22:48:04 +0200, David Kastrup
>  ha scritto:
>> "make doc-clean" appears to work better.  I find it somewhat
>> surprising
>> that it should not have been implied by "make clean".
>
> IIRC it's implied by make distclean

Well, but distclean removes everything done by ./configure as well.
Including config.status , so I cannot do ./config.status --recheck
anymore.

-- 
David Kastrup

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

Re: make info fails without preceding make doc

[David Kastrup]

Federico Bruni  writes:

> Il giorno mar 21 set 2021 alle 22:48:04 +0200, David Kastrup
>  ha scritto:
>> "make doc-clean" appears to work better.  I find it somewhat
>> surprising
>> that it should not have been implied by "make clean".
>
> IIRC it's implied by make distclean

At any rate, the Makefile structure was already in place since I had run
autogen.sh and configure again.  If make doc then fails due to missing
generated files, that points to missing dependencies.  Those missing
dependencies will still be good for triggering failed parallel make runs
occasionally.

-- 
David Kastrup

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

Re: make info fails without preceding make doc

[Jean Abou Samra]

Le 22/09/2021 à 14:02, David Kastrup a écrit :

Federico Bruni  writes:


Il giorno mar 21 set 2021 alle 22:48:04 +0200, David Kastrup
 ha scritto:

"make doc-clean" appears to work better.  I find it somewhat
surprising
that it should not have been implied by "make clean".

IIRC it's implied by make distclean

At any rate, the Makefile structure was already in place since I had run
autogen.sh and configure again.  If make doc then fails due to missing
generated files, that points to missing dependencies.


The dependencies are not logically missing, but
peculiarly specified. notation.texi “depends” on
internals.texi so that the process leading to
the generation of internals.texi, namely the compilation
of ly/generate-documentation.ly, also creates
the includable files notation.texi needs along
the way.

It may be possible to specify the dependencies
on the individual files hyphenation.texi,
markup-commands.tely, etc. My understanding of
the doc build is too low to even attempt that.



Those missing
dependencies will still be good for triggering failed parallel make runs
occasionally.


I think they do not cause problems with parallel builds,
but build updates.


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

Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Status: Accepted
Owner: 
Labels: Type-Build

New issue 2028 by philehol...@gmail.com: Make doc always recreates HTML  
files

http://code.google.com/p/lilypond/issues/detail?id=2028

As the title says.  Run make, make doc and then make doc again.  The HTML  
files all have fresh timestamps.  It would presumably speed up make doc to  
avoid building these when they don't require a rebuild.



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

Issue 2353 in lilypond: Patch: More reductions in make doc

[lilypond]

Status: New
Owner: 
Labels: Type-Patch Patch-new

New issue 2353 by philehol...@gmail.com: Patch: More reductions in make doc
http://code.google.com/p/lilypond/issues/detail?id=2353

More reductions in make doc

Pushes the output from making midi .ly files and ly-examples to logfiles.

http://codereview.appspot.com/5694079


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

Re: Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Comment #1 on issue 2028 by philehol...@gmail.com: Make doc always  
recreates HTML files

http://code.google.com/p/lilypond/issues/detail?id=2028

Done some more looking at this.  It appears that the .html files aren't  
being made, just copied.  GNUmakefile.in has the following rule:


WWW-post:
[snip]
	$(buildscript-dir)/www_post $(PACKAGE_NAME) $(TOPLEVEL_VERSION)  
$(outdir) "$(WEB_TARGETS)"


 - so the script www_post.py is run as follows:

/home/phil/lilypond-git/build/scripts/build/out/www_post LilyPond  
2.15.19 ./out-www "offline"


This copies the html files from build/Documentation/out-www/web (where they  
have their old timestamps) to build/out-www/offline-root/Documentation/web  
- although the "copy" is done by www_post.py, which also fixes up some  
references and adds footers - it therefore takes processing power to do  
this - it's something like 15,000 files in total.  On my mighty fast build  
machine, running make doc with a fully up-to-date doc tree takes 22.3  
seconds.  Without the web_post.py it takes 8.3 seconds.  I think we need a  
rule that web_post gets run only if needed?



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

Re: Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Comment #2 on issue 2028 by philehol...@gmail.com: Make doc always  
recreates HTML files

http://code.google.com/p/lilypond/issues/detail?id=2028

Given the way www_post.py works, I don't think it's wise to try to create a  
make rule to stop it running if a given file is already present in the  
destination tree.  My suggestion would be to modify web_post.py so that it  
checks the timestamp of the file in the output directory before processing  
and copying it, and skipping the processing if the file is newer or the  
same age as the source file.  This will mean checking 15,000 timestamps,  
but still should be a lot quicker.



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

Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Status: Accepted
Owner: 
Labels: Type-Build

New issue 2075 by philehol...@gmail.com: Implement GOP 9 - behavior of make  
doc

http://code.google.com/p/lilypond/issues/detail?id=2075

See http://lilypond.org/~graham/gop/gop_9.html.  This needs to be  
implemented at some point.  I'm making a small start.



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

Re: Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Comment #3 on issue 2028 by philehol...@gmail.com: Make doc always  
recreates HTML files

http://code.google.com/p/lilypond/issues/detail?id=2028

Not sure whether there have been changes to the doc build that make a  
repeat build take longer, but I now see make doc followed by make doc take  
well over a minute on my system.  However, make LANGS='' doc takes 18  
seconds with the www_post.py, but only 4 seconds without it.



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

Re: Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Updates:
Blockedon: 2158

Comment #4 on issue 2028 by julien.r...@gmail.com: Make doc always  
recreates HTML files

http://code.google.com/p/lilypond/issues/detail?id=2028

(No comment was entered for this change.)


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

Re: Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Updates:
Blockedon: -2158

Comment #5 on issue 2028 by pkx1...@gmail.com: Make doc always recreates  
HTML files

http://code.google.com/p/lilypond/issues/detail?id=2028

(No comment was entered for this change.)


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

Re: Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Updates:
Status: Fixed
Labels: Fixed_2_15_25

Comment #6 on issue 2028 by philehol...@gmail.com: Make doc always  
recreates HTML files

http://code.google.com/p/lilypond/issues/detail?id=2028

See Issue 2158


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

Re: Issue 2028 in lilypond: Make doc always recreates HTML files

[lilypond]

Updates:
Status: Verified

Comment #7 on issue 2028 by julien.r...@gmail.com: Make doc always  
recreates HTML files

http://code.google.com/p/lilypond/issues/detail?id=2028

(No comment was entered for this change.)


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

Re: Issue 2353 in lilypond: Patch: More reductions in make doc

[lilypond]

Updates:
Labels: Patch-review

Comment #1 on issue 2353 by julien.r...@gmail.com: Patch: More reductions  
in make doc

http://code.google.com/p/lilypond/issues/detail?id=2353#c1

Patchy the autobot says: LGTM.


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

Re: Issue 2353 in lilypond: Patch: More reductions in make doc

[lilypond]

Updates:
Labels: -Patch-countdown Patch-push

Comment #3 on issue 2353 by colinpkc...@gmail.com: Patch: More reductions  
in make doc

http://code.google.com/p/lilypond/issues/detail?id=2353

Counted down to 20120228, please push.


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

Re: Issue 2353 in lilypond: Patch: More reductions in make doc

[lilypond]

Updates:
Status: Verified
Labels: -Patch-push Fixed_2_15_32

Comment #4 on issue 2353 by philehol...@gmail.com: Patch: More reductions  
in make doc

http://code.google.com/p/lilypond/issues/detail?id=2353

Pushed to staging as 8bfdda40f3444df7f94f32ebc79e0ccd9695949a


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

Re: Issue 2353 in lilypond: Patch: More reductions in make doc

[lilypond]

Comment #5 on issue 2353 by julien.r...@gmail.com: Patch: More reductions  
in make doc

http://code.google.com/p/lilypond/issues/detail?id=2353

I verify.


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

Re: Issue 2353 in lilypond: Patch: More reductions in make doc

[lilypond]

Updates:
Status: Fixed

Comment #6 on issue 2353 by philehol...@gmail.com: Patch: More reductions  
in make doc

http://code.google.com/p/lilypond/issues/detail?id=2353

Reverted to fixed, since this needs reverifying by checking the source as  
pulled from git, not just the commitish.



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

Re: Issue 2353 in lilypond: Patch: More reductions in make doc

[lilypond]

Updates:
Status: Verified

Comment #7 on issue 2353 by julien.r...@gmail.com: Patch: More reductions  
in make doc

http://code.google.com/p/lilypond/issues/detail?id=2353

These changes are part of the source tree as checked out from git  
release/unstable.



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

Issue 2415 in lilypond: make doc clean does not delete logfiles

[lilypond]

Status: Accepted
Owner: 
Labels: Type-Build

New issue 2415 by philehol...@gmail.com: make doc clean does not delete  
logfiles

http://code.google.com/p/lilypond/issues/detail?id=2415

As the title says.  Now make doc creates lots of logfiles, make doc clean  
should delete them.



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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Comment #1 on issue 2075 by philehol...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075

Baseline is make doc on my system creates 164,663 lines of output and takes  
12 min 40 sec.



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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Comment #2 on issue 2075 by philehol...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075

Trying to upload a patch for this for review, but getting:

phil@Ubuntu:~/lilypond-git$ git cl upload origin/master  
make/lilypond-vars.make  |6 +++---

 make/ly-rules.make   |4 ++--
 make/lysdoc-targets.make |2 +-
 python/lilylib.py|   11 ---
 scripts/lilypond-book.py |   12 ++--
 5 files changed, 20 insertions(+), 15 deletions(-)
fatal: ref HEAD is not a symbolic ref
Command "git symbolic-ref HEAD" failed.

Can anyone help?


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Comment #3 on issue 2075 by gra...@percival-music.ca: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075

Not a clue; I'd make sure I had the patch (with git format-patch), then do  
a git reset --hard origin/master, reapply the patch, and try again?



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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Labels: Patch-new

Comment #4 on issue 2075 by philehol...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075#c4

Update LSR and fix Issue 1971

Fixes Issue 1971

http://codereview.appspot.com/5436073


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Comment #5 on issue 2075 by philehol...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075#c5

Initial reduction of make doc op - Issue 2075

Some initial changes to implement Issue 2075

http://codereview.appspot.com/5453046


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Labels: Patch-review

Comment #6 on issue 2075 by lilypond...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075#c6

Patchy the autobot says: LGTM.


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Labels: -Patch-countdown Patch-needs_work

Comment #8 on issue 2075 by gra...@percival-music.ca: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075

(No comment was entered for this change.)


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Labels: Patch-new

Comment #9 on issue 2075 by philehol...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075#c9

Initial reduction of make doc op - Issue 2075

This proposed patch reduces output to 113,500 lines by pushing lilypond  
output to logfiles.  If there is an error with lilypond-book trying to  
compile a lilypond file, it issues a simple error message pointing at the  
relevant logfile and exits.


http://codereview.appspot.com/5453046


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Labels: Patch-review

Comment #10 on issue 2075 by lilypond...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075#c10

Patchy the autobot says: LGTM.


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Labels: -Patch-countdown Patch-push

Comment #12 on issue 2075 by colinpkc...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075

Counted down to 20111213


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_23

Comment #13 on issue 2075 by philehol...@gmail.com: Implement GOP 9 -  
behavior of make doc

http://code.google.com/p/lilypond/issues/detail?id=2075

Pushed as 06aadb4af78fb061726d9f91ab7e2bb52eab59e8


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

Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc

[lilypond]

Updates:
Status: Verified

Comment #14 on issue 2075 by d...@gnu.org: Implement GOP 9 - behavior of  
make doc

http://code.google.com/p/lilypond/issues/detail?id=2075

Verified as being in 2.15.23


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

Issue 2352 in lilypond: Patch: Quietens extract-texi-filenames in make doc

[lilypond]

Status: New
Owner: 
Labels: Type-Patch Patch-new

New issue 2352 by philehol...@gmail.com: Patch: Quietens  
extract-texi-filenames in make doc

http://code.google.com/p/lilypond/issues/detail?id=2352

Quietens extract-texi-filenames in make doc

http://codereview.appspot.com/5698066


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

Issue 2378 in lilypond: Patch: Various updates to reduce make doc output

[lilypond]

Status: New
Owner: 
Labels: Type-Patch Patch-new

New issue 2378 by philehol...@gmail.com: Patch: Various updates to reduce  
make doc output

http://code.google.com/p/lilypond/issues/detail?id=2378

Various updates to reduce make doc output

http://codereview.appspot.com/5727055


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

Issue 2395 in lilypond: Patch: Update roadmap, make and make doc info.

[lilypond]

Status: New
Owner: 
Labels: Type-Enhancement Patch-new

New issue 2395 by julien.r...@gmail.com: Patch: Update roadmap, make and  
make doc info.

http://code.google.com/p/lilypond/issues/detail?id=2395

Update roadmap, make and make doc info.

CG: Review info about the build system.
CG: Update info about make doc.
Update ROADMAP.

http://codereview.appspot.com/5811043


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

Re: Issue 2352 in lilypond: Patch: Quietens extract-texi-filenames in make doc

[lilypond]

Updates:
Status: Fixed
Labels: -Patch-new Fixed_2_15_31

Comment #1 on issue 2352 by philehol...@gmail.com: Patch: Quietens  
extract-texi-filenames in make doc

http://code.google.com/p/lilypond/issues/detail?id=2352

Pushed to staging as d4d2ddbd7f52765dd4a0558e1153bb327eeb6f0f


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

Re: Issue 2352 in lilypond: Patch: Quietens extract-texi-filenames in make doc

[lilypond]

Updates:
Status: Verified

Comment #2 on issue 2352 by colingh...@gmail.com: Patch: Quietens  
extract-texi-filenames in make doc

http://code.google.com/p/lilypond/issues/detail?id=2352

Verified this commit is present in the repository.

Also checked it is part of 2.15.31-1.


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

Re: Issue 2378 in lilypond: Patch: Various updates to reduce make doc output

[lilypond]

Updates:
Labels: Patch-review

Comment #1 on issue 2378 by d...@gnu.org: Patch: Various updates to reduce  
make doc output

http://code.google.com/p/lilypond/issues/detail?id=2378#c1

Patchy the autobot says: LGTM.


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

Re: Issue 2378 in lilypond: Patch: Various updates to reduce make doc output

[lilypond]

Updates:
Labels: -Patch-countdown Patch-needs_work

Comment #3 on issue 2378 by gra...@percival-music.ca: Patch: Various  
updates to reduce make doc output

http://code.google.com/p/lilypond/issues/detail?id=2378

Julien and I have concerns about modifying the default behaviour of a few  
python scripts; we think they should be changed to take a --quiet option.



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

Re: Issue 2378 in lilypond: Patch: Various updates to reduce make doc output

[lilypond]

Comment #4 on issue 2378 by philehol...@gmail.com: Patch: Various updates  
to reduce make doc output

http://code.google.com/p/lilypond/issues/detail?id=2378

I'm happy to address those comments, but it'll be the weekend at the  
earliest.



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

Re: Issue 2352 in lilypond: Patch: Quietens extract-texi-filenames in make doc

[lilypond]

Updates:
Status: Fixed

Comment #3 on issue 2352 by philehol...@gmail.com: Patch: Quietens  
extract-texi-filenames in make doc

http://code.google.com/p/lilypond/issues/detail?id=2352

Reverted to fixed, since this needs reverifying by checking the source as  
pulled from git, not just the commitish.



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

Re: Issue 2352 in lilypond: Patch: Quietens extract-texi-filenames in make doc

[lilypond]

Updates:
Status: Verified

Comment #4 on issue 2352 by julien.r...@gmail.com: Patch: Quietens  
extract-texi-filenames in make doc

http://code.google.com/p/lilypond/issues/detail?id=2352

These changes are part of the source tree as checked out from git  
release/unstable.



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

Re: Issue 2378 in lilypond: Patch: Various updates to reduce make doc output

[lilypond]

Updates:
Labels: Patch-new

Comment #5 on issue 2378 by philehol...@gmail.com: Patch: Various updates  
to reduce make doc output

http://code.google.com/p/lilypond/issues/detail?id=2378#c5

GNUmakefile: pushes lilypond output to a logfile.  Using $(*F) for the  
filename since the target name includes the directory.

GNUmakefile.in: heeltap from previous patch
lilypond-book-rules.make: removes output from pdflatex and prevents it  
requesting input if it fails.

lysdoc-rules.make: Gets rid of echoed progress message
abc2ly.py; lys-to-tely.py; midi2ly.py: Gets rid of progress message.

http://codereview.appspot.com/5727055


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