commons-daemon config problem: java home

[vikingjs@…]

During update (immediately following selfupdate), recieved the following error:

org.macports.configure for port commons-daemon returned: configure failure: command execution failed

Log file (attached) indicates that JAVA_HOME was not properly set. This is probably related to trunk/dports/_resources/port1.0/group/java-1.0.tcl?rev=96264, but I don't know how all the bits work together, so I thought I'd call attention to this case.

Note that I have updated XCode, agreed to the license, removed old versions, and all that stuff. Other project (e.g., WebKit) build successfully from the command line, so I don't think that's the issue here. Unless I'm missing something, which happens.

A few more tidbits from my machine, since this seems java-related:

iJer:Users Jerry$ java -version
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-12A269)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode)

iJer:Users Jerry$ /usr/libexec/java_home
/Library/Java/JavaVirtualMachines/1.6.0_29-b11-402.jdk/Contents/Home

[vikingjs@…]

log from failed attempt to upgrade commons-daemon

[ciserlohn@…]

Replying to vikingjs@…:

During update (immediately following selfupdate), recieved the following error:

org.macports.configure for port commons-daemon returned: configure failure: command execution failed

Log file (attached) indicates that JAVA_HOME was not properly set. This is probably related to trunk/dports/_resources/port1.0/group/java-1.0.tcl?rev=96264, but I don't know how all the bits work together, so I thought I'd call attention to this case.

This is not related since commons-daemon doesn't use the java port group. But even then it would fail because the java port group only sets JAVA_HOME for the build phase. I modified the java port group to set JAVA_HOME in the configure and destroot phase as well (r96958) and also updated commons-daemon to version 1.0.10 and let it use the java port group (r96959).

Please install commons-daemon again:

$ sudo port clean commons-daemon 
$ sudo port install commons-daemon

P.S.: If you create a ticket you don't need to cc yourself. And please don't set arbitrary keywords (see DraftKeywordGuidelines).

[vikingjs@…]

Thanks for jumping on this. Sorry for cluttering tagspace; I had half a clue but that's often worse than no clue at all.

Cleaned and installed and got the same result; the failure was with commons-daemon-1.0.10_0.darwin_12.x86_64. If I understand your comments, perhaps this fix will not work until your change to the java port group lands? I did a selfupdate/clean/retry and got no love.

[ciserlohn@…]

Replying to vikingjs@…:

Cleaned and installed and got the same result; the failure was with commons-daemon-1.0.10_0.darwin_12.x86_64. If I understand your comments, perhaps this fix will not work until your change to the java port group lands? I did a selfupdate/clean/retry and got no love.

The change to the java port group is already available. Changes to ports or port groups are usually available within 30 minutes after the corresponding commit.
Please try a clean install with debug output enabled:

$ sudo port selfupdate
$ sudo port clean --all commons-daemon
$ sudo port -d install commons-daemon

and attach the log file.

[ciserlohn@…]

JAVA_HOME gets lost when ant carried out by the system command in the pre-build phase. If JAVA_HOME is not set ant assumes JAVA_HOME to be

/System/Library/Frameworks/JavaVM.framework/Home

But on newer system (e.g. mountain lion) JDKs install in

/Library/Java/JavaVirtualMachines

and will cause ant to fail.

Fixed in r96985 and r96989.