Created attachment 321650 [details] net-analyzer:wireshark-1.8.1:20120818-172140.log The gnutls/libgcrypt dependencies need looking into.
You mean you can't make it do this? [ebuild R ~] net-analyzer/wireshark-1.8.2-r1 USE="caps geoip gtk ipv6 kerberos lua pcap portaudio python smi ssl zlib -adns -doc -doc-pdf -gcrypt -libadns -profile (-selinux)"
I can confirm this issue. Before installing libgcrypt a build with -gcrypt failed (only caps, ipv6, ssl, zlib enabled).
Should be fixed in 1.8.3-r1. Please test and confirm.
I tested wireshark with USE="ssl -ipsec" (as gcrypt USE flag has been renamed to ipsec) and the SSL dissector doesn't work at all, it's not even compiled in. It's because it depends on both gnutls and libgcrypt. And because compiling wireshark with libgcrypt enables more features than just ipsec decryption[1], I don't think the rename was good. [1] Run `grep -r '#if.*LIBGCRYPT' .|cut -f1 -d':'|sort|uniq` in wireshark sources to get a list of files that include features depending by libgcrypt, packet-ipsec.c is just one of 17. So configure option description, which mentions only ipsec, is wrong.
How about USE=crypto, then?
(In reply to comment #5) > How about USE=crypto, then? Sounds good. And, because the SSL dissector requires --with-gcrypt, REQUIRED_USE="ssl? ( crypto )", which would allow to drop the "ssl? ( dev-libs/libgcrypt )" dependency. BTW, did you notice my feedback in bug #436212? I'm asking because I don't see you being the assignee or CC'ed.
(In reply to comment #6) > (In reply to comment #5) > > How about USE=crypto, then? > > Sounds good. I picked USE=crypt instead as that is widely used in the tree already. > And, because the SSL dissector requires --with-gcrypt, > REQUIRED_USE="ssl? ( crypto )", which would allow to drop the "ssl? ( > dev-libs/libgcrypt )" dependency. This is where it gets tricky. Apparently with USE=ssl we do not even set --with-ssl at this time, unless we count in the ugly hack enabled only when `use kerberos'. > BTW, did you notice my feedback in bug #436212? I'm asking because I don't > see you being the assignee or CC'ed. I read netmon@g.o. Also, I am trying to come up with a single fix for all these issues, so it's a matter of getting to grips with the way the configure script works - and maybe we should patch that up as well.
(In reply to comment #7) > I picked USE=crypt instead as that is widely used in the tree already. Ah, right. I thought "crypto" is what is already used widely. > This is where it gets tricky. Apparently with USE=ssl we do not even set > --with-ssl at this time, unless we count in the ugly hack enabled only when > `use kerberos'. And it's correct. Wireshark doesn't use OpenSSL at all. It seems to me that the main reason for the existence of --with-ssl in Wireshark is to make people aware that there is a potential licensing problem if Wireshark is linked to krb5 library which is linked to OpenSSL. Of course you can patch configure to avoid that hack in the ebuild.
Created attachment 347480 [details] wireshark-1.10.0_rc1 build.log.gz I'm getting a build failure today with wireshark-1.10.0_rc1[-crypt] that looks very similar to this one. Is this basically the same bug or should I open a fresh report?
(In reply to comment #9) To me it's the same issue. As I've already stated, with current build system setup in Wireshark, crypto USE flag should be required if ssl USE flag is enabled.
(In reply to comment #6) > And, because the SSL dissector requires --with-gcrypt, > REQUIRED_USE="ssl? ( crypto )", which would allow to drop the "ssl? ( > dev-libs/libgcrypt )" dependency. Fixed in wireshark-1.8.6-r1 and wireshark-1.10.0_rc1.
*** Bug 468818 has been marked as a duplicate of this bug. ***
*** Bug 469018 has been marked as a duplicate of this bug. ***
