From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] problem with blacklisted packages
Date: Wed, 6 Jul 2016 17:23:13 +0200 [thread overview]
Message-ID: <577D2261.1040400@mlbassoc.com> (raw)
In-Reply-To: <577D1D64.8080604@elfin.de>
On 2016-07-06 17:01, piotr.lewicki wrote:
> Hi,
> I'm having problem with some of the recipes which are blacklisted due to problems with compilation using GCC-6.
>
> I wonder if there is a way to "whitelist" those packages without changing content of original recipe?
>
> For now I have:
>
> GCCVERSION = "5.%"
>
> in my distro.conf so if a recipe is not building due to problems with gcc6 I simply edit the recipe and remove the line
> with PNBLACKLIST.
>
> Is there a better way to deal with those problems?
> Can this blacklisting depend on "GCCVERSION" ?
>
> Example of problematic recipe : crda (from crda_3.18.bb)
>
I asked this same question last week :-) I agree that not everyone
is using the leading edge compilers and making those of us have to
take such pains is a bit unfair.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-07-06 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 8:05 [krogoth][wic][PATCH] wic: rawcopy: make source filenames unique Ed Bartosh
2016-07-06 12:38 ` Fabio Berton
2016-07-06 15:01 ` [OE-core] problem with blacklisted packages piotr.lewicki
2016-07-06 15:23 ` Gary Thomas [this message]
2016-07-06 15:35 ` Davis, Michael
2016-07-07 8:50 ` piotr.lewicki
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=577D2261.1040400@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@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.