All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Davis, Michael" <michael.davis@essvote.com>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] problem with blacklisted packages
Date: Wed, 6 Jul 2016 15:35:47 +0000	[thread overview]
Message-ID: <2476892.ILE9ZpP5Yr@localhost.localdomain> (raw)
In-Reply-To: <577D1D64.8080604@elfin.de>

You can override the blacklist to off.  That is what I have been doing.
Put the following in your local.conf or distro conf file.
PNBLACKLIST[crda] = ""

On Wednesday, July 06, 2016 05:01:56 PM 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)
> 
> 
> 
> Thanks,
> Piotr Lewicki
> 

  parent reply	other threads:[~2016-07-06 15:35 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
2016-07-06 15:35   ` Davis, Michael [this message]
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=2476892.ILE9ZpP5Yr@localhost.localdomain \
    --to=michael.davis@essvote.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.