From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] insane bbclass: turn fatal errors back into fatal errors
Date: Fri, 01 Jul 2011 19:18:00 +0100 [thread overview]
Message-ID: <1309544280.20015.535.camel@rex> (raw)
In-Reply-To: <38420CC7-A216-4D03-B512-0D85BA9393B9@dominion.thruhere.net>
On Fri, 2011-07-01 at 19:33 +0200, Koen Kooi wrote:
> Op 1 jul 2011, om 19:25 heeft Mark Hatle het volgende geschreven:
>
> > On 7/1/11 12:16 PM, Khem Raj wrote:
> >> On 07/01/2011 10:12 AM, Richard Purdie wrote:
> >>> gcc-4.6.0+svnr175150, non dev contains .so, gcc, /work/i586-poky-linux/gcc-4.6.0+svnr175150-r4/packages-split/gcc/usr/libexec/gcc/i586-poky-linux/4.6.1/liblto_plugin.so
> >>>>
> >>
> >> This should be packages with gcc itself. May be adding to FILES will get
> >> rid of this warning
> >
> > The warning above indicates that it -is- being packaged in the 'gcc' package.
> > The check verified that no files of the name .so exit and they are not symlinks:
> >
> > if not name.endswith("-dev") and not name.endswith("-dbg") and
> > path.endswith(".so") and os.path.islink(path):
> >
> > In this case, I believe that the file is likely supposed to be there. Is there
> > a way to selectively disable insane checks on a per-recipe basis when we know
> > they are wrong?
>
> We only have the big INSANE_SKIP_gcc = True hammer
Although as I hint at in my insane.bbclass patch, I just made it much
easier to implement skipping specific checks. Its not there yet but
shouldn't be too difficult from where the code it at now...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-01 18:22 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
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 [this message]
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=1309544280.20015.535.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