From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Yocto <yocto@yoctoproject.org>
Subject: Re: Linux Yocto style kernel errors with no config fragments
Date: Thu, 12 Jun 2014 14:59:36 +0100 [thread overview]
Message-ID: <5399B248.2070002@dynamicdevices.co.uk> (raw)
In-Reply-To: <5399B0F1.7040508@windriver.com>
On 12/06/2014 14:53, Bruce Ashfield wrote:
> On 14-06-12 09:46 AM, Alex J Lennon wrote:
>> 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?
>
> I have a fix for a similar issue in a patch queue that I'm going to
> finish work on short (as part of 1.7 development work) .. the error
> message that is generated in that scenario is certainly not much
> help to anyone.
>
> To see if this is the same issue, I'll ask a quick clarification
> question.
>
> From what you describe .. when you see the message, do you also
> have a defconfig on the SRC_URI ?
Hi Bruce,
Currently I'm using -
SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.12.y \
file://sl030raspberrypii2ckernel.patch \
file://dummy.cfg \
"
The original RPi recipe seems to be trying to use KERNEL_DEFCONFIG to use
an existing config within the tree so I had left that alone thus far,
but I'm not sure it
is being pulled in so am looking at this now too,
# NOTE: For now we pull in the default config from the RPi kernel GIT tree.
KERNEL_DEFCONFIG = "bcmrpi_defconfig"
Thanks,
Alex
next prev parent reply other threads:[~2014-06-12 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 13:46 Linux Yocto style kernel errors with no config fragments Alex J Lennon
2014-06-12 13:53 ` Bruce Ashfield
2014-06-12 13:59 ` Alex J Lennon [this message]
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=5399B248.2070002@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=bruce.ashfield@windriver.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.