From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Make GNU_HASH failures fatal
Date: Mon, 14 Mar 2011 20:51:20 +0000 [thread overview]
Message-ID: <1300135880.30423.571.camel@rex> (raw)
In-Reply-To: <4D7E44D4.2020701@mentor.com>
On Mon, 2011-03-14 at 09:39 -0700, Tom Rini wrote:
> On 03/14/2011 08:35 AM, Koen Kooi wrote:
> > Hi,
> >
> > GNU_HASH QA failures are nearly gone in .dev, but still rampant in
> > oe-core. I would like to propose making them fatal so they get fixed.
> > The most worrysome offenders currently are gcc-runtime and perl.
>
> It's a little worse than that actually. Nothing is fatal currently. I
> think we should grab warning/error
> bit I did in oe.dev and pull that in (and then talk about adding RPATH
> to the fatal list).
I think there are "fatal" warnings in OECore in that the QA errors
trigger non-zero exit codes. Warnings don't do that and GNU_HASH is a
warning, RPATH is an error from what I remember...
Cheers,
Richard
next prev parent reply other threads:[~2011-03-14 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 15:35 [RFC] Make GNU_HASH failures fatal Koen Kooi
2011-03-14 16:39 ` Tom Rini
2011-03-14 20:51 ` Richard Purdie [this message]
2011-03-14 17:54 ` Khem Raj
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=1300135880.30423.571.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