From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] curl: enable ssl support
Date: Mon, 11 Jun 2012 07:50:54 -0700 [thread overview]
Message-ID: <4FD605CE.6060203@linux.intel.com> (raw)
In-Reply-To: <0DCEDF44-AD19-4718-92F2-4801F8268190@dominion.thruhere.net>
On 06/08/2012 12:39 AM, Koen Kooi wrote:
>
> Op 8 jun. 2012, om 02:59 heeft Saul Wold het volgende geschreven:
>
>> This patch enables ssl support for curl to allow git to clone from
>> https / ssl sites.
>>
>> [YOCTO #2532]
>>
>> Signed-off-by: Saul Wold<sgw@linux.intel.com>
>> ---
>> meta/recipes-support/curl/curl_7.24.0.bb | 6 +++---
>> 1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta/recipes-support/curl/curl_7.24.0.bb b/meta/recipes-support/curl/curl_7.24.0.bb
>> index 12e95c9..f0ae7f1 100644
>> --- a/meta/recipes-support/curl/curl_7.24.0.bb
>> +++ b/meta/recipes-support/curl/curl_7.24.0.bb
>> @@ -5,10 +5,10 @@ SECTION = "console/network"
>> LICENSE = "MIT"
>> LIC_FILES_CHKSUM = "file://COPYING;beginline=7;md5=3a34942f4ae3fbf1a303160714e664ac"
>>
>> -DEPENDS = "zlib gnutls"
>> +DEPENDS = "zlib gnutls openssl"
>> DEPENDS_virtclass-native = "zlib-native"
>> DEPENDS_virtclass-nativesdk = "zlib-nativesdk"
>> -PR = "r0"
>> +PR = "r1"
>>
>> SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \
>> file://noldlibpath.patch \
>> @@ -20,7 +20,7 @@ SRC_URI[sha256sum] = "ebdb111088ff8b0e05b1d1b075e9f1608285e8105cc51e21caacf33d01
>> inherit autotools pkgconfig binconfig
>>
>> EXTRA_OECONF = "--with-zlib=${STAGING_LIBDIR}/../ \
>> - --without-ssl \
>> + --with-ssl \
>> --without-libssh2 \
>> --with-random=/dev/urandom \
>> --without-libidn \
>
> I haven't looked at the complete recipe, but what is the ssl behaviour for the -native and -nativesdk versions?
>
Actually it's the -native that needs the ssl behavior, and this adds it
for all 3 correctly, tested on target as well as -native (I did not
actually test the -nativesdk, but I will now).
Sau!
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-06-11 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 0:59 [PATCH] curl: enable ssl support Saul Wold
2012-06-08 7:39 ` Koen Kooi
2012-06-11 14:50 ` Saul Wold [this message]
2012-06-11 15:19 ` Koen Kooi
2012-06-11 22:13 ` Saul Wold
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=4FD605CE.6060203@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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