Summary: | net-im/pidgin-2.10.4[gnutls] fails configure with net-libs/gnutls[nettle] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Tsoy <alexander> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | b.brachaczek, net-im |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 361315 | ||
Attachments: |
build.log
config.log pidgin-2.10.4.ebuild.patch pidgin-2.10.4-configure.patch pidgin-2.10.4.ebuild.patch |
Description
Alexander Tsoy
2012-06-27 09:59:27 UTC
Created attachment 316395 [details]
build.log
Created attachment 316397 [details]
config.log
Created attachment 316399 [details, diff]
pidgin-2.10.4.ebuild.patch
Unfortunately that's not the right solution. The problem is that in the case of gnutls[nettle] it shouldn't use gcrypt at all. Created attachment 316415 [details, diff]
pidgin-2.10.4-configure.patch
Created attachment 316417 [details, diff]
pidgin-2.10.4.ebuild.patch
(In reply to comment #5) > Created attachment 316415 [details, diff] [details, diff] > pidgin-2.10.4-configure.patch Oh.. I didn't test it with net-libs/gnutls[-nettle] and it may fail. (In reply to comment #7) > Oh.. I didn't test it with net-libs/gnutls[-nettle] and it may fail. It won't fail. Pidgin doesn't use libgcrypt, `pkg-config --libs gnutls` with stable net-libs/gnutls[-nettle] doesn't mention -lgcrypt, so simply removing -lgcrypt is correct. I filed an upstream report for this: https://developer.pidgin.im/ticket/15329 Hi, I can confirm that pidgin 2.10.6 without gtk && with ncurses (in order to get finch only) is not able to build. After negating 'nettle' flag on gnutls it builds fine. System is a recently installed gentoo 2012. Here's an emerge --info: http://bpaste.net/show/56253/ Regards, Paul It's fixed in upstream Pidgin 2.10.7. As already mentioned this is fixed in 2.10.7. |