[OE-core] WARNING: The license listed CLOSED was not in the licenses collected for foo
Mike Looijmans
mike.looijmans at topic.nl
Mon May 11 09:39:18 UTC 2015
On 11-05-15 11:36, Paul Eggleton wrote:
> At a guess, maybe do_populate_lic didn't re-execute for this recipe. Does it
> still happen if you bitbake -c cleansstate the recipe and try again?
Yes, it even complains about this on a completely fresh build.
>
> Cheers,
> Paul
>
> On Monday 11 May 2015 10:58:07 Mike Looijmans wrote:
>> Hmm, I cannot figure it out... I have in a recipe:
>>
>> LICENSE = "internal"
>> LIC_FILES_CHKSUM = "file://LICENSE;md5=cf85de037de7ae12cc2d0059741fdbae"
>>
>> Then in my layer.conf:
>>
>> LICENSE_PATH += "${LAYERDIR}/licenses"
>>
>> I have a file called "internal" in that path. Still, I get:
>>
>> WARNING: log_check: WARNING: The license listed internal was not in the
>> licenses collected for ...
>>
>> What am I missing still then? What does the warning mean? I thought I got
>> everything right, but either the licensing rules have changed or I never got
>> it right in the first place and a check was added to make me aware of that.
>> On 11-05-15 08:54, Mike Looijmans wrote:
>>> What is one expected to do when one justs wants to add the missing license
>>> to the "licenses collected for ..."?
>>>
>>> I'm a bit spoiled now, most OE messages explain what it expects me to do
>>> to
>>> fix the problem.
>>
>> Kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>> TOPIC Embedded Products
>> Eindhovenseweg 32-C, NL-5683 KH Best
>> Postbus 440, NL-5680 AK Best
>> Telefoon: +31 (0) 499 33 69 79
>> Telefax: +31 (0) 499 33 69 70
>> E-mail: mike.looijmans at topicproducts.com
>> Website: www.topicproducts.com
>>
>> Please consider the environment before printing this e-mail
>
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans at topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
More information about the Openembedded-core
mailing list