* [RFC] Make GNU_HASH failures fatal
@ 2011-03-14 15:35 Koen Kooi
2011-03-14 16:39 ` Tom Rini
2011-03-14 17:54 ` Khem Raj
0 siblings, 2 replies; 4+ messages in thread
From: Koen Kooi @ 2011-03-14 15:35 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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.
regards,
Koen
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [RFC] Make GNU_HASH failures fatal
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
2011-03-14 17:54 ` Khem Raj
1 sibling, 1 reply; 4+ messages in thread
From: Tom Rini @ 2011-03-14 16:39 UTC (permalink / raw)
To: openembedded-core
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).
--
Tom Rini
Mentor Graphics Corporation
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [RFC] Make GNU_HASH failures fatal
2011-03-14 16:39 ` Tom Rini
@ 2011-03-14 20:51 ` Richard Purdie
0 siblings, 0 replies; 4+ messages in thread
From: Richard Purdie @ 2011-03-14 20:51 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [RFC] Make GNU_HASH failures fatal
2011-03-14 15:35 [RFC] Make GNU_HASH failures fatal Koen Kooi
2011-03-14 16:39 ` Tom Rini
@ 2011-03-14 17:54 ` Khem Raj
1 sibling, 0 replies; 4+ messages in thread
From: Khem Raj @ 2011-03-14 17:54 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Koen Kooi
On Mon, Mar 14, 2011 at 8:35 AM, Koen Kooi <koen@dominion.thruhere.net> 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.
>
Yes I would say we fix the existing ones and then make it fatal.
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-03-14 20:53 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2011-03-14 17:54 ` Khem Raj
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.