All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Nikhil Kamath <Nikhil.Kamath@lnties.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Prashanth Shiva <Prashanth.Shiva@lnties.com>
Subject: Re: FW: problem in LIC_FILES_CHKSUM
Date: Wed, 01 Jun 2011 09:28:33 -0700	[thread overview]
Message-ID: <4DE668B1.6000305@linux.intel.com> (raw)
In-Reply-To: <4ED62A07621E9C41B8CB2F608655EF45FD4C@POCITMSEXMB01.LntUniverse.com>

On 06/01/2011 07:42 AM, Nikhil Kamath wrote:
> Hi,
>
> We are trying to build a linux kernel 2.6.35.3 for imx platform. We are
> facing a problem as attached in the mail.
>
>
> The following steps followed are as follows
>
> 1.Initially we have run the $bitbake poky-image-minimal for ‘qemuarm’
> machine. It got compiled.
>
> 2.Next I added a folder named ‘ linux-imx’ in
> ‘\poky-bernard-5.0\meta\recipes-kernel\linux’ to create a kernel image
> for imx platform.
>
> 3.The linux-imx folder contains mx35pdk folder, which inturn contains
> defconfig file for imx35pdk board.
>
> 4.The linux.inc & linux-imx_git.bb is added in linux folder
> ‘\poky-bernard-5.0\meta\recipes-kernel\linux’.
>
> 5.Added mx35pdk.conf file in ‘\poky-bernard-5.0\meta\conf\machine’.
>
> 6.Then I ran $bitbake linux-imx
>
> Please see the following attached image.
>
You need to setup the LIC_FILES_CHKSUM correctly, is your linux-imx a 
regular kernel source or does it contain other source?

LIC_FILES_CHKSUM is looking for a COPYING in the source directory, which 
may not be in your source area, you can look at 
tmp/work/mx35pdk-poky-linux/linux-imx-2.6.35.3-r0/git to check for the 
correct licensing files.


Sau!

> Thanks,
> Prashanth Shiva
> EmSyS, Larsen & Toubro Limited,
> Mysore | Ph: +91-821-2405582
> http://www.Lntemsys.com
>
>
>
> This mail is classified as :
> ( ) L&T EmSyS Proprietary ( ) L&T EmSyS Confidential ( x ) L&T EmSyS
> Internal Use ( ) L&T EmSyS General Business
>
> This email may contain confidential or privileged information for the
> intended recipient(s). If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system. Thanks!!
>
>
>
> *Larsen & Toubro Limited
>
> www.larsentoubro.com <http://www.larsentoubro.com>
>
> *This Email may contain confidential or privileged information for the
> intended recipient (s) If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
>
>
> *Larsen & Toubro Limited
>
> www.larsentoubro.com
>
> *This Email may contain confidential or privileged information for the
> intended recipient (s) If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


      reply	other threads:[~2011-06-01 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87C8C51E47F55D47ABF9BB39687792ED42021A@POCITMSEXMB01.LntUniverse.com>
2011-06-01 14:42 ` FW: problem in LIC_FILES_CHKSUM Nikhil Kamath
2011-06-01 16:28   ` 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=4DE668B1.6000305@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Nikhil.Kamath@lnties.com \
    --cc=Prashanth.Shiva@lnties.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.