From: spdawson at gmail.com <spdawson@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libfreefare: add missing openssl dependency
Date: Sun, 17 Jun 2012 10:07:40 +0100 [thread overview]
Message-ID: <1339924060-4250-1-git-send-email-spdawson@gmail.com> (raw)
From: Simon Dawson <spdawson@gmail.com>
If openssl is not selected, configuration fails for the libfreefare package
as follows.
configure: error: Cannot find libcrypto.
This patch adds the missing dependency on openssl.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
---
package/libfreefare/Config.in | 4 ++++
package/libfreefare/libfreefare.mk | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/package/libfreefare/Config.in b/package/libfreefare/Config.in
index 2e11f7e..438bcbf 100644
--- a/package/libfreefare/Config.in
+++ b/package/libfreefare/Config.in
@@ -1,7 +1,11 @@
config BR2_PACKAGE_LIBFREEFARE
bool "libfreefare"
+ depends on BR2_PACKAGE_OPENSSL
select BR2_PACKAGE_LIBNFC
help
Library for high level manipulation of MIFARE cards.
http://code.google.com/p/nfc-tools/wiki/libfreefare
+
+comment "libfreefare requires openssl"
+ depends on !BR2_PACKAGE_OPENSSL
diff --git a/package/libfreefare/libfreefare.mk b/package/libfreefare/libfreefare.mk
index 0499999..16ef8fb 100644
--- a/package/libfreefare/libfreefare.mk
+++ b/package/libfreefare/libfreefare.mk
@@ -5,6 +5,6 @@
#############################################################
LIBFREEFARE_VERSION = 0.3.2
LIBFREEFARE_SITE = http://nfc-tools.googlecode.com/files
-LIBFREEFARE_DEPENDENCIES = libnfc
+LIBFREEFARE_DEPENDENCIES = libnfc openssl
$(eval $(call AUTOTARGETS))
--
1.7.9.5
next reply other threads:[~2012-06-17 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 9:07 spdawson at gmail.com [this message]
2012-06-17 10:20 ` [Buildroot] [PATCH] libfreefare: add missing openssl dependency Peter Korsgaard
2012-06-17 10:30 ` Baruch Siach
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=1339924060-4250-1-git-send-email-spdawson@gmail.com \
--to=spdawson@gmail.com \
--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