Closed
Bug 327469
Opened 18 years ago
Closed 18 years ago
"argument list too long" when compiling javaxpcom
Categories
(Core Graveyard :: Java to XPCOM Bridge, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.8.1
People
(Reporter: benjamin, Assigned: benjamin)
Details
(Keywords: fixed1.8.0.2, fixed1.8.1, Whiteboard: [nvn-dl])
Attachments
(1 file)
2.97 KB,
patch
|
jhpedemonte
:
review+
|
Details | Diff | Splinter Review |
Patch coming up shortly to use an @file to specify the filenames to compile. I'm not sure why I'm seeing this now and not other times, it's perhaps related to what shell I'm making in, but this is a more reliable solution in general because many platforms have hard limits on the length of a command line.
Assignee | ||
Comment 1•18 years ago
|
||
Attachment #212115 -
Flags: review?(jhpedemonte)
Assignee | ||
Comment 2•18 years ago
|
||
http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html#commandlineargfile
Comment 3•18 years ago
|
||
Comment on attachment 212115 [details] [diff] [review] Use @java.files, rev. 1 Odd, I haven't had any problems with xargs on any of the 3 major platforms. But this is an elegant solution. Just need to add "java.files" to GARBAGE. With that, r=jhpedemonte. We should also get this on the branches.
Attachment #212115 -
Flags: review?(jhpedemonte) → review+
Comment 4•18 years ago
|
||
bsmedberg checked this patch in to trunk and branches.
Updated•18 years ago
|
Whiteboard: [nvn-dl]
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•