[MacPorts] #28683: Wireshark 1.4.4 - configure failure
#28683: Wireshark 1.4.4 - configure failure -------------------------------------+-------------------------------------- Reporter: nick@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: wireshark -------------------------------------+-------------------------------------- OS X 10.6.6, XCode 3.2.5 (1760) Wireshark presently fails to finish installing, failing at the 'Configuring' stage. This has occurred even after an uninstall and clean of wireshark. Terminal output: {{{ [534] $ sudo port install wireshark Password: ---> Computing dependencies for wireshark ---> Configuring wireshark Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details) Log for wireshark is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> adminfabry@dragon:/Volumes/Osmium/Users/fabry [535] $ sudo port clean wireshark ---> Cleaning wireshark adminfabry@dragon:/Volumes/Osmium/Users/fabry [536] $ sudo port uninstall wireshark adminfabry@dragon:/Volumes/Osmium/Users/fabry [537] $ sudo port install wireshark ---> Computing dependencies for wireshark ---> Fetching wireshark ---> Verifying checksum(s) for wireshark ---> Extracting wireshark ---> Configuring wireshark Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details) Log for wireshark is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> }}} The aformentioned log file is attached. Glancing through it, the following lines appear particularly relevant, but I may be mistaken: {{{ :info:configure checking for GTK+ - version >= 2.4.0... no :info:configure *** Could not run GTK+ test program, checking why... :info:configure *** The test program compiled, but did not run. This usually means :info:configure *** that the run-time linker is not finding GTK+ or finding the wrong :info:configure *** version of GTK+. If it is not finding GTK+, you'll need to set your :info:configure *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point :info:configure *** to the installed location Also, make sure you have run ldconfig if that :info:configure *** is required on your system :info:configure *** :info:configure *** If you have an old version installed, it is best to remove it, although :info:configure *** you may also be able to get things to work by modifying LD_LIBRARY_PATH :info:configure configure: error: GTK+ 2.4 or later isn't available, so Wireshark can't be compiled }}} -- Ticket URL: <https://trac.macports.org/ticket/28683> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28683: Wireshark 1.4.4 - configure failure -------------------------------------+-------------------------------------- Reporter: nick@… | Owner: ricci@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: wireshark -------------------------------------+-------------------------------------- Changes (by jmr@…): * owner: macports-tickets@… => ricci@… Comment: Please remember to cc the maintainer. Attach the config.log; it should have details of how the test program failed. -- Ticket URL: <https://trac.macports.org/ticket/28683#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28683: Wireshark 1.4.4 - configure failure -------------------------------------+-------------------------------------- Reporter: nick@… | Owner: ricci@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: wireshark -------------------------------------+-------------------------------------- Comment(by nick@…): Okay, I'm not sure if I was merely a dumbass or if something else was amiss, but I took the next logical step since GTK+ appeared problematic by uninstalling it and reinstalling it and then wireshark built successfully. Sorry for the trouble. {{{ sudo port -c uninstall gtk2 ---> Deactivating gtk2 @2.22.1_1+x11 ---> Cleaning gtk2 ---> Uninstalling gtk2 @2.22.1_1+x11 ---> Cleaning gtk2 adminfabry@dragon:/Volumes/Osmium/Users/fabry [552] $ sudo port install wireshark ---> Computing dependencies for wireshark ---> Dependencies to be installed: gtk2 ---> Fetching gtk2 ---> Verifying checksum(s) for gtk2 ---> Extracting gtk2 ---> Applying patches to gtk2 ---> Configuring gtk2 ---> Building gtk2 ---> Staging gtk2 into destroot ---> Installing gtk2 @2.22.1_1+x11 ---> Activating gtk2 @2.22.1_1+x11 ---> Cleaning gtk2 ---> Configuring wireshark ---> Building wireshark ---> Staging wireshark into destroot ---> Installing wireshark @1.4.4_0 ---> Activating wireshark @1.4.4_0 ---> Cleaning wireshark }}} -- Ticket URL: <https://trac.macports.org/ticket/28683#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28683: Wireshark 1.4.4 - configure failure --------------------------------------+------------------------------------- Reporter: nick@… | Owner: ricci@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: worksforme | Keywords: Port: wireshark | --------------------------------------+------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => worksforme -- Ticket URL: <https://trac.macports.org/ticket/28683#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts