On 17 March 2017 at 19:55, Richard Melville <[email protected]> wrote:
> On 17 March 2017 at 19:04, Chris Staub <[email protected]> wrote: > >> On 03/17/2017 02:41 PM, Richard Melville wrote: >> >>> I'm getting:- >>> >>> checking for LIBGNUTLS... no >>> >>> when running the configure script. The configure summary includes:- >>> >>> TLS support: no >>> >>> I have GnuTLS installed, and it's not a script issue this time. Does >>> anybody know why this is happening? >>> >>> Richard >>> >>> >>> >> 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? 4. GnuTLS needs to be shown as an optional dependency of GnuPG. I have already mentioned this in an earlier post (titled GnuPG-2.1.18). Richard
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
