From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Yocto <yocto@yoctoproject.org>
Subject: Linux Yocto style kernel errors with no config fragments
Date: Thu, 12 Jun 2014 14:46:57 +0100 [thread overview]
Message-ID: <5399AF51.1030605@dynamicdevices.co.uk> (raw)
Hi,
I was taking a quick look at converting the meta-raspberrypi kernel
recipes to be linux-yocto style, to provide config frag support.
I'm working with poky master, referencing linux-yocto-custom.bb in
meta-skeleton
This seems to be working as far as it goes, but I get an error when
there are no configuration fragments supplied on the SRC_URI.
| DEBUG: Executing shell function do_kernel_configme
| [INFO] doing kernel configme
| [INFO] Configuring target/machine combo: "standard/raspberrypi"
| [INFO] collecting configs in ./.meta/meta-series
| cat: .meta/cfg/standard/raspberrypi/config_frag.txt: No such file or
directory
| cat: .meta/cfg/standard/raspberrypi/config_frag.txt: No such file or
directory
| mv: cannot stat
`[.....]/tmp/work/raspberrypi-poky-linux-gnueabi/linux-raspberrypi/3.12.21+gitcb53ea88f75180cc1ba74f7f197c8e3fd4f47cfe-r0/linux-raspberrypi-standard-build/.tmp.config*':
No such file or directory
| creation of pre-processed config data failed
| config of "standard/raspberrypi" failed
When I add an empty file://dummy.cfg file to the SRC_URI then I can
build successfully.
When I add a dummy option CONFIG_DUMMY=y into that fragment file
do_kernel_configcheck correctly flags up that this is an unknown option
for the kernel so it seems to be pulled in ok.
Can anybody advise?
Thanks,
Alex
next reply other threads:[~2014-06-12 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 13:46 Alex J Lennon [this message]
2014-06-12 13:53 ` Linux Yocto style kernel errors with no config fragments Bruce Ashfield
2014-06-12 13:59 ` Alex J Lennon
2014-06-12 14:52 ` Alex J Lennon
2014-06-12 14:54 ` Bruce Ashfield
2014-06-12 14:59 ` Alex J Lennon
2014-06-12 14:53 ` Bruce Ashfield
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=5399AF51.1030605@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--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.