From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] curl: make CURL_FEATURES configurable again
Date: Thu, 28 Oct 2010 17:09:37 -0400 [thread overview]
Message-ID: <4CC9E691.9000809@cbnco.com> (raw)
In-Reply-To: <AANLkTikbv9bF9fBvFU2_C6sK13A23wBXgRzwbX++VLhq@mail.gmail.com>
Khem Raj wrote:
> On Thu, Oct 28, 2010 at 11:49 AM, Michael Smith <msmith@cbnco.com> wrote:
>> It seems to do the right thing here - CURL_FEATURES_virtclass-native is
>> not weak, so in my curl-native config.log, I see --disable-gnutls.
>
> certainly nor for me. here is what I get
Maybe because I have a setting for CURL_FEATURES in my conf? If so, that
sounds like odd bitbake behaviour. :(
Do you have any thoughts on how to solve it? There is not much point to
having CURL_FEATURES as a variable if it's not configurable. I can just
hack over it in an amend.inc, but the recipe as it stands is broken.
>> (btw: why do we not want gnutls in curl-native?)
>
> thats a different question does not solve the problem at hand.
Yes, it's a different question. I didn't realize I was limited to one
per e-mail. :)
Mike
next prev parent reply other threads:[~2010-10-28 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 17:22 [PATCH] curl: make CURL_FEATURES configurable again Michael Smith
2010-10-28 18:30 ` Khem Raj
2010-10-28 18:49 ` Michael Smith
2010-10-28 20:53 ` Khem Raj
2010-10-28 21:09 ` Michael Smith [this message]
2010-10-28 22:34 ` Khem Raj
2010-10-29 15:01 ` Michael Smith
2010-10-30 10:15 ` Denys Dmytriyenko
2010-11-02 13:49 ` Michael Smith
2010-10-29 15:02 ` [PATCH v2] curl: remove anon python block Michael Smith
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=4CC9E691.9000809@cbnco.com \
--to=msmith@cbnco.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.