Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "David Nyström" <david.c.nystrom@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv2] libpam: Avoid host contamination issue w. libprelude
Date: Mon, 23 Sep 2013 18:34:01 +0200	[thread overview]
Message-ID: <1379954041-5575-3-git-send-email-david.nystrom@enea.com> (raw)
In-Reply-To: <1379954041-5575-1-git-send-email-david.nystrom@enea.com>

Since we dont use prelude in OE, we just disable autodetection of
prelude in the libpam configuration.

Seems like an old bug: 
http://lists.openembedded.org/pipermail/openembedded-devel/2012-March/083804.html

Signed-off-by: David Nyström <david.nystrom@enea.com>
---
 meta/recipes-extended/pam/libpam_1.1.6.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/pam/libpam_1.1.6.bb b/meta/recipes-extended/pam/libpam_1.1.6.bb
index f7493c5..c9bdcb0 100644
--- a/meta/recipes-extended/pam/libpam_1.1.6.bb
+++ b/meta/recipes-extended/pam/libpam_1.1.6.bb
@@ -37,7 +37,8 @@ EXTRA_OECONF = "--with-db-uniquename=_pam \
                 --includedir=${includedir}/security \
                 --libdir=${base_libdir} \
                 --disable-nis \
-                --disable-regenerate-docu"
+                --disable-regenerate-docu \
+		--disable-prelude"
 
 CFLAGS_append = " -fPIC "
 
-- 
1.8.3.2



      parent reply	other threads:[~2013-09-23 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 16:33 [PATCHv3] makedevs: add nativesdk to BBCLASSEXTENDS David Nyström
2013-09-23 16:34 ` [PATCH] shadow: Create recipe nativesdk-shadow David Nyström
2013-09-23 18:01   ` Mark Hatle
2013-09-23 19:01     ` David Nystrom
2013-09-23 21:14       ` Richard Purdie
2013-09-24  8:25         ` Richard Purdie
2013-09-24 14:30           ` David Nyström
2013-09-25 10:03             ` Richard Purdie
2013-09-25 12:24               ` David Nyström
2013-09-23 16:34 ` David Nyström [this message]

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=1379954041-5575-3-git-send-email-david.nystrom@enea.com \
    --to=david.c.nystrom@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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