<p dir="ltr"><br>
On Jun 22, 2016 2:59 PM, "Joe Slater" <<a href="mailto:jslater@windriver.com">jslater@windriver.com</a>> wrote:<br>
><br>
> We have encountered some issues with the use of PNBLACKLIST in recipes.<br>
> In particular, PNBLACKLIST[pkg] will not suppress building of lib32-pkg<br>
> or lib64-pkg so world builds can fail unexpectedly.<br>
><br>
> One solution could be to implement BPNBLACKLIST[] which checks BPN instead<br>
> of PN when a recipe is being parsed. I have included a patch to do this.<br>
><br>
> If this were adopted, there are many recipes under meta-openembedded that<br>
> should probably changed to use BPNBLACKLIST instead of PNBLACKLIST.</p>
<p dir="ltr">Bpn will also mean native and nativesdk among others. I think its better to list multilibs explicitly.</p>
<p dir="ltr">><br>
> Joe Slater (1):<br>
> blacklist: add BPNBLACKLIST support<br>
><br>
> meta/classes/blacklist.bbclass | 24 ++++++++++++++++++++----<br>
> 1 file changed, 20 insertions(+), 4 deletions(-)<br>
><br>
> --<br>
> 1.7.9.5<br>
><br>
> --<br>
> _______________________________________________<br>
> Openembedded-core mailing list<br>
> <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a></p>