Opened 11 years ago
Closed 11 years ago
#39291 closed defect (fixed)
wireshark @1.8.6_2: configure cannot find gtk2
Reported by: | dershow | Owned by: | opendarwin.org@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | hsivank@…, cooljeanius (Eric Gallager) | |
Port: | wireshark |
Description
I have wireshark 1.8.6_1 installed and just tried to upgrade to 1.8.6_2, but it fails in the configuration stage:
---> Computing dependencies for wireshark ---> Configuring wireshark Error: org.macports.configure for port wireshark returned: configure failure: command execution failed Please see the log file for port wireshark for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_wireshark/wireshark/main.log Error: Unable to upgrade port: 1
My log file concludes as follows:
:info:configure checking for pkg-config... /opt/local/bin/pkg-config :info:configure checking for GTK+ - version >= 2.12.0 and < 3.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: Neither Qt nor GTK+ 2.12 or later are available, so Wireshark can't be compiled :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_wireshark/wireshark/work/wireshark-1.8.6" && ./configure --prefix=/opt/local --with-libsmi=/opt/local --disable-usr-local --with-adns=/opt/local --without-c-ares --with-geoip=/opt/local --with-gnutls=yes --with-libgcrypt-prefix=/opt/local --with-lua=/opt/local --enable-ipv6 --with-pcap=/opt/local --with-ssl=/opt/local --with-zlib=/opt/local --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --with-portaudio=/opt/local --disable-warnings-as-errors --with-krb5=/opt/local --without-python :info:configure Exit code: 1 :error:configure org.macports.configure for port wireshark returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "$procedure $targetname" :info:configure Warning: targets not executed for wireshark: org.macports.install org.macports.configure org.macports.build org.macports.destroot :notice:configure Please see the log file for port wireshark for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_wireshark/wireshark/main.log
But I do have a normal macports install of gtk+ and Qt:
qt4-mac @4.8.4_6 (active)
gtk2 @2.24.18_0+universal+x11 (active)
So, it seems that wireshark is somehow not looking in the right place when it is building?
Thanks,
Attachments (3)
Change History (11)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
Cc: | hsivank@… added; opendarwin.org@… removed |
---|---|
Owner: | changed from macports-tickets@… to opendarwin.org@… |
Summary: | Wireshark upgrade fails → wireshark @1.8.6_2: configure cannot find gtk2 |
comment:3 Changed 11 years ago by neverpanic (Clemens Lang)
Problem is probably caused by the icu update. I'd expect some library still links against the old (now missing) icu and the test binary thus fails to execute. Finding the broken library and revbumping it should fix this.
comment:4 follow-up: 5 Changed 11 years ago by dershow
I did notice that icu an upgrade at the same time from 49.1.2_1 to 51.2_0. Why should something completely different, that links against icu, cause a wireshark problem? What I see depending on icu, on my system is just:
$port dependents icu boost depends on icu gimp2 depends on icu harfbuzz depends on icu webkit-gtk depends on icu
I just did another clean and upgrade, and I am attaching the full log.
comment:5 Changed 11 years ago by neverpanic (Clemens Lang)
Replying to dersh@…:
I did notice that icu an upgrade at the same time from 49.1.2_1 to 51.2_0. Why should something completely different, that links against icu, cause a wireshark problem?
Because gtk2 might link against icu, because it links against harfbuzz and autotools magic pulls in each and every dependent library in the linking process.
I just did another clean and upgrade, and I am attaching the full log.
Unfortunately main.log
isn't very helpful in this case. Please locate config.log
in $(port work wireshark)
and also attach that.
Changed 11 years ago by dershow
Attachment: | config.log added |
---|
Changed 11 years ago by leonfauster@…
Attachment: | config.2.log added |
---|
error: Linking with liblua failed
comment:7 Changed 11 years ago by neverpanic (Clemens Lang)
That's two different errors. One is:
dyld: Library not loaded: /opt/local/lib/libicule.49.dylib Referenced from: /opt/local/lib/libgtk-x11-2.0.0.dylib Reason: image not found
which should already be fixed. Run selfupdate and upgrade outdated.
The other one is that Lua's API changed and wireshark isn't compatible with Lua 5.2.
comment:8 Changed 11 years ago by neverpanic (Clemens Lang)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please clean wireshark, try upgrading again, and attach
main.log
.