[bitbake-devel] PREFERRED_VERSION with % wildcard picking unexpected version

[Khem Raj]

> On Dec 9, 2015, at 3:27 PM, Nicolas Dechesne <nicolas.dechesne at linaro.org> wrote:
> 
> On Tue, Dec 1, 2015 at 6:13 AM, Andre McCurdy <armccurdy at gmail.com> wrote:
>> I have two recipes within a single layer:
>> 
>>  stblinux_3.14-1.7.bb
>>  stblinux_3.14-1.8.bb
>> 
>> If PREFERRED_VERSION_stblinux is set to "3.14%", then I would expect
>> the version 3.14-1.8 recipe to be selected, however 3.14-1.7 gets
>> selected instead.
>> 
>> Reversing the order of files stored in pkg_pn[pn] seems to help. Is it
>> a reasonable solution?
> 
> 
> I have a somewhat similar issue..
> 
> in oe-core we have GCCVERSION set to 5.%, if I add meta-linaro layer
> which has gcc_5.1.bb (while OE has gcc_5.2.bb), I am seeing this:
> 
> $ bitbake -e gcc | grep ^PV
> PV="5.1.0"
> 
> While I would expect 5.2.0 to be picked up.
> 
> This patch does not fix this issue, btw.
> 
> If I remove gcc_5.1.bb from my layers, then I can see:
> 
> $ bitbake -e gcc | grep ^PV
> PV=“5.2.0"

whats the order of your layer in bitbake search path. Secondly whats the LAYER_PRIORITY
if they are higher than oe-core then it will always choose the provider from the higher order layer
versions don’t matter.

> --
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20151209/83f26391/attachment-0002.sig>