I did an emerge fop. The emerge process stop with an out of memory error: c/codegen/font-file.xsl [style] Warning: the task name <style> is deprecated. Use <xslt> instead. [style] Processing /var/tmp/portage/dev-java/fop-0.93/work/fop-0.93/src/codegen/ZapfDingbats.xml to /var/tmp/portage/dev-java/fop-0.93/work/fop-0.93/build/gensrc/org/apache/fop/fonts/base14/ZapfDingbats.java [style] Loading stylesheet /var/tmp/portage/dev-java/fop-0.93/work/fop-0.93/src/codegen/font-file.xsl compile-java: [mkdir] Created dir: /var/tmp/portage/dev-java/fop-0.93/work/fop-0.93/build/classes [javac] Compiling 827 source files to /var/tmp/portage/dev-java/fop-0.93/work/fop-0.93/build/classes [javac] [javac] [javac] The system is out of resources. [javac] Consult the following stack trace for details. [javac] java.lang.OutOfMemoryError BUILD FAILED /var/tmp/portage/dev-java/fop-0.93/work/fop-0.93/build.xml:313: Compile failed; see the compiler error output for details. Total time: 26 seconds !!! ERROR: dev-java/fop-0.93 failed. Call stack: ebuild.sh, line 1614: Called dyn_compile ebuild.sh, line 971: Called qa_call 'src_compile' environment, line 4851: Called src_compile fop-0.93.ebuild, line 77: Called eant '-Djdk14.present=true' '-Djce.present=true' 'package' 'javadocs' java-utils-2.eclass, line 1815: Called die !!! eant failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/dev-java/fop-0.93/temp/build.log'. !!! When you file a bug report, please include the following information: GENTOO_VM=blackdown-jdk-1.4.2 CLASSPATH="" JAVA_HOME="/opt/blackdown-jdk-1.4.2.03" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="javac" and of course, the output of emerge --info Reproducible: Always Steps to Reproduce: 1. emerge =dev-java/fop-0.93 2. 3. Actual Results: fop was not installed Expected Results: fop should be installed
How much memory do you have?
physical: 2 GB free RAM: about 1 GB SWAP: 3 GB
3Gb Swap !!! dam thats a lot. Just in process of hunting down optimal amount of to pass to thru -Xmx currently looks like 256 is good.
Ok. so here is the sad sad story. fop's javadocs will not build on amd64. I tried cranking Xmx over 1g still with no luck and using ecj-3.2. Currently I have package.use.mask'd the doc use flag for >=fop-0.93. so sorry no javadocs will be available. I quick look on the web page did not show them to be downloadable separately. As it looks like we will have to use upstream produced javadocs for amd64. the ebuild is now depending on eclipse-ecj-3.2 and has ANT_OPTS="-Xmx256M" set. I have just committed, so this fix should hit the rsync mirrors in a couple of hours. This bug will stay open until doc are available for amd64.
(In reply to comment #4) > > fop's javadocs will not build on amd64. I tried cranking Xmx over 1g still > with no luck and using ecj-3.2. ecj does not have anything to do with javadocs. Could try how well gjdoc does.
I just built this with the doc flag, and after addressing an unreasonable 2.3G of virtual memory to create the javadocs, it seemed to build just fine. I'm not sure if 2.3G is still considered a DOS on a 64-bit system, so the mask probably still makes some sense.
Just built fop-0.95 with the doc useflag enabled on an amd64. Valgrind segfaults, so the numbers below are taken from top. Virtal size < 1.1GB Residual size < 270MB Seems like the mask could be removed and this bug be closed.
Package has undergone an update. Consider using fop-2.0.
