All of lore.kernel.org
 help / color / mirror / Atom feed
From: p_j_r_m <p_j_r_m@yahoo.com>
To: Randy Witt <randy.e.witt@linux.intel.com>,
	 "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Append recipe LICENCE checksum problem
Date: Thu, 5 Mar 2015 22:58:34 +0000 (UTC)	[thread overview]
Message-ID: <1911460113.6376815.1425596314408.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <54F8C240.4060808@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3375 bytes --]

>You are overwriting the SRC_URI rather than appending to it. So my guess is that 
>the source isn't getting fetched, which is why it says it can't find the license 
>file.

I´ve change that to SRC_URI_append, but it had no effect and it still fails.
My recipe is an .bbappend to a grub recipe, and it has no sources. Should it have a source with a LICENCE file?
 
 

     El Jueves 5 de marzo de 2015 21:53, Randy Witt <randy.e.witt@linux.intel.com> escribió:
   

 On 03/05/2015 12:46 PM, p_j_r_m wrote:
> I have a layer meta-mycompany where i want to append to the grub_2.00 recipe placed at openembedded-core layer just to add my custom grub.cfg file.
> Also, I see there is ALREADY a grub-2.00.bbappend file in my BSP layer (meta-montavista-1.4).My layer has highest priority.
>
> So I wrote a recipe called grub-2.00.bbappend like this in my layer:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URI = "file://grub${MYBOARD}.cfg "

You are overwriting the SRC_URI rather than appending to it. So my guess is that 
the source isn't getting fetched, which is why it says it can't find the license 
file.


> FILES_${PN}_append = "${base_prefix}/boot"
>
> do_install_append() {
>    if [ ! -d ${D}${base_prefix}/boot/grub ]
>    then
>      install -m 0755 -d ${S}${base_prefix}/boot/grub ${D}${base_prefix}/boot/grub
>    fi
>    install -m 0755 ${WORKDIR}/grub${MYBOARD}.cfg ${D}${base_prefix}/boot/grub/grub.cfg
> }
>
> $MYBOARD is a custom name just to pick up the proper grub file for each platform.
>
> But when i do a "bitbake grub" I get:
>
> NOTE: Executing RunQueue Tasks
> ERROR: Function failed: grub: LIC_FILES_CHKSUM points to an invalid file: /opt/work/tmp/work/x86_64-montavista-linux/grub/2.00-r1.2.2/grub-2.00/COPYING
> ERROR: Logfile of failure stored in: /opt/work/tmp/work/x86_64-montavista-linux/grub/2.00-r1.2.2/temp/log.do_configure.628
> Log data follows:
> | DEBUG: Executing python function sysroot_cleansstate
> ...
> | DEBUG: Python function do_qa_configure finished
> | ERROR: Function failed: grub: LIC_FILES_CHKSUM points to an invalid file: /opt/work/tmp/work/x86_64-montavista-linux/grub/2.00-r1.2.2/grub-2.00/COPYING
> ERROR: Task 5 (/opt/work/tmp/layers/openembedded-core-1.4-1411101352/openembedded-core-1.4-1411101352/meta/recipes-bsp/grub/grub_2.00.bb, do_configure) failed with exit code '1'
>
> If i take my layer out of my conf/extra-layers.conf ,recipe builds ok.
>
> My layer is:
>
> releases
> ├── meta-mycompany
> │  ├── conf
> │  │  └── layer.conf
> │  ├── README
> │  ├── recipes
> │      ├── grub
> │      │  ├── files
> │      │  │  ├── grubatca.cfg
> │      │  │  └── grubmni.cfg
> │      │  └── grub_2.00.bbappend
> │      ├── images
> │          ├── mycompany-atca-image.bb
> │          └── mycompany-atca-image-buildcf.bb
> ├── meta-mycompany.tar.bz2
> ├── meta-mycompany.tar.bz2.md5
>
> Do you know what is the problem?
> Must an .append recipe also provide a LICENCE file? Where?
>
> Thank you
>

-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto




[-- Attachment #2: Type: text/html, Size: 5827 bytes --]

      reply	other threads:[~2015-03-05 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 20:46 Append recipe LICENCE checksum problem p_j_r_m
2015-03-05 20:53 ` Randy Witt
2015-03-05 22:58   ` p_j_r_m [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=1911460113.6376815.1425596314408.JavaMail.yahoo@mail.yahoo.com \
    --to=p_j_r_m@yahoo.com \
    --cc=randy.e.witt@linux.intel.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.