From: Martin Hicks <mort@bork.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cryptsetup: select e2fsprogs for libuuid dependency
Date: Tue, 1 Feb 2011 13:44:17 -0500 [thread overview]
Message-ID: <1296585857-5491-1-git-send-email-mort@bork.org> (raw)
In-Reply-To: <=> run ramboot>
Signed-off-by: Martin Hicks <mort@bork.org>
---
package/cryptsetup/Config.in | 1 +
package/cryptsetup/cryptsetup.mk | 1 -
2 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/package/cryptsetup/Config.in b/package/cryptsetup/Config.in
index 23c4afa..8b543cd 100644
--- a/package/cryptsetup/Config.in
+++ b/package/cryptsetup/Config.in
@@ -3,6 +3,7 @@ config BR2_PACKAGE_CRYPTSETUP
select BR2_PACKAGE_LIBGCRYPT
select BR2_PACKAGE_POPT
select BR2_PACKAGE_LVM2
+ select BR2_PACKAGE_E2FSPROGS
help
This tool helps manipulate dm-crypt and luks partitions for on-disk
encryption.
diff --git a/package/cryptsetup/cryptsetup.mk b/package/cryptsetup/cryptsetup.mk
index 5b0310f..33869c7 100644
--- a/package/cryptsetup/cryptsetup.mk
+++ b/package/cryptsetup/cryptsetup.mk
@@ -6,7 +6,6 @@ CRYPTSETUP_SOURCE = cryptsetup-$(CRYPTSETUP_VERSION).tar.bz2
CRYPTSETUP_SITE = http://cryptsetup.googlecode.com/files
CRYPTSETUP_INSTALL_STAGING = NO
CRYPTSETUP_INSTALL_TARGET = YES
-#CRYPTSETUP_CONF_OPT = --BLAH
CRYPTSETUP_DEPENDENCIES = lvm2 libgcrypt popt e2fsprogs
$(eval $(call AUTOTARGETS,package,cryptsetup))
--
1.5.6.5
next parent reply other threads:[~2011-02-01 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <=>
2011-02-01 18:44 ` Martin Hicks [this message]
2011-02-01 21:03 ` [Buildroot] [PATCH] cryptsetup: select e2fsprogs for libuuid dependency Thomas Petazzoni
2011-02-07 14:09 ` [Buildroot] [PATCH] V2: Add cryptsetup package Martin Hicks
2011-02-07 14:16 ` [Buildroot] [PATCH] V3: " Martin Hicks
2011-02-07 17:38 ` Martin Hicks
2011-02-07 14:17 ` [Buildroot] [PATCH] V2: " Martin Hicks
2011-02-02 1:04 ` [Buildroot] [PATCH] cryptsetup: select e2fsprogs for libuuid dependency Mike Frysinger
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=1296585857-5491-1-git-send-email-mort@bork.org \
--to=mort@bork.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