#47171: tig @2.1 Configure error - command execution failed ---------------------------------+-------------------------------- Reporter: cengizc+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: tig | ---------------------------------+-------------------------------- Changes (by cal@…): * cc: cengizc+macports@… (removed) * cc: mk@…, cal@… (added) * keywords: tig => Comment: You don't have to Cc yourself. -- Ticket URL: <https://trac.macports.org/ticket/47171#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#47171: tig @2.1 Configure error - command execution failed ---------------------------------+-------------------------------- Reporter: cengizc+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: tig | ---------------------------------+-------------------------------- Comment (by cengizc+macports@…): Replying to [comment:3 cal@…]:

You don't have to Cc yourself. That was a futile attempt to modify Cc: field.

-- Ticket URL: <https://trac.macports.org/ticket/47171#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X

#47171: tig @2.1 Configure error - command execution failed ---------------------------------+-------------------------------- Reporter: cengizc+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: tig | ---------------------------------+-------------------------------- Comment (by cal@…): Did you try in trace mode as well? You might just happen to have the file installed. -- Ticket URL: <https://trac.macports.org/ticket/47171#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

#47171: tig @2.1 Configure error - command execution failed ---------------------------------+-------------------------------- Reporter: cengizc+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: tig | ---------------------------------+-------------------------------- Comment (by cengizc+macports@…): Replying to [comment:8 cal@…]:

I tried reproducing this in trace mode and couldn't; the build went fine for me.

cengizc: can you try `sudo port clean tig; sudo port -t install tig` and see if that works?

{{{ $ sudo port clean tig; sudo port -t install tig ---> Cleaning tig ---> Computing dependencies for tig ---> Fetching archive for tig ---> Attempting to fetch tig-2.1_0.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/tig ---> Attempting to fetch tig-2.1_0.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/tig ---> Attempting to fetch tig-2.1_0.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/tig ---> Fetching distfiles for tig ---> Verifying checksums for tig ---> Extracting tig ---> Configuring tig Warning: The following file inside the MacPorts prefix not installed by a port was accessed: /opt/local/share/aclocal/wxwin.m4 Error: org.macports.configure for port tig returned: command execution failed Please see the log file for port tig for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_tig/tig/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port tig failed }}} -- Ticket URL: <https://trac.macports.org/ticket/47171#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

#47171: tig @2.1 Configure error - command execution failed ---------------------------------+-------------------------------- Reporter: cengizc+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: tig | ---------------------------------+-------------------------------- Comment (by cengizc+macports@…): Out of desperation, I removed wxwin.m4 file {{{ $ sudo rm /opt/local/share/aclocal/wxwin.m4 }}} and tig was configured successfully. {{{ $ sudo port install -t tig ---> Computing dependencies for tig ---> Configuring tig ---> Building tig ---> Staging tig into destroot ---> Installing tig @2.1_0 ---> Activating tig @2.1_0 ---> Cleaning tig ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. }}} But my autoconf installation is missing a macro now. -- Ticket URL: <https://trac.macports.org/ticket/47171#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X

#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