Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] insane bbclass: turn fatal errors back into fatal errors
Date: Thu, 30 Jun 2011 16:59:54 +0100	[thread overview]
Message-ID: <201106301659.54941.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4FC82E26-5A0C-48DF-99F5-7E2D9B8C7290@dominion.thruhere.net>

On Thursday 30 June 2011 16:49:57 Koen Kooi wrote:
> It's a white list, so:
> 
> # 0 - non dev contains .so
> # 5 - .la contains installed=yes or reference to the workdir
> # 7 - the desktop file is not valid
> # 8 - .la contains reference to the workdir
> # 9 - LDFLAGS ignored
> 
> Are warnings and
> 
> # 1 - package contains a dangerous RPATH
> # 2 - package depends on debug package
> # 3 - non dbg contains .so
> # 4 - wrong architecture
> # 6 - .pc contains reference to /usr/include or workdir
> # 10 - Build paths in binaries
> # 11 - package depends on devel package
> 
> Are fatal errors. The splits seems arbitrary to me, but it that's how it
> was last year before RP disabled all fatal errors.

OK, comprehension fail on my part, sorry. Good to have them listed out 
explicitly though, thanks for that. The fatal errors are definitely not good 
things to be allowing through if we can avoid it.

Without checking, do you have a handle on how many of these we would have to 
fix in OE-core to make it build without fatal errors?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-06-30 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 15:11 [PATCH] insane bbclass: turn fatal errors back into fatal errors Koen Kooi
2011-06-30 15:33 ` Paul Eggleton
2011-06-30 15:49   ` Koen Kooi
2011-06-30 15:59     ` Paul Eggleton [this message]
2011-07-01 16:25       ` Richard Purdie
2011-07-01 17:12         ` Richard Purdie
2011-07-01 17:16           ` Khem Raj
2011-07-01 17:25             ` Mark Hatle
2011-07-01 17:33               ` Koen Kooi
2011-07-01 18:18                 ` Richard Purdie
2011-07-04 14:10           ` Paul Eggleton
2011-07-05 10:38           ` Richard Purdie
2011-07-01 14:55     ` Phil Blundell
2011-07-01 15:09       ` Koen Kooi
2011-06-30 15:58 ` Tom Rini
2011-06-30 16:08   ` Mark Hatle
2011-06-30 20:35     ` Koen Kooi
2011-06-30 20:59       ` Scott Garman

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=201106301659.54941.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --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