Bug 3020 – Error when emerging dev-libs/aterm-1.6.6

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Jens Schittenhelm 2002-05-25 09:37:17 UTC]

When I emerge aterm I get following error message:

Error: The ebuild did not complete sucessfully.
Function src_compile, Line 22, Exitcode 2
(no error message)

Emerge aborted

Somewhere in the middle of the compiling messages is following line:
/bin/sh: javac: command not found

[Comment 1 Jens Schittenhelm 2002-05-26 03:41:57 UTC]

Bug is reproductible. 
 
Making all in java 
make[1]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java' 
Making all in aterm 
make[2]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm' 
Making all in visitor 
make[3]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm/visitor' 
CLASSPATH=../../../java/:./../../../java/:$CLASSPATH javac -d ../../../java/  
Visitable.java Visitor.java VisitFailure.java TopDown.java 
/bin/sh: javac: command not found 
make[3]: *** [classjava.stamp] Error 127 
make[3]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm/visitor' 
make[2]: *** [all-recursive] Error 1 
make[2]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm' 
make[1]: *** [all-recursive] Error 1 
make[1]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java' 
make: *** [all-recursive] Error 1 
Making all in aterm 
make[1]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/aterm' 
make[1]: Nothing to be done for `all'. 
make[1]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/aterm' 
Making all in utils 
make[1]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/utils' 
make[1]: Nothing to be done for `all'. 
make[1]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/utils' 
Making all in test 
make[1]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/test' 
make[1]: Nothing to be done for `all'. 
make[1]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/test' 
Making all in java 
make[1]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java' 
Making all in aterm 
make[2]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm' 
Making all in visitor 
make[3]: Entering directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm/visitor' 
CLASSPATH=../../../java/:./../../../java/:$CLASSPATH javac -d ../../../java/  
Visitable.java Visitor.java VisitFailure.java TopDown.java 
/bin/sh: javac: command not found 
make[3]: *** [classjava.stamp] Error 127 
make[3]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm/visitor' 
make[2]: *** [all-recursive] Error 1 
make[2]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java/aterm' 
make[1]: *** [all-recursive] Error 1 
make[1]: Leaving directory 
`/var/tmp/portage/aterm-1.6.6/work/aterm-1.6.6/java' 
make: *** [all-recursive] Error 1 
 
!!! ERROR: The ebuild did not complete successfully. 
!!! Function src_compile, Line 22, Exitcode 2 
!!! (no error message) 
 
!!! emerge aborting on  /usr/portage/dev-libs/aterm/aterm-1.6.6.ebuild . 

[Comment 2 Karl Trygve Kalleberg (RETIRED) 2002-05-28 14:06:52 UTC]

I'll look into it. In the meantime, make sure that java works at all, and that
you have a javac in root's path. (Use java-config to set up java if not).

[Comment 3 Jens Schittenhelm 2002-05-29 05:45:26 UTC]

I checked this out and found that during the installation of openoffice-bin my
java-configuration was messed up. I'd had the blackdown-jdk as system-wide
setting but somehow this has changed to the blackdown-jre - so no javac was
available.

After setting back to the jdk, the installation of aterm worked fine.
Sorry.. should have checked this out first, before submitting a bug
*getting red*

I suggest to change the ebuild script in thin way that it checks for:
a) is java installed
b) is a javac available?
If jdk ist installed as a dependency of other packages it needs to be set up
automatically before continuing with other packages that may rely on it.

[Comment 4 Karl Trygve Kalleberg (RETIRED) 2002-06-03 17:57:33 UTC]

Yes, the java ebuilds are going to be reworked.