From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Yocto Project Mailing List <yocto@yoctoproject.org>
Subject: Re: 1.3_M3 do_kernel_config failes, config_frag.txt is crippled.
Date: Thu, 23 Aug 2012 09:31:15 -0400 [thread overview]
Message-ID: <503630A3.90606@windriver.com> (raw)
In-Reply-To: <20120823151259.f1550eb3-e33f-4100-93dc-f39eab90e4b1.mhubig@imko.de>
On 12-08-23 09:24 AM, Markus Hubig wrote:
> Hello @all,
>
> because I need the commit 'dcadeda' I switched from denzil to 1.3_M3.
> Now I get a strage error while do_kernel_config:
>
> | configme --reconfig --output<...>/linux-portuxg20-standard-build standard stamp9g20
> | [INFO] Configuring target/machine combo: "standard/stamp9g20"
> | [INFO] collecting configs in ./meta/meta-series
> | [##################################################] (completed in 0 seconds)
> | ERROR: could not sanitize configuration fragments
> | errors are logged in meta/cfg/standard/portuxg20/config.log
>
> Digin a bit deeper I found:
>
> | [INFO] Sanitizing meta/cfg/kernel-cache/features/fuse/fuse.cfg
> | [INFO] Sanitizing meta/cfg/kernel-cache/ktypes/standard/standard.cfg
> | [INFO] Sanitizing meta/cfg/kernel-cache/cfg/devtmpfs.cfg
> | [INFO] Sanitizing meta/cfg/kernel-cache/cfg/debugfs.cfg
> | [INFO] Sanitizing meta/cfgportuxg20
> ^^^^^^^^^^^^^^^^^
> | [ERROR] Kern frag does not exist
>
> And again a bit deeper I found that the file
>
> | ./meta/cfg/standard/portuxg20/config_frag.txt
>
> is somewhat crippled:
>
> | ...
> | /kernel-cache/ktypes/standard/standard.cfg
> | /kernel-cache/cfg/devtmpfs.cfg
> | /kernel-cache/cfg/debugfs.cfg
> | portuxg20
> ^^^^^^^^^
> | hardware.cfg
> | non-hardware.cfg
> | /kernel-cache/features/usb-net/usb-net.cfg
> | portuxg20
> | hardware.cfg
> | non-hardware.cfg
> | /kernel-cache/features/usb-net/usb-net.cfg
> | /hardware.cfg
> | /non-hardware.cfg
> | /portuxg20/portuxg20.cfg
> | /kernel-cache/features/netfilter/netfilter.cfg
> | /kernel-cache/features/taskstats/taskstats.cfg
>
> Who is creating this file?
Were you using yocto-bsp to create the BSP framework ? I did some test
builds of the layer you previously sent me, and I didn't reproduce the
problem, but this is the same thing that you had seen last week.
Do you have an updated layer that I can try against master ?
Bruce
>
> Cheers, Markus
>
next prev parent reply other threads:[~2012-08-23 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 13:24 1.3_M3 do_kernel_config failes, config_frag.txt is crippled Markus Hubig
2012-08-23 13:31 ` Bruce Ashfield [this message]
2012-08-23 16:18 ` Markus Hubig
2012-08-23 16:22 ` Markus Hubig
2012-08-23 16:26 ` Bruce Ashfield
2012-08-23 17:28 ` Markus Hubig
2012-08-23 17:33 ` 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=503630A3.90606@windriver.com \
--to=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.