This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: input line is too long
- From: "Erik Poupaert" <erik dot poupaert at chello dot be>
- To: "Dhek Bhun Kho" <bhun at chello dot nl>
- Cc: <java at gcc dot gnu dot org>
- Date: Sun, 22 Dec 2002 00:11:04 +0100
- Subject: RE: input line is too long
>>>> I'd like to know too. The only way I know at the moment is in your
case,
compile everything with jikes if you haven't been able to track
dependencies between sources or keep the number of files within a
package relatively small. Then jar everything up and generate a library:
GCJ seems to have a problem with figuring out dependencies between source
files. GCJ does not seem to have any concept of "sourcetree", only of
"classpath". I haven't been able to get one single alternative way
operational, except for using Jikes.
>>>>> gjc --shared -o lib-package.so package.jar
I don't know why, but that fails consistently in GCJ/minGW.
GCJ never manages to solve dependencies in the jar that it is busy
compiling. It manages, however, to use a foldertree of .class files to
resolve dependencies. So, I first create this foldertree of .class files
with jikes, and then I use it as a classpath for GCJ. By the way, it only
works with jikes. GCJ goes abend on .class files generated with the JDK1.4
javac; something to do with the exception tables in in the .class files.
Jikes is a brilliant "header-file" producer for GCJ!
Another bizar thing: Jikes compiles sources about a 100 times faster than
GCJ. Admitted that GCJ does a bit more work, but not a hundred times!