------- Comment #11 from lucabon at interfree dot it 2010-02-12 17:18 ------- (In reply to comment #10) > Does slackware provide packaging files to show how they build their gcc?
Yes, sure. It is a "standard" build, with ecj.jar placed in the top source tree, and it is exactly the same build script between 32 and 64 bits (always x86 architecture), but only 64 bits has the problem. I could try another x86_64 distribution, but I think the problem is into gcc java interpreter... > Does your stock gcj compile simple java code like... > with just 'gcj --main=testme -O testme.java'? Yes, the problem seems to be only if ecj.jar (run by ecj1/gij interpreter) has to compile many .java source files and in the same time it has to keep in memory many bytecode .class file (option -fzip-target), like in pdftk. If you run ecj.jar by Sun java interpreter or if you fully compile ecj.jar with gcj to build a complete ecj1 (not only a wrapper for gij), pdftk compilation works fine. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41802
