All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Svilans <msvilans@aeonyx.ca>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: bbappend files and "ERROR: no recipes available for"
Date: Fri, 01 Nov 2013 15:43:19 -0400	[thread overview]
Message-ID: <52740457.5020101@aeonyx.ca> (raw)

Dear list,

I am working on a compact filesystem image, that contains firmware only 
for the network hardware on the motherboard.

Therefore, I created a linux-firmware.bbappend file, with the following 
contents:

> # Cherrypick the firmware files that we need for our hardware
>
> #FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>
> PACKAGES += "${PN}-rtl8168d-1"
>
> FILES_${PN}-rtl8168d-1 = " \
>   /lib/firmware/rtl_nic/rtl8168d-1.fw \
> "


However, running "bitbake linux-firmware" fails with this bbappend file 
present:


> ERROR: No recipes available for:
> /home/markus/yocto/genericx86-64-dora-10.0.0/meta-markus/recipes-kernel/linux-firmware/linux-firmware.bbappend
> ERROR: Command execution failed: Exited with 1


Other bbappend files, such as for custom kernel config for linux-yocto, 
worked without complaints.

So far, I was following the instructions for using bbappend files here:
http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#using-bbappend-files
http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html


 From what I can see, I am setting up my linux-firmware.bbappend file 
consistently with the instructions.

What am I doing wrong here?

Thanks very much
Markus





             reply	other threads:[~2013-11-01 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 19:43 Markus Svilans [this message]
2013-11-01 19:48 ` bbappend files and "ERROR: no recipes available for" Søren Holm
2013-11-01 20:18   ` Markus Svilans

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=52740457.5020101@aeonyx.ca \
    --to=msvilans@aeonyx.ca \
    --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.