Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 31750 - error configuering kdebindings-3.1.4 because of an error in the configuration of the Java home in ebuild
Summary: error configuering kdebindings-3.1.4 because of an error in the configuration...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-22 10:20 UTC by Manuel Schneider
Modified: 2003-11-01 07:09 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 Manuel Schneider 2003-10-22 10:20:53 UTC
When trying to emerge kdebindings, I get errors about the host system couldn't 
be identified, the parameter /opt/blackdown-jdk-1.3.1 is not a valied system 
type.


Reproducible: Always
Steps to Reproduce:
1. have blackdown-jdk-1.3.1 installed
2. emerge kdebindings
3. voila

Actual Results:  
Investigating the ebuild of kdebindings-3.1.4 I found out that there is a line 
use java        && myconf="$myconf --with-java=$(java-config --jdk-home)"       
|| myconf="$myconf --without-java"
that adds the location of the jdk via parameter to the configure script of 
kdebindings.
Checking the output of java-config --jdk-home I got the following result:
JDK_HOME: /opt/blackdown-1.3.1
So the reason of the problem is, that configure doesn't get an right parameter 
for the location of jdk, because of the JDK_HOME: and the following blank 
/opt/blackdown-1.3.1 will be interpreted as an own parameter, in this case for 
the HOST definition.
My quick and dirty solution was to change the line into 
use java        && myconf="$myconf --with-java=/opt/blackdown-1.3.1"       || 
myconf="$myconf --without-java"

So it works.
Comment 1 Caleb Tennis (RETIRED) gentoo-dev 2003-11-01 07:09:29 UTC
should now be fixed in portage.  please test and make sure.