From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] insane: make GNU_HASH check slightly more robust (avoids false negatives with gold); add check for useless rpaths
Date: Wed, 20 Jul 2011 15:48:53 +0100 [thread overview]
Message-ID: <1311173333.2344.51.camel@rex> (raw)
In-Reply-To: <1310728890.3805.1.camel@phil-desktop>
On Fri, 2011-07-15 at 12:21 +0100, Phil Blundell wrote:
> On Thu, 2011-07-14 at 21:26 +0200, Koen Kooi wrote:
> > The new rpath warning is nice, but a bit too terse:
>
> Yes, agreed. Try this patch and see if the situation improves.
>
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-07-20 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 9:02 [PATCH v2] insane: make GNU_HASH check slightly more robust (avoids false negatives with gold); add check for useless rpaths Phil Blundell
2011-07-14 14:07 ` Richard Purdie
2011-07-14 19:26 ` Koen Kooi
2011-07-15 11:21 ` Phil Blundell
2011-07-15 12:34 ` Koen Kooi
2011-07-20 14:48 ` Richard Purdie [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=1311173333.2344.51.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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