From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libfreefare: add missing openssl dependency
Date: Sun, 17 Jun 2012 13:30:35 +0300 [thread overview]
Message-ID: <20120617103034.GA5839@tarshish> (raw)
In-Reply-To: <87wr36fdf0.fsf@macbook.be.48ers.dk>
Hi Peter,
On Sun, Jun 17, 2012 at 12:20:03PM +0200, Peter Korsgaard wrote:
> >>>>> "spdawson" == spdawson <spdawson@gmail.com> writes:
>
> spdawson> From: Simon Dawson <spdawson@gmail.com>
> spdawson> If openssl is not selected, configuration fails for the libfreefare package
> spdawson> as follows.
>
> spdawson> configure: error: Cannot find libcrypto.
>
> spdawson> This patch adds the missing dependency on openssl.
>
> spdawson> Signed-off-by: Simon Dawson <spdawson@gmail.com>
> spdawson> ---
> spdawson> package/libfreefare/Config.in | 4 ++++
> spdawson> package/libfreefare/libfreefare.mk | 2 +-
> spdawson> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> spdawson> diff --git a/package/libfreefare/Config.in b/package/libfreefare/Config.in
> spdawson> index 2e11f7e..438bcbf 100644
> spdawson> --- a/package/libfreefare/Config.in
> spdawson> +++ b/package/libfreefare/Config.in
> spdawson> @@ -1,7 +1,11 @@
> spdawson> config BR2_PACKAGE_LIBFREEFARE
> spdawson> bool "libfreefare"
> spdawson> + depends on BR2_PACKAGE_OPENSSL
>
> We normally use 'depends on' for library dependencies (like libnfc), so
> I've changed that and committed, thanks.
s/depends on/select/
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-06-17 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 9:07 [Buildroot] [PATCH] libfreefare: add missing openssl dependency spdawson at gmail.com
2012-06-17 10:20 ` Peter Korsgaard
2012-06-17 10:30 ` Baruch Siach [this message]
2012-06-17 12:10 ` Peter Korsgaard
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=20120617103034.GA5839@tarshish \
--to=baruch@tkos.co.il \
--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