<p dir="ltr">On May 28, 2014 5:09 PM, "Richard Purdie" <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br>
><br>
> On Tue, 2014-05-27 at 17:38 -0600, Dan McGregor wrote:<br>
> > From: Dan McGregor <<a href="mailto:dan.mcgregor@usask.ca">dan.mcgregor@usask.ca</a>><br>
> ><br>
> > On systems with /bin and /usr/bin merged the gzip recipe may find grep<br>
> > in /usr/bin, while OE puts it in /bin. Force the recipe to find grep in<br>
> > the correct place.<br>
> ><br>
> > Signed-off-by: Dan McGregor <<a href="mailto:dan.mcgregor@usask.ca">dan.mcgregor@usask.ca</a>><br>
> > ---<br>
> > meta/recipes-extended/gzip/gzip.inc | 2 ++<br>
> > 1 file changed, 2 insertions(+)<br>
> ><br>
> > diff --git a/meta/recipes-extended/gzip/gzip.inc<br>
> > b/meta/recipes-extended/gzip/gzip.inc<br>
> > index 920b256..57873cb 100644<br>
> > --- a/meta/recipes-extended/gzip/gzip.inc<br>
> > +++ b/meta/recipes-extended/gzip/gzip.inc<br>
> > @@ -12,6 +12,8 @@ SRC_URI = "${GNU_MIRROR}/gzip/${BP}.tar.gz"<br>
> ><br>
> > inherit autotools texinfo<br>
> ><br>
> > +EXTRA_OEMAKE = "GREP=${base_bindir}/grep"<br>
> > +<br>
> > do_install_append () {<br>
> > # Rename and move files into /bin (FHS), which is typical place for gzip<br>
> > install -d ${D}${base_bindir}<br>
><br>
> My worry is what happens to gzip-native. Do we have to encode a path?<br>
><br>
> Cheers,<br>
><br>
> Richard<br>
><br>
gzip native does encode a path, but what it encodes should probably be what gets automatically configured. Would making the EXTRA_OEMAKE variable be EXTRA_OEMAKE_class-target then?</p>