wireshark: configure failure when looking for kerberos5

[george@…]

Apparently also a problem in Wireshark.

[george@…]

wireshark-devel port installation log file

[george@…]

Running the command:

sudo port -v install wireshark-devel +adns+ipv6+libgcrypt+pcre+python27+rtp

Upon running the configure script, installation bombs out with this output:

checking whether to use Kerberos library... yes
checking krb5.h usability... yes
checking krb5.h presence... yes
checking for krb5.h... yes
checking whether the Kerberos library is Heimdal or MIT... no
configure: error: Kerberos not found
Command failed:  cd "/opt/local/var/macports/build/_Users_gthiruva_scratch_macports-trunk_dports_net_wireshark-devel/wireshark-devel/work/wireshark-1.8.5"
&& ./configure --prefix=/opt/local --disable-usr-local --with-pcap=/opt/local --with-ssl=/opt/local --with-zlib=/opt/local 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --disable-warnings-as-errors --with-krb5=/opt/local --without-gnutls
--with-adns=/opt/local --without-c-ares --with-libgcrypt-prefix=/opt/local --enable-ipv6 --with-pcre=/opt/local --with-portaudio=/opt/local 
--with-python 
Exit code: 1
Error: org.macports.configure for port wireshark-devel returned: configure failure: command execution failed
Warning: targets not executed for wireshark-devel: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install
Please see the log file for port wireshark-devel for details:
    /opt/local/var/macports/logs/_Users_gthiruva_scratch_macports-trunk_dports_net_wireshark-devel/wireshark-devel/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port wireshark-devel failed

[larryv (Lawrence Velázquez)]

Thanks for the ticket. In the future, please Cc relevant port maintainers.

This may have something to do with today’s Kerberos kerfuffle. Cc-ing Jeremy and Cal just in case.

[larryv (Lawrence Velázquez)]

Actually, this is probably a a duplicate of #37917, sort of.

[neverpanic (Clemens Lang)]

This is not a duplicate, because a revbump will not fix it.

The problem is caused by Wireshark's configure trying to determine whether it is linking against Heimdal or MIT Kerberos by grepping the krb5.h for "Massachusetts Institute of Technology". With version 1.11 of kerberos5 however, this text is broken into two lines. A simple fix is changing all occurances of this string in configure to "Massachusetts".

[george@…]

Cc Me!

[george@…]

Cc Me!

[george@…]

Cc Me!

[jeremyhu (Jeremy Huddleston Sequoia)]

Wow, that's quite a big fail in the Wireshark's configure script. LOL