This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

input line is too long


Hi

I've got a project with 280 *.o files. gcj is still capable of linking that
on the commandline (win2K). Most of the files are actually generated by
upstream source generators.

Then, I've got a related project with 436 *.o files, also mostly generated
from 1 grammarfile and 2 modelfiles that get translated into java sources;
and about 35 custom-written java source files. Well, at 436 files gcj fails
to link it. I get "The input line is too long". The commandline is 22.9 Kb
big, and therefore still well under the win2K limit of 32 Kb.

And I can't get away with using a response file:
"""
@file A file containing a whitespace-separated list of input file names.
(Currently, these must all be .java source files, but that may change.) Each
named file is compiled, just as if it had been on the command line.
"""

This project may grow to well over a thousand *.o files.

Jikes doesn't have any problem with this. And linking bytecode consist in
simply zipping the class foldertree into one jar file. Therefore, I can
still run the project in bytecode, but I can't run it natively. By the way,
it's only a 1.5 Mb jarfile; I still can grow that one, way up.

Is there any other way to link a foldertree with *.o files without running
into all kinds of limitations?

Greetings
Erik Poupaert



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]