First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 177585
Alias:
Product:
Component:
Status: ASSIGNED
Resolution:
Assigned To: Java team <java@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: menschmeier <steffen.scheuring@gmx.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 177585 depends on: Show dependency tree
Bug 177585 blocks: 187600
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-05-08 06:54 0000
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

------- Comment #1 From Petteri Räty 2007-05-08 07:02:09 0000 -------
How much memory do you have?

------- Comment #2 From menschmeier 2007-05-08 07:07:38 0000 -------
physical: 2 GB
free RAM: about 1 GB
SWAP: 3 GB

------- Comment #3 From Alistair Bush 2007-05-08 07:14:36 0000 -------
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.

------- Comment #4 From Alistair Bush 2007-05-08 11:17:27 0000 -------
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.

------- Comment #5 From Petteri Räty 2007-05-08 15:48:44 0000 -------
(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.

First Last Prev Next    No search results available      Search page      Enter new bug