net-libs/gnutls-3.6.5 fails to build since the configure phase fails. Reproducible: Always Steps to Reproduce: 1. emerge net-libs/gnutls-3.6.5 Actual Results: configure run fails with: checking for NETTLE... no configure: error: *** *** Libnettle 3.4 was not found. Expected Results: a clean build Even though configure fails, nettle is present: qlist -vI nettle dev-libs/nettle-3.4 Seems to be some sort of detection error.
From config.log: configure:10044: checking for NETTLE configure:10051: $PKG_CONFIG --exists --print-errors "nettle >= 3.4.1" Requested 'nettle >= 3.4.1' but version of Nettle is 3.4 You may find new versions of Nettle at http://www.lysator.liu.se/~nisse/nettle configure:10054: $? = 1 configure:10068: $PKG_CONFIG --exists --print-errors "nettle >= 3.4.1" Requested 'nettle >= 3.4.1' but version of Nettle is 3.4 You may find new versions of Nettle at http://www.lysator.liu.se/~nisse/nettle configure:10071: $? = 1 configure:10085: result: no Requested 'nettle >= 3.4.1' but version of Nettle is 3.4 You may find new versions of Nettle at http://www.lysator.liu.se/~nisse/nettle So, the configure script should actually print 3.4.1, then it would indeed make sense, and the dep should be updated accordingly in the ebuild.
I do not know what happens at your side, the ebuild depends on nettle-3.4.1[1] Can you please make sure you have latest portage? [1] https://github.com/gentoo/gentoo/blob/master/net-libs/gnutls/gnutls-3.6.5.ebuild#L24
(In reply to Alon Bar-Lev from comment #2) > I do not know what happens at your side, the ebuild depends on > nettle-3.4.1[1] > > Can you please make sure you have latest portage? > > [1] > https://github.com/gentoo/gentoo/blob/master/net-libs/gnutls/gnutls-3.6.5. > ebuild#L24 Thanks for your feedback. Indeed nettle-3.4.1 seems to be in RDEPEND. Unfortunately gnutls was in @preserved-rebuild, so I decided to emerge net-libs/gnutls which in turn tried to emerge 3.6.5 (the version in preserved was gone from portage) As this failed I decided to manually merge v3.5.19-r1 (oneshotted). Of course gnutls is now gone from @preserved-rebuild, reproduction is thus impossible. and a wrold update isn'T even trying to upgrade to 3.6.5.
How did you reach this state? have you added any unstable keywords to gnutls? How did you get any of the non stable versions?
(In reply to Alon Bar-Lev from comment #4) > How did you reach this state? have you added any unstable keywords to > gnutls? How did you get any of the non stable versions? I got ~arch in ACCEPT_KEYWORDS ... The whole mess actually started with openssl and different packages pulling in different versions (of openssl) in the same slot ... I started upgrading openssl and rebuilding packages against it, maybe that was the first step into 'darkness'.
OK, I am closing this for now. The settings were correct from first package import, I can only guess that you have done something manually to make portage confused.
I wanted to suggest the same (closing) When I now emerge --oneshot -pv net-libs/gnutls the nettle dep is correctly pulled in and listed. Thanks for your help, patience and feedback.
