From: Jezz <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [[PATCH v2]] strongswan: new package
Date: Tue, 12 Feb 2013 18:59:02 +0100 [thread overview]
Message-ID: <1696554.VhhAAgJSGv@sagittae> (raw)
In-Reply-To: <20130212122551.46e895b6@skate>
On Tuesday 12 February 2013 12:25:51 Thomas Petazzoni wrote:
> Dear J?r?me Pouiller,
>
> On Tue, 12 Feb 2013 12:19:33 +0100, J?r?me Pouiller wrote:
> > +config BR2_PACKAGE_STRONGSWAN_OPENSSL
> > + bool "Enables OpenSSL based crypto backends"
> > + select OPENSSL
> > +
> > +config BR2_PACKAGE_STRONGSWAN_GCRYPT
> > + bool "Enables libgcrypt based crypto backends"
> > + select LIBGCRYPT
>
> "select OPENSSL" or "select LIBGCRYPT" definitely cannot work, we don't
> have such options in Buildroot.
Sure.
hmm... Config cannot warn me about stupid errors like this?
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2013-02-12 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 17:43 [Buildroot] [PATCH] strongswan: new package Jérôme Pouiller
2013-02-08 18:02 ` Thomas Petazzoni
2013-02-12 11:19 ` Jérôme Pouiller
2013-02-12 11:19 ` [Buildroot] [[PATCH v2]] " Jérôme Pouiller
2013-02-12 11:25 ` Thomas Petazzoni
2013-02-12 17:59 ` Jezz [this message]
2013-02-14 13:25 ` [Buildroot] [PATCH v3] " Jérôme Pouiller
2013-02-14 13:39 ` Thomas Petazzoni
2013-02-14 15:10 ` [Buildroot] [PATCH v4 1/2] " Jérôme Pouiller
2013-02-14 15:10 ` [Buildroot] [PATCH v4 2/2] strongswan: fix build without IPv6 support Jérôme Pouiller
2013-03-24 14:31 ` Gustavo Zacarias
2013-05-13 15:15 ` [Buildroot] [PATCH v5] strongswan: new package Jérôme Pouiller
2013-07-31 16:17 ` Thomas Petazzoni
2013-03-24 14:31 ` [Buildroot] [PATCH v4 1/2] " Gustavo Zacarias
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=1696554.VhhAAgJSGv@sagittae \
--to=jezz@sysmic.org \
--cc=buildroot@busybox.net \
/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