- 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
- 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
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-
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 f
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 h
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 su
- 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
bui
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
"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-c
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
cheapes
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 suff
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 re
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
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
Lily
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'"
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 long
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
- 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 Holme
ch 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-
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
- 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 b
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" b
22 matches
Mail list logo
