[MacPorts] #35786: commons-daemon config problem: java home
MacPorts
noreply at macports.org
Wed Aug 22 13:57:44 PDT 2012
#35786: commons-daemon config problem: java home
-------------------------------+--------------------------------------------
Reporter: vikingjs@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.1.2
Resolution: fixed | Keywords: mountainlion
Port: commons-daemon |
-------------------------------+--------------------------------------------
Changes (by ciserlohn@…):
* status: new => closed
* keywords: mountainlion, JAVA_HOME => mountainlion
* resolution: => fixed
* cc: vikingjs@… (removed)
Comment:
Replying to [ticket:35786 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
[https://trac.macports.org/browser/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 [wiki:DraftKeywordGuidelines]).
--
Ticket URL: <https://trac.macports.org/ticket/35786#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list