From: Saul Wold <sgw@linux.intel.com>
To: Konrad Scherer <konrad.scherer@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] cracklib: cracklib-native should not depend on zlib
Date: Thu, 24 Oct 2013 14:56:21 -0700 [thread overview]
Message-ID: <52699785.6030504@linux.intel.com> (raw)
In-Reply-To: <1382627820-3165-2-git-send-email-konrad.scherer@windriver.com>
On 10/24/2013 08:17 AM, Konrad Scherer wrote:
> From: Konrad Scherer <Konrad.Scherer@windriver.com>
>
> Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com>
> ---
> meta/recipes-extended/cracklib/cracklib_2.9.0.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-extended/cracklib/cracklib_2.9.0.bb b/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
> index 34c2ff1..bbf88bb 100644
> --- a/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
> +++ b/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
> @@ -5,7 +5,7 @@ LICENSE = "LGPLv2.1+"
> LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06"
>
> DEPENDS = "cracklib-native zlib"
> -DEPENDS_class-native = "zlib"
> +DEPENDS_class-native = "zlib-native"
>
This is actually needed since cracklib has a configure test for zlib.h,
with no way to disable it. So without the zlib-native the build will be
non-determinstic, since depending on the existance of zlib.h configure
output will be different.
Thanks
Sau!
> EXTRA_OECONF = "--without-python --libdir=${base_libdir}"
>
>
next prev parent reply other threads:[~2013-10-24 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 15:16 [Patch 0/1] cracklib: cracklib-native should not depend on zlib Konrad Scherer
2013-10-24 15:17 ` [PATCH] " Konrad Scherer
2013-10-24 21:56 ` Saul Wold [this message]
2013-10-24 22:03 ` Saul Wold
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=52699785.6030504@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=konrad.scherer@windriver.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