All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: bbappend - Where should my file be?
Date: Tue, 30 Aug 2011 19:07:42 +0100	[thread overview]
Message-ID: <1314727662.5939.388.camel@rex> (raw)
In-Reply-To: <02B62B87-3FD5-421C-A344-9A808B1E9C99@keylevel.com>

On Fri, 2011-08-12 at 00:51 +0100, Chris Tapp wrote:
> I've got a linux-wrs_git.bbappend file in a layer (under poky laverne  
> 4.0.1) that contains:
> 
> COMPATIBLE_MACHINE_Vortex86DX = "Vortex86DX"
> WRMACHINE_Vortex86DX  = "common_pc"
> 
> FILESEXTRAPATHS := "${THISDIR}/${PN}"
> 
> SRC_URI += " file://defconfig"
> 
> Where should the defconfig file be relative to the bbappend?
> 
> I've tried:
> 
> MyLayer
>        +--- recipies
>                    +--- linux
>                             +--- linux-wrs_git.bbappend
>                             +--- linux-wrs_git
>                                              +--- defconfig
> 
> 
> However, my defconfig file isn't being picked up during do_unpack:
> 
> cp: cannot stat `/home/chris/yocto/yocto-versions/laverne-4.0.1/meta/ 
> recipes-kernel/linux/files/defconfig': No such file or directory
> NOTE: Unpacking /home/chris/yocto/yocto-downloads/ 
> git_git.pokylinux.org.linux-2.6-windriver.git.tar.gz to /home/chris/ 
> yocto/mbox-3300-build/tmp/work/Vortex86DX-poky-linux/linux- 
> wrs 
> -2.6.34 
> + 
> git0 
> + 
> b67e060194a38c6331da1532bd06446087a42b3b_0 
> +0431115c9d720fee5bb105f6a7411efb4f851d26-r12/
> NOTE: Unpacking /home/chris/yocto/yocto-versions/laverne-4.0.1/meta/ 
> recipes-kernel/linux/files/defconfig to /home/chris/yocto/mbox-3300- 
> build/tmp/work/Vortex86DX-poky-linux/linux- 
> wrs 
> -2.6.34 
> + 
> git0 
> + 
> b67e060194a38c6331da1532bd06446087a42b3b_0 
> +0431115c9d720fee5bb105f6a7411efb4f851d26-r12/
> ERROR: Task failed:
> 
> Which seems to show that it's not looking in FILESEXTRAPATHS.
> 
> The .bbappend file seems to be processed, as commenting out the  
> SRC_URI line gets rid of the error.
> 
> What have I got wrong?

I've just been looking at the open bug related to this
(http://bugzilla.yoctoproject.org/show_bug.cgi?id=1379) and I can't
reproduce an issue with layers ending with -numeric causing a
problem :/.

In the above example, 

recipies/linux/linux-wrs/defconfig

is the correct path since PN == "linux-wrs". (you had linux-wrs_git).
Could you check whether the layer numeric part is a red herring please
and whether the above path works?

Cheers,

Richard




  parent reply	other threads:[~2011-08-30 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 23:51 bbappend - Where should my file be? Chris Tapp
2011-08-11 23:57 ` Scott Garman
2011-08-12  0:28   ` Bruce Ashfield
2011-08-12  8:20     ` Chris Tapp
2011-08-12 12:59       ` Bruce Ashfield
2011-08-12 19:48         ` Chris Tapp
2011-08-17 16:32           ` Joshua Lock
2011-08-30 18:07 ` Richard Purdie [this message]
2011-08-31 19:33   ` Chris Tapp
2011-08-31 20:01     ` Richard Purdie

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=1314727662.5939.388.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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.