On 19 March 2017 at 17:23, Chris Staub <[email protected]> wrote: > On 03/19/2017 11:37 AM, Richard Melville wrote: > >> On 17 March 2017 at 19:55, Richard Melville <[email protected] <mailto: >> [email protected]>> wrote: >> >> On 17 March 2017 at 19:04, Chris Staub <[email protected] >> <mailto:[email protected]>> wrote: >> >> GnuPG recognizes GnuTLS for me... >> >> TLS support: gnutls >> >> Maybe config.log gives a hint of why it's not being found for you. >> >> >> Thanks Chris -- I won't be able to check this out until after the >> weekend now. >> >> >> OK, I returned earlier than expected. I've checked the GnuPG build and >> it seems that libidn2 hadn't created a pkgconfig file. I've manually >> created one, and now GnuPG builds with GnuTLS support, but questions >> remain:- >> >> 1. What could have stopped the libidn2 build from creating a .pc file? I >> seem to remember having this issue a few years ago, but I can't remember >> which package was affected. >> >> 2. Libidn2 appears to be a dependency of GnuTLS. The book wrongly shows >> libidn as an optional dependency. Instead, libidn2 needs to be in the >> required dependency list, particularly if GnuTLS support is required in a >> future GnuPG build. >> >> 3. Shouldn't libidn2 have a page of its own in the book, like NASM and >> Yasm? >> > > Neither libidn nor libidn2 is required for GnuTLS - I don't have either, > and GnuTLS installs fine, and GnuPG still finds GnuTLS.
Interesting. I had libidn2 already installed (but not libidn), and GnuTLS was built following on from that. When the GnuPG configure script couldn't find libidn2 owing to a missing .pc file, the error message was that libidn2 was needed for GnuTLS and therefore GnuTLS support would not be built. So I'm not sure what is going on. In any event it looks like a poor GnuPG configure script. Richard
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
