Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Dan McGregor <danismostlikely@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gzip: Avoid host contamination during build
Date: Thu, 29 May 2014 00:09:28 +0100	[thread overview]
Message-ID: <1401318568.2607.69.camel@ted> (raw)
In-Reply-To: <CACS+7ZSGKFG06F_jFOJZu7FJqLh2F+FgkW30PSMRQ8Xdio51Qw@mail.gmail.com>

On Tue, 2014-05-27 at 17:38 -0600, Dan McGregor wrote:
> From: Dan McGregor <dan.mcgregor@usask.ca>
> 
> On systems with /bin and /usr/bin merged the gzip recipe may find grep
> in /usr/bin, while OE puts it in /bin. Force the recipe to find grep in
> the correct place.
> 
> Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
> ---
>  meta/recipes-extended/gzip/gzip.inc | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta/recipes-extended/gzip/gzip.inc
> b/meta/recipes-extended/gzip/gzip.inc
> index 920b256..57873cb 100644
> --- a/meta/recipes-extended/gzip/gzip.inc
> +++ b/meta/recipes-extended/gzip/gzip.inc
> @@ -12,6 +12,8 @@ SRC_URI = "${GNU_MIRROR}/gzip/${BP}.tar.gz"
> 
>  inherit autotools texinfo
> 
> +EXTRA_OEMAKE = "GREP=${base_bindir}/grep"
> +
>  do_install_append () {
>   # Rename and move files into /bin (FHS), which is typical place for gzip
>   install -d ${D}${base_bindir}

My worry is what happens to gzip-native. Do we have to encode a path?

Cheers,

Richard



  parent reply	other threads:[~2014-05-28 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 23:38 [PATCH] gzip: Avoid host contamination during build Dan McGregor
2014-05-28 20:29 ` Khem Raj
2014-05-28 21:23   ` Dan McGregor
2014-05-28 23:09 ` Richard Purdie [this message]
2014-05-29 17:41   ` Dan McGregor

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=1401318568.2607.69.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=danismostlikely@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