Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 125319 - ibm-jdk-bin-1.4.2 fails to compile ant-core on PPC
Summary: ibm-jdk-bin-1.4.2 fails to compile ant-core on PPC
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC Linux
: High major (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-06 18:28 UTC by Andy Botting
Modified: 2006-04-10 21:11 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Botting 2006-03-06 18:28:42 UTC
I am having some big problems compiling any java stuff on my fresh 2006.0 install on my G4 Powerbook, with ibm-jdk-bin-1.4.2.03. (also seen this on 1.4.2.04)

What's happening is I want to compile eclipse, but it's failing on ant-core (but not ant-core exclusively)

I do have an older 2005.1 install on another partition, where it works fine. I have even played with my cflags, but they've always been pretty safe ones. 

Has anybody else experienced this, or has any idea how to fix it?

>>> emerge (1 of 29) dev-java/ant-core-1.6.2-r5 to /
>>> md5 files   ;-) ant-core-1.6.2-r5.ebuild
>>> md5 files   ;-) ant-core-1.6.5-r2.ebuild
>>> md5 files   ;-) ant-core-1.5.4-r2.ebuild
>>> md5 files   ;-) files/rpmbuild.patch
>>> md5 files   ;-) files/build.sh-exit-fix.patch
>>> md5 files   ;-) files/1.5.4-ant
>>> md5 files   ;-) files/1.6.2-ant
>>> md5 files   ;-) files/1.6.5-ant
>>> md5 files   ;-) files/digest-ant-core-1.5.4-r2
>>> md5 files   ;-) files/digest-ant-core-1.6.2-r5
>>> md5 files   ;-) files/digest-ant-core-1.6.5-r2
>>> md5 files   ;-) files/1.6.2-scp.patch
>>> md5 src_uri ;-) apache-ant-1.6.2-src.tar.bz2
>>> Unpacking source...
>>> Unpacking apache-ant-1.6.2-src.tar.bz2 to /var/tmp/portage/ant-core-1.6.2-r5/work
tar: A lone zero block at 34226
 * Applying 1.6.2-scp.patch ... [ ok ] 
 * Applying build.sh-exit-fix.patch ... [ ok ]
>>> Source unpacked.
.
... Bootstrapping Ant Distribution
... Compiling Ant Classes
JVMDG217: Dump Handler is Processing Signal 11 - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /var/tmp/portage/ant-core-1.6.2-r5/work/apache-ant-1.6.2/javacore.20060307.021359.5787.txt
JVMDG215: Dump Handler has Processed Exception Signal 11.
./bootstrap.sh: line 135:  5787 Segmentation fault      "${JAVAC}" $BOOTJAVAC_OPTS -d ${CLASSDIR} ${TOOLS}/bzip2/*.java ${TOOLS}/tar/*.java ${TOOLS}/zip/*.java ${TOOLS}/ant/util/regexp/RegexpMatcher.java ${TOOLS}/ant/util/regexp/RegexpMatcherFactory.java ${TOOLS}/ant/types/*.java ${TOOLS}/ant/*.java ${TOOLS}/ant/taskdefs/*.java ${TOOLS}/ant/taskdefs/compilers/*.java ${TOOLS}/ant/taskdefs/condition/*.java
... Failed compiling Ant classes !
Bootstrap FAILED

!!! ERROR: dev-java/ant-core-1.6.2-r5 failed.
!!! Function src_compile, Line 53, Exitcode 1
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.


emerge --info

Portage 2.0.54 (default-linux/ppc/ppc32, gcc-3.4.4, glibc-2.3.5-r3, 2.6.16-rc5 ppc)
=================================================================
System uname: 2.6.16-rc5 ppc 7447A, altivec supported
Gentoo Base System version 1.6.14
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CBUILD="powerpc-unknown-linux-gnu"
CFLAGS="-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
PKGDIR="/mnt/cdrom"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="ppc X alsa audiofile berkdb bitmap-fonts bzip2 cdr crypt cups eds esd exif expat fam fortran gdbm glut gnome gpm gstreamer gtk gtkhtml idn ipv6 java jpeg lcms ldap mad mng mozilla ncurses nls nptl ogg opengl pam perl png python readline ssl tcpd tiff truetype truetype-fonts type1-fonts udev unicode vorbis xml2 zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
Comment 1 Andy Botting 2006-03-06 18:31:08 UTC
Should also have added:

# java-config -L
[ibm-jdk-bin-1.4.2.03] "IBM JDK 1.4.2.03" (/etc/env.d/java/20ibm-jdk-bin-1.4.2.03) *

and that I have done the env-update and source /etc/profile stuff also
Comment 2 Josh Nichols (RETIRED) gentoo-dev 2006-04-10 17:57:34 UTC
Could someone from ppc take a look at this, please?
Comment 3 Wormo (RETIRED) gentoo-dev 2006-04-10 20:32:34 UTC
Two of us on the ppc team (ChrisWhite and myself) have tried to reproduce this without success. The most likely problem though is the kernel, since certain kernels have been known to make java prone to crash. We suggest trying with the current stable kernel and see if the problem persists.
Comment 4 Andy Botting 2006-04-10 21:11:39 UTC
Thanks for looking into it guys. 

This java problem was really kicking my ass, from a fresh install from a stage3-2006.0, but now what I have done is upgrade the world from that stage 3, which would bring down the newer gcc-3.4.5 (and other stuff) and then it worked. 

Not sure if it was actually related to gcc/glibc whatever, but doing that emerge -au world seemed to resolve the problem.

While trying to fix the problem, I was always running the 2.6.16-rc series, up to 2.6.16. I don't think it was kernel related, but can't be certain.