Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73235 - antlr failed to install "Java VM java failed"
Summary: antlr failed to install "Java VM java failed"
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-03 09:02 UTC by Hoyle Anderson
Modified: 2004-12-06 08:24 UTC (History)
0 users

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 Hoyle Anderson 2004-12-03 09:02:16 UTC
when I emerge antlr (which apparently is a new dep for ant), I get the below message.  I can emerge ant-core OK

[ebuild  N    ] dev-java/antlr-2.7.3  
[ebuild  N    ] dev-java/ant-tasks-1.6.2-r5  
[ebuild     U ] dev-java/ant-1.6.2-r6 [1.5.4-r1] 


Reproducible: Always
Steps to Reproduce:
1.emerge antlr

Actual Results:  
>>> Source unpacked.
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking if examples must be built... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking if we are using Cygwin/MinGW... no
no
checking if we prefer gcj built over normal java... no
checking if BOOTSTRAP_JAR is set... no
checking for ar... /usr/bin/ar
checking for as... /usr/bin/as
checking for cygpath... no
checking for i686-pc-linux-gnu-gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for i686-pc-linux-gnu-g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for doxygen... doxygen
checking for a BSD-compatible install... /bin/install -c
CLASSPATH set to:
/opt/sun-j2ee-1.3.1/lib/j2ee.jar:.
IMPORTANT: make sure the current directory containing configure
is in the CLASSPATH
checking if /opt/sun-jdk-1.4.2.06/bin/javac works... yes
checking for kaffe... no
checking for java... java
checking for uudecode... yes
checking if uudecode can decode base 64 file... yes
checking if java works... configure: error: The Java VM java failed (see
config.log, check the CLASSPATH?)

!!! ERROR: dev-java/antlr-2.7.3 failed.
!!! Function econf, Line 449, Exitcode 1
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.

Expected Results:  
antlr to be installed.

java-config -L
[sun-jdk-1.4.2.06] "Sun JDK 1.4.2.06" (/etc/env.d/java/20sun-jdk-1.4.2.06) *
java-config -o
/opt/sun-jdk-1.4.2.06
java-config -c
/opt/sun-jdk-1.4.2.06/bin/javac
java-config -O
/opt/sun-jdk-1.4.2.06

CLASSPATH=/opt/sun-j2ee-1.3.1/lib/j2ee.jar:.
Comment 1 Hoyle Anderson 2004-12-06 08:24:35 UTC
I determined this was not an antlr problem, but rather the result of a bad symlink   which was pointing to the older jre.  changing /usr/local/bin/java to point to the new java fixed the problem.