All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Zheng <goodmenzy@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ecryptfs-utils: add linux-pam dependency if PAM has been enabled
Date: Wed, 27 Nov 2019 12:23:48 +0800	[thread overview]
Message-ID: <CAJPHfYOm0O9WSRv-u1huwqzeEKBsKEEpsqTjd3ugJ=NwiwwSUw@mail.gmail.com> (raw)
In-Reply-To: <20191127042053.GC1282@techyauld.com>

        If linux-pam has been selected, we want to build pam_ecryptfs.so
        and install it into /lib/security/

Signed-off-by: Yi Zheng <goodmenzy@gmail.com>
---
 package/ecryptfs-utils/ecryptfs-utils.mk | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/package/ecryptfs-utils/ecryptfs-utils.mk
b/package/ecryptfs-utils/ecryptfs-utils.mk
index eb3194b6d0..326ff4f2dd 100644
--- a/package/ecryptfs-utils/ecryptfs-utils.mk
+++ b/package/ecryptfs-utils/ecryptfs-utils.mk
@@ -11,13 +11,20 @@ ECRYPTFS_UTILS_LICENSE = GPL-2.0+
 ECRYPTFS_UTILS_LICENSE_FILES = COPYING

 ECRYPTFS_UTILS_DEPENDENCIES = keyutils libnss host-intltool
-ECRYPTFS_UTILS_CONF_OPTS = --disable-pywrap --disable-pam
+ECRYPTFS_UTILS_CONF_OPTS = --disable-pywrap

 #Needed for build system to find pk11func.h and libnss3.so
 ECRYPTFS_UTILS_CONF_ENV = \
        NSS_CFLAGS="-I$(STAGING_DIR)/usr/include/nss
-I$(STAGING_DIR)/usr/include/nspr" \
        NSS_LIBS="-lnss3"

+ifeq ($(BR2_PACKAGE_LINUX_PAM),y)
+ECRYPTFS_UTILS_CONF_OPTS += --enable-pam
+ECRYPTFS_UTILS_DEPENDENCIES += linux-pam
+else
+ECRYPTFS_UTILS_CONF_OPTS += --disable-pam
+endif
+
 ifeq ($(BR2_PACKAGE_OPENSSL),y)
 ECRYPTFS_UTILS_CONF_OPTS += --enable-openssl
 ECRYPTFS_UTILS_DEPENDENCIES += openssl
--
2.24.0

       reply	other threads:[~2019-11-27  4:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191127042053.GC1282@techyauld.com>
2019-11-27  4:23 ` Yi Zheng [this message]
2019-12-24 14:10   ` [Buildroot] [PATCH] ecryptfs-utils: add linux-pam dependency if PAM has been enabled Thomas Petazzoni

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='CAJPHfYOm0O9WSRv-u1huwqzeEKBsKEEpsqTjd3ugJ=NwiwwSUw@mail.gmail.com' \
    --to=goodmenzy@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 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.