From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] cups: fix host contamination issue
Date: Mon, 04 Aug 2014 10:46:53 +0100 [thread overview]
Message-ID: <1407145613.6981.48.camel@ted> (raw)
In-Reply-To: <1406891040-8738-1-git-send-email-koen@dominion.thruhere.net>
On Fri, 2014-08-01 at 13:04 +0200, Koen Kooi wrote:
> -I/usr/include would end up in CFLAGS if /usr/bin/gcrypt-config is
> present on the host systemd.
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> ...crypt-config-from-the-host-it-leads-to-SS.patch | 28 ++++++++++++++++++++++
> meta/recipes-extended/cups/cups_1.7.4.bb | 1 +
> 2 files changed, 29 insertions(+)
> create mode 100644 meta/recipes-extended/cups/cups/0001-don-t-use-gcrypt-config-from-the-host-it-leads-to-SS.patch
Does the patch "cups: regen configure so cups-no-gcrypt.patch has an
effect" obsolete the need for this change?
Cheers,
Richard
next prev parent reply other threads:[~2014-08-04 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 11:04 [PATCH] cups: fix host contamination issue Koen Kooi
2014-08-04 9:46 ` Richard Purdie [this message]
2014-08-04 11:06 ` Koen Kooi
2014-08-04 13:18 ` Peter A. Bigot
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=1407145613.6981.48.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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