Azureus has a new dep, dev-java/bcprov. Please test and keyword azureus and bcprov on amd64 and ppc.
Building bcprov-1.31-r1 and azureus-2.4.0.2 with ~x86 keyword on my ~amd64 system, I get this error on azureus build: init: [echo] Building Azureus2.jar... [mkdir] Created dir: /var/tmp/portage/azureus-2.4.0.2/work/azureus/dist compile: [javac] Compiling 1737 source files to /var/tmp/portage/azureus-2.4.0.2/work/azureus [javac] The system is out of resources. [javac] Consult the following stack trace for details. [javac] java.lang.OutOfMemoryError BUILD FAILED /var/tmp/portage/azureus-2.4.0.2/work/azureus/build.xml:31: Compile failed; see the compiler error output for details. Total time: 11 seconds !!! ERROR: net-p2p/azureus-2.4.0.2 failed. Call stack: ebuild.sh, line 1545: Called dyn_compile ebuild.sh, line 940: Called src_compile azureus-2.4.0.2.ebuild, line 71: Called eant 'jar' java-utils-2.eclass, line 1224: Called die !!! eant failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! 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" Portage 2.1.1_pre3-r4 (default-linux/amd64/2006.0, gcc-4.1.1/amd64-vanilla, glibc-2.4-r3, 2.6.17-ck1-r2 x86_64) ================================================================= System uname: 2.6.17-ck1-r2 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.1 ccache version 2.4 [enabled] app-admin/eselect-compiler: 2.0.0_rc2-r1 dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r2 dev-util/confcache: 0.4.2-r1 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r1, 2.16.93, 2.17, 2.17.50.0.2, 2.17.50.0.3 sys-devel/gcc-config: 2.0.0_rc1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.16 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe -ggdb" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib64/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/eselect/compiler /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=k8 -O2 -pipe -ggdb -ffriend-injection" DISTDIR="/var/portage/distfiles" EMERGE_DEFAULT_OPTS="" FEATURES="autoconfig ccache confcache distlocks fixpackages parallel-fetch sandbox sfperms splitdebug strict" GENTOO_MIRRORS="http://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://gentoo.osuosl.org/ " LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LINGUAS="en" MAKEOPTS="-j2" PKGDIR="/var/portage/packages" PORTAGE_RSYNC_EXTRA_OPTS="--timeout=120" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/wrobel /usr/portage/local/layman/gentopia /usr/portage/local/layman/sunrise /usr/portage/local/layman/portage-xgl /usr/portage/local/layman/break-my-gentoo-main" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="amd64 X aac alsa avi bash-completion berkdb bitmap-fonts bzip2 cairo cdr cli crypt cups dbus debug dlloader dri dvd dvdr eds emboss encode esd firefox flac foomaticdb fortran gdbm gif glitz gnome gpm gstreamer gtk gtk2 hal imlib ipv6 isdnlog java jpeg kde kdehiddenvisibility ldap lzw lzw-tiff mad mono mp3 mpeg ncurses nls nptl nptlonly ogg opengl pam pcre pdflib perl pic png pppd python qt qt3 quicktime readline reflection ruby samba sdl session spell spl sqlite ssl tcpd theora tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis xml xml2 xorg xpm xv zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux linguas_en userland_GNU video_cards_vesa video_cards_nvidia" Unset: CTARGET, INSTALL_MASK, LDFLAGS I'm assuming that's a java VM out-of-memory error as I am running this on a system with 1GB RAM/2GB swap and am nowhere near out of memory. I successfully upgraded to the new java system the day after it was available and have had no other java-related issues.
Could you try with sun-jdk-1.5? I recall there often being an issue with blackdown on amd64 getting OutOfMemoryErrors.
(In reply to comment #2) > Could you try with sun-jdk-1.5? I recall there often being an issue with > blackdown on amd64 getting OutOfMemoryErrors. > eselect java-vm list Available Java Virtual Machines: [1] blackdown-jdk-1.4.2 [2] sun-jdk-1.5 system-vm user-vm [3] sun-jre-bin-1.5 sudo emerge azureus These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild N ] net-p2p/azureus-2.4.0.2 USE="-source" 0 kB Total size of downloads: 0 kB Would you like to merge these packages? [Yes/No] >>> Emerging (1 of 1) net-p2p/azureus-2.4.0.2 to / * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking Azureus_2.4.0.2_source.zip ;-) ... [ ok ] * Using: blackdown-jdk-1.4.2 Perhaps I don't understand the new java system -- if I set user and system VM to sun-jdk-1.5 and it still uses blackdown, does that mean there's something in the ebuild forcing blackdown?
(In reply to comment #3) > Perhaps I don't understand the new java system -- if I set user and system VM > to sun-jdk-1.5 and it still uses blackdown, does that mean there's something > in the ebuild forcing blackdown? > There's a difference between the build vm, and the system/user vm. It's configured by /etc/java-config-2/build/jdk.conf You can also test by going: JAVA_PKG_FORCE_VM=sun-jdk-1.5 emerge foo to use it temporarily.
Same problem with sun-jdk-1.5: * Using: sun-jdk-1.5 >>> Unpacking source... >>> Unpacking Azureus_2.4.0.2_source.zip to /var/tmp/portage/azureus-2.4.0.2/work >>> Source unpacked. >>> Unpacking Azureus_2.4.0.2_source.zip to /var/tmp/portage/azureus-2.4.0.2/work/azureus * Applying various patches (bugfixes/updates) ... * azureus-cache-size.patch ... [ ok ] * azureus-no-restart.patch ... [ ok ] * azureus-remove-manifest-classpath.patch ... [ ok ] * azureus-remove-win32-osx-platforms.patch ... [ ok ] * azureus-remove-win32-PlatformManagerUpdateChecker.patch ... [ ok ] * Done with patching Rewriting ./build.xml >>> Compiling source in /var/tmp/portage/azureus-2.4.0.2/work/azureus ... /usr/bin/ant: line 161: arch: command not found Buildfile: build.xml init: [echo] Building Azureus2.jar... [mkdir] Created dir: /var/tmp/portage/azureus-2.4.0.2/work/azureus/dist compile: [javac] Compiling 1737 source files to /var/tmp/portage/azureus-2.4.0.2/work/azureus [javac] The system is out of resources. [javac] Consult the following stack trace for details. [javac] java.lang.OutOfMemoryError: Java heap space BUILD FAILED /var/tmp/portage/azureus-2.4.0.2/work/azureus/build.xml:31: Compile failed; see the compiler error output for details. Total time: 26 seconds !!! ERROR: net-p2p/azureus-2.4.0.2 failed. Call stack: ebuild.sh, line 1545: Called dyn_compile ebuild.sh, line 940: Called src_compile azureus-2.4.0.2.ebuild, line 71: Called eant 'jar' java-utils-2.eclass, line 1224: Called die !!! eant failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.07" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="javac" I see the JAVACFLAGS forced blackdown to be used before.
Maybe -Xmx248m added to ANT_OPTS in ebuild is still not enough, try to raise that to 512m and see?
(In reply to comment #6) > Maybe -Xmx248m added to ANT_OPTS in ebuild is still not enough, try to raise > that to 512m and see? > After making that change I still get the same error with both blackdown-jdk and sun-jdk.
You may want to keep trying to bump up the max memory size, on the upwards of 768 or 1024 mb.
(In reply to comment #8) > You may want to keep trying to bump up the max memory size, on the upwards of > 768 or 1024 mb. > I've taken it as far as -Xmx2048m with no change in the error. I can't believe this is the problem. I've been using azureus-bin for the last few months to get 2.4.0.2, but before that release I never had a problem building azureus. Can the requirements have really jumped so much between versions?
I tried to emerge it yesterday and it failed under both blackdown and sun jdks both with out of memory errors. Today I tried a suggestion that seemed to work. JAVA_PKG_FORCE_COMPILER=ecj-3.1 emerge azureus When compiling that way, the heap size of -Xmx248m was plenty. Seems to be the only way to compile the packages without out of memory errors. I will get with nichoj on this ASAP, and see about addressing the ebuild.
I added java-pkg_force-compiler to java-utils-2.eclass. I updated the ebuild to do: use amd64 && java-pkg_force-compiler ecj-3.1 It also depends on dev-java/eclipse-ecj now. Keyworded for amd64.
(In reply to comment #11) > I added java-pkg_force-compiler to java-utils-2.eclass. I updated the ebuild to > do: > > use amd64 && java-pkg_force-compiler ecj-3.1 > > It also depends on dev-java/eclipse-ecj now. > > Keyworded for amd64. > Works for me, thanks. Do you have a handle on what the problem was? Is it Azureus or blackdown/sun jdks? Or something Gentoo-specific? I ask so I know where and whether to file an upstream bug.
(In reply to comment #12) > (In reply to comment #11) > > I added java-pkg_force-compiler to java-utils-2.eclass. I updated the ebuild to > > do: > > > > use amd64 && java-pkg_force-compiler ecj-3.1 > > > > It also depends on dev-java/eclipse-ecj now. > > > > Keyworded for amd64. > > > Works for me, thanks. > > Do you have a handle on what the problem was? Is it Azureus or blackdown/sun > jdks? Or something Gentoo-specific? I ask so I know where and whether to file > an upstream bug. > The problem is specific to the jdks and as such it was fixed by switching the compiler used.
Added ~ppc
