"argument list too long" when compiling javaxpcom

RESOLVED FIXED in mozilla1.8.1

Status

Core Graveyard
Java to XPCOM Bridge
RESOLVED FIXED
12 years ago
3 years ago

People

(Reporter: bsmedberg, Assigned: bsmedberg)

Tracking

({fixed1.8.0.2, fixed1.8.1})

Trunk
mozilla1.8.1
x86
All
fixed1.8.0.2, fixed1.8.1

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nvn-dl])

Attachments

(1 attachment)

(Assignee)

Description

12 years ago
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

12 years ago
Created attachment 212115 [details] [diff] [review]
Use @java.files, rev. 1
Attachment #212115 - Flags: review?(jhpedemonte)
(Assignee)

Comment 2

12 years ago
http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javac.html#commandlineargfile
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+
bsmedberg checked this patch in to trunk and branches.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Keywords: fixed1.8.0.2, fixed1.8.1
Resolution: --- → FIXED

Updated

12 years ago
Whiteboard: [nvn-dl]
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.