Updates:
Labels: -Patch-needs_work
Comment #25 on issue 1821 by julien.r...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
(No comment was entered for this change.)
___
bug-lilypond mailing li
Updates:
Status: Verified
Comment #24 on issue 1821 by brownian.box: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.o
Updates:
Status: Fixed
Labels: fixed_2_15_10
Comment #23 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Pushed as 623197430a7ed9b755d92cb053b64c21678af803
Comment #22 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
oh, definitely change whatever you need in lys-to-tely.py. Both the input
filename and glob input both failed (without further changes to the make
file), so go
Comment #21 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Yes, as I mentioned in comment 19, this needs a change to Graham's
--input-filenames feature in lys-to-tely.py. I didn't want to change it
before hearing
Updates:
Labels: -Patch-new Patch-needs_work
Comment #20 on issue 1821 by pkx1...@gmail.com: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
(No comment was entered for this change.)
___
bug-lilypond mailing
Comment #19 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
It seems that Graham's commit 340d7b49e816a5930ae39e17212415f16c8d152d
makes lys-to-tely expect the filenames in --input-filenames=FILE to be one
per line
Updates:
Status: Started
Owner: reinhold...@gmail.com
Labels: Patch-new
Comment #18 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Patch is up for review at http://codereview.appspot.com/495005
lilyp...@googlecode.com writes:
> Comment #17 on issue 1821 by reinhold...@gmail.com: GUB argument list
> too long
> http://code.google.com/p/lilypond/issues/detail?id=1821
>
> For out-of-source builds, there is no way we can use relative pathes!
I don't see why not.
After ../lilypond-build/conf
Comment #17 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
For out-of-source builds, there is no way we can use relative pathes!
Inside the make file, the $^ needs to expand all pathes to absolute pathes,
since th
Comment #16 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Ah, I see it's basically a problem of out-of-source builds (I'm always
using in-source builds, mainly for convenience). Each file needs to have
the full a
wrote in message
news:15-9567054385019064696-5785647612212700228-lilypond=googlecode@googlecode.com...
Comment #15 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Judging from the logfile from comment 3:
http://lilypo
Comment #15 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Judging from the logfile from comment 3:
http://lilypond.org/~graham/lilypond-test.log
it is indeed using absolute paths.
Note that the only people using GUB are
Comment #14 on issue 1821 by d...@gnu.org: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Uh, does that mean we are using absolute paths? From my painful
experiences as a project manager, I can tell that this would be a terrible
idea. Not only do we comp
Comment #13 on issue 1821 by tdaniels...@googlemail.com: GUB argument list
too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Another possibility, maybe for the short-term, would be to build using
shorter directory names or paths. These are repeated for every entry in
the l
Comment #12 on issue 1821 by tdaniels...@googlemail.com: GUB argument list
too long
http://code.google.com/p/lilypond/issues/detail?id=1821
The problem seems to be the value of MAX_ARG_STRLEN (131072) which limits
the length of each individual command line argument. The failing length
wa
Comment #11 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
I've also added a --glob-input option (i.e. --glob-input=*.ly) to
lys-to-doc.py, but that didn't help because $(COLLATED_FILES) is a bunch of
filenames rather th
Comment #10 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
I've added an --input-filename= option to lys-to-tely.
However, the $(foreach ...) proposal for lysdoc.make still lists everything
on the same command-line. I'm
Comment #9 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
David commented in email that it is not plausible that GNU screen played
any role in this.
I evidently did a merge from master to release/unstable in between tryi
lilyp...@googlecode.com writes:
> Comment #7 on issue 1821 by percival.music.ca: GUB argument list too long
> http://code.google.com/p/lilypond/issues/detail?id=1821
>
> by sheer fluke, I just tried running stuff without using GNU screen,
> and it appears to have passed this stage!
>
> I took a ve
Comment #8 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
cancel that; I'm still getting the same error.
On the plus side, I fixed a bunch of dist errors before I ran into this
problem again, but on the minus side I'm now
Comment #7 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
by sheer fluke, I just tried running stuff without using GNU screen, and it
appears to have passed this stage!
I took a very quick look but didn't see anything im
Comment #6 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
I see this behaviour on GUB master. I've attached the exact failing
command (extracted from the logs), which is longer than you thought,
probably due to long dir
Updates:
Labels: -Type-Build -Priority-Critical Type-Critical
Comment #5 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
(No comment was entered for this change.)
___
bug-
lilyp...@googlecode.com writes:
> Comment #4 on issue 1821 by reinhold...@gmail.com: GUB argument list
> too long
> http://code.google.com/p/lilypond/issues/detail?id=1821
>
> Okay, here's a proof-of-concept: In lysdoc-rules.make, instead of
> passing the list of filenames directly to lys-to-tely,
Comment #4 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Okay, here's a proof-of-concept: In lysdoc-rules.make, instead of passing
the list of filenames directly to lys-to-tely, we simply loop over them and
write
On Aug 16, 2011, at 12:58 PM, Reinhold Kainhofer wrote:
> Am Tuesday, 16. August 2011, 12:47:13 schrieb Mike Solomon:
>> On Aug 16, 2011, at 12:06 PM, David Kastrup wrote:
>>> If we can't pass the filenames to a call of lys-to-tely because of
>>> command line length limits, I don't see us passing
Am Tuesday, 16. August 2011, 12:47:13 schrieb Mike Solomon:
> On Aug 16, 2011, at 12:06 PM, David Kastrup wrote:
> > If we can't pass the filenames to a call of lys-to-tely because of
> > command line length limits, I don't see us passing the filenames to
> > "echo" or similar shell commands more e
On Aug 16, 2011, at 12:06 PM, David Kastrup wrote:
> Reinhold Kainhofer writes:
>
>> On Di., 16. Aug. 2011 07:46:32 CEST, David Kastrup wrote:
>>
>>> lilyp...@googlecode.com writes:
I think it's literally that we have too many regression test files to
fit into the current allowable
Am Tuesday, 16. August 2011, 12:06:30 schrieben Sie:
> Reinhold Kainhofer writes:
> > I think the lys-to-tely call should stay one call. However, it would
> > be quite simple to write the filenames to a file and pass that to
> > lys-to-tely (like we do it in lilypond-book already for compiling the
Reinhold Kainhofer writes:
> On Di., 16. Aug. 2011 07:46:32 CEST, David Kastrup wrote:
>
>> lilyp...@googlecode.com writes:
>> > I think it's literally that we have too many regression test files to
>> > fit into the current allowable file size.
>>
>> Use
>>
>> for splitting the file lists int
On Di., 16. Aug. 2011 07:46:32 CEST, David Kastrup wrote:
> lilyp...@googlecode.com writes:
> > I think it's literally that we have too many regression test files to
> > fit into the current allowable file size.
>
> Use
>
> for splitting the file lists into two groups, like those starting with
lilyp...@googlecode.com writes:
> Status: Accepted
> Owner:
> Labels: Type-Build Priority-Critical
>
> New issue 1821 by percival.music.ca: GUB argument list too long
> http://code.google.com/p/lilypond/issues/detail?id=1821
>
> trying to build lilypond-test results in this:
>
> make[2]: exec
Comment #3 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
I'd love it if this could be fixed in lilypond git instead of GUB.
Here's the complete log of
target/linux-x86/log/lilypond-test.log
http://lilypond.org/~graham/li
Comment #2 on issue 1821 by hanw...@gmail.com: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
can you post a more detailed trace?
$ make -n out/collated-files.tely | wc
1 997 23345
certainly the maximum command line length is much larger than 23
Comment #1 on issue 1821 by hanw...@gmail.com: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
this doesn't look like a gub proiblem
$ make -n out/collated-files.tely
/home/hanwen/vc/lilypond/scripts/build/out/lys-to-tely
--name=./out/collated-files.tely --t
Status: Accepted
Owner:
Labels: Type-Build Priority-Critical
New issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
trying to build lilypond-test results in this:
make[2]: execvp: /bin/sh: Argument list too long
make[2]: ***
37 matches
Mail list logo
