Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 382779 - net-analyser/wireshark fails to build with USE="ssl -gcrypt"
Summary: net-analyser/wireshark fails to build with USE="ssl -gcrypt"
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Peter Volkov (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-13 07:17 UTC by Olivier Crete (RETIRED)
Modified: 2011-12-12 06:47 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
patch to unify ssl and gcrypt flags (wireshark-gcrypt-is-ssl.patch,5.78 KB, patch)
2011-09-13 07:17 UTC, Olivier Crete (RETIRED) 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Crete (RETIRED) gentoo-dev 2011-09-13 07:17:36 UTC 
Created attachment 286297 [details, diff]
patch to unify ssl and gcrypt flags

ssl and gcrypt are actually intermingled in the wireshark source code. Trying to make them separate flag just does not build. So the attached patch just puts everything under the ssl use flag.
Comment 1 Peter Volkov (RETIRED) gentoo-dev 2011-09-14 09:24:55 UTC 
Last time I've checked it built and looking in the source made me think different. What version you have failure with? Please, attach, build.log. Thanks.
Comment 2 Olivier Crete (RETIRED) gentoo-dev 2011-09-17 22:56:11 UTC 
1.4.8 and 1.4.9

If you look in dissectors/packet-ssl-utils.c, look for gcry_md_open(), it is protected by "#ifdef HAVE_LIBGNUTLS", not HAVE_LIBGCRYPT.. Just trying building with with USE="ssl -gcrypt", and you'll see it doesn't build.
Comment 3 Peter Volkov (RETIRED) gentoo-dev 2011-12-12 06:47:04 UTC 
Olivier, please, test wireshark-1.6.4. Actually having USE="ssl -gcrypt" is my default setup and so far I had no problems to build wireshark. Finally, please, ATTACH build.log.