From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] insane bbclass: turn fatal errors back into fatal errors
Date: Fri, 1 Jul 2011 12:25:19 -0500 [thread overview]
Message-ID: <4E0E02FF.4040304@windriver.com> (raw)
In-Reply-To: <4E0E00FA.1060508@gmail.com>
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?
--Mark
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-07-01 17:29 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 [this message]
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=4E0E02FF.4040304@windriver.com \
--to=mark.hatle@windriver.com \
--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 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.