From: Saul Wold <sgw@linux.intel.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Kernel QA build error
Date: Fri, 28 Jan 2011 10:23:05 -0800 [thread overview]
Message-ID: <4D430989.9050407@linux.intel.com> (raw)
In-Reply-To: <042CC4DD-1AF2-421C-8423-7251B294B935@keylevel.com>
On 01/28/2011 12:31 AM, Chris Tapp wrote:
> I'm getting a QA failure when running a build from a recent git master:
>
>> Checking autotools environment for common misconfiguration
>> NOTE: Checking autotools environment for common misconfiguration
>> linux: Recipe file does not have license file information
>> (LIC_FILES_CHKSUM)
>> ERROR: linux: Recipe file does not have license file information
>> (LIC_FILES_CHKSUM)
>> Licensing Error: LIC_FILES_CHKSUM does not match, please fix
>> ERROR: Licensing Error: LIC_FILES_CHKSUM does not match, please fix
>> Function 'do_qa_configure' failed
>> ERROR: Function 'do_qa_configure' failed
>
> This is when building kernel version 2.6.33.2-r2.
>
Chris,
This has been fixed in master, this is due to that recipe missing the
LIC_FILES_CHKSUM (as noted in the error message). I added the missing line:
+LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
Thanks for pointing this one out.
Sau!
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
prev parent reply other threads:[~2011-01-28 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 8:31 Kernel QA build error Chris Tapp
2011-01-28 18:23 ` Saul Wold [this message]
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=4D430989.9050407@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=opensource@keylevel.com \
--cc=yocto@yoctoproject.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.