From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wget: use GnuTLS instead of OpenSSL
Date: Fri, 04 Jul 2014 10:08:54 +0100 [thread overview]
Message-ID: <53B66F26.5000800@communistcode.co.uk> (raw)
In-Reply-To: <1402915976-12506-1-git-send-email-ross.burton@intel.com>
On 16/06/14 11:52, Ross Burton wrote:
> OpenSSL has license complications and GnuTLS is preferred, so although the
> license complications don't impact wget use GnuTLS for consistency.
>
> Also add a recommendation on ca-certificates so that https: URLs work.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
> meta/recipes-extended/wget/wget.inc | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-extended/wget/wget.inc b/meta/recipes-extended/wget/wget.inc
> index a778bca..642d502 100644
> --- a/meta/recipes-extended/wget/wget.inc
> +++ b/meta/recipes-extended/wget/wget.inc
> @@ -3,15 +3,16 @@ HOMEPAGE = "https://www.gnu.org/software/wget/"
> SECTION = "console/network"
> LICENSE = "GPLv3"
> LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
> -DEPENDS = "openssl zlib libpcre"
> +DEPENDS = "gnutls zlib libpcre"
>
> INC_PR = "r16"
>
> inherit autotools gettext texinfo update-alternatives
>
> -EXTRA_OECONF = "--enable-ipv6 --with-libssl-prefix=${STAGING_DIR_HOST} \
> - --with-ssl=openssl --disable-rpath --disable-iri \
> +EXTRA_OECONF = "--enable-ipv6 --with-ssl=gnutls --disable-rpath --disable-iri \
> ac_cv_header_uuid_uuid_h=no"
>
> ALTERNATIVE_${PN} = "wget"
> ALTERNATIVE_PRIORITY = "100"
> +
> +RRECOMMENDS_${PN} += "ca-certificates"
>
Ross,
I've just pulled this in today after being on holiday for a while and it
causes a breakage on my system.
| checking for libgnutls... no
| configure: error: --with-ssl=gnutls was given, but GNUTLS is not
available.
| Configure failed. The contents of all config.log files follows to aid
debugging
log: http://ix.io/dfO
I would have expected gnutls to have been pulled in through the depends
but it obviously hasn't, or the system hasn't managed to find it...
Any ideas?
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
next prev parent reply other threads:[~2014-07-04 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 10:52 [PATCH] wget: use GnuTLS instead of OpenSSL Ross Burton
2014-07-04 9:08 ` Jack Mitchell [this message]
2014-07-17 11:06 ` Jack Mitchell
2014-07-17 11:33 ` Richard Purdie
2014-07-17 11:39 ` Jack Mitchell
2014-07-17 11:44 ` Jack Mitchell
2014-07-17 11:46 ` Jack Mitchell
2014-07-17 12:39 ` Richard Purdie
2014-07-17 12:48 ` Richard Purdie
2014-07-25 16:40 ` Khem Raj
2014-07-25 16:59 ` Richard Purdie
2014-07-25 10:42 ` Koen Kooi
2014-07-25 16:22 ` Khem Raj
2014-07-25 16:27 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B66F26.5000800@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox