- Original Message -
From: Julien Rioux jri...@physics.utoronto.ca
To: lilypond-de...@gnu.org
Cc: bug-lilypond@gnu.org
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
- Original Message -
From: Phil Holmes m...@philholmes.net
To: lilypond-de...@gnu.org; Julien Rioux jri...@physics.utoronto.ca
Cc: bug-lilypond@gnu.org
Sent: Friday, January 27, 2012 1:38 PM
Subject: Re: make doc problem
- Original Message -
From: Julien Rioux jri
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
- Original Message -
From: Reinhold Kainhofer reinh...@kainhofer.com
To: Julien Rioux jri...@physics.utoronto.ca
Cc: lilypond-de...@gnu.org; bug-lilypond@gnu.org
Sent: Thursday, January 26, 2012 4:13 PM
Subject: Re: make doc problem
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks
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
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
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.
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
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
- Original Message -
From: Jean-Charles Malahieude lily...@orange.fr
To: Lily Bugs bug-lilypond@gnu.org; lilypond-devel
lilypond-de...@gnu.org; Julien Rioux jri...@physics.utoronto.ca
Sent: Sunday, January 22, 2012 6:19 PM
Subject: make doc problem
Hi all!
Not only that I can
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
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
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
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
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
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'
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
Julien Rioux jri...@physics.utoronto.ca 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
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
On 22/01/2012 2:38 PM, David Kastrup wrote:
Julien Riouxjri...@physics.utoronto.ca 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
Julien Rioux jri...@physics.utoronto.ca wrote in message
news:4f1c6a79.3040...@physics.utoronto.ca...
On 22/01/2012 2:38 PM, David Kastrup wrote:
Julien Riouxjri...@physics.utoronto.ca writes:
I can't run -j, I have a single core.
This is factually incorrect. You can run -j just fine, but
21 matches
Mail list logo
