[MacPorts] #47171: tig @2.1 Configure error - command execution failed
MacPorts
noreply at macports.org
Sun May 3 13:48:27 PDT 2015
#47171: tig @2.1 Configure error - command execution failed
---------------------------------+--------------------------------
Reporter: cengizc+macports@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.3.3
Resolution: invalid | Keywords:
Port: tig |
---------------------------------+--------------------------------
Changes (by cal@…):
* status: new => closed
* resolution: => invalid
Comment:
cengizc: Your log file suggests that wxwin.m4 was not installed by a
MacPorts port. Since aclocal suggests it did not exist either, I'm
assuming it was a dangling symlink (or a symlink to a file hidden by trace
mode, which would also appear as a dangling symlink in this case). I would
expect any wxwidgets port that ships a file like this to register it
correctly; so, it was (a) not installed by a MacPorts port, in which case
deleting it was fine, (b) installed by a MacPorts port but not registered
as file installed by that port, which would be a bug in that port, (c)
deliberately not registered by a port, in which case I'm wondering why
somebody would choose to do that. In any case, deleting was probably the
right thing to do in this case, and I'm going to close this ticket.
philippe: Your problem isn't the same, because the configure phase
succeeds but building fails later on. You should file this as a separate
ticket or ask for help on the [[MailingLists|macports-users mailing
list]]. In your log file, I see
{{{
1594 :info:build dyld: lazy symbol binding failed: Symbol not found:
_gzopen
1595 :info:build Referenced from: /opt/local/lib/libxml2.2.dylib
1596 :info:build Expected in: flat namespace
}}}
which suggests that for some reason your `/opt/local/lib/libxml2.2.dylib`
doesn't correctly reference `/opt/local/lib/libz.1.dylib`, which should
provide this symbol. The additional "Expected in: flat namespace" makes me
wonder whether you somehow modified your environment, i.e. by setting any
`DYLD_` environment variables – but as discussed, please open a new ticket
or mail to the mailing list for help on this.
--
Ticket URL: <https://trac.macports.org/ticket/47171#comment:13>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list