All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Hubig <mhubig@imko.de>
To: Yocto Project Mailing List <yocto@yoctoproject.org>
Subject: Strange WARNING while do_kernel_configcheck()
Date: Wed, 8 Aug 2012 21:35:28 +0200	[thread overview]
Message-ID: <20120808193528.GA20546@imko.de> (raw)

Hello @all,

I'm working on a bsp vor the taskit stamp9g20 cpu module.

I have a bbappend file for the linux-yocto_3.2 kernel which was ones working
but now (after updating the denzil branch from 7.0 to 7.0.1) I get a strange
error while building the kernel.

I managed to track the problem down to a warning at the do_kernel_configcheck
task ... 

The warning I get is:

| NOTE: validating kernel configuration
| WARNING: Can't find any BSP hardware or required configuration fragments.
| WARNING: Looked at 
|  <snip>/linux/meta/cfg/standard/default/arm-versatile-926ejs/hdw_frags.txt
| and
|  <snip>/linux/meta/cfg/standard/default/arm-versatile-926ejs/required_frags.txt
| in directory:
|  <snip>/linux/meta/cfg/standard/default/arm-versatile-926ejs

Which seems to be the wrong path to look, course there is no such path like

<snip>/linux/meta/cfg/standard/default/arm-versatile-926ejs

the whole stuff is in:

<snip>/linux/meta/cfg/standard/default/stamp9g20

maybe I made a mistake in my linux-yocto_3.2.bbappend file?

| 1| FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
| 2| 
| 3| PR := "${PR}.1"
| 4| 
| 5| COMPATIBLE_MACHINE_stamp9g20 = "stamp9g20"
| 6| KBRANCH_stamp9g20  = "standard/default/arm-versatile-926ejs"
| 7| KMACHINE_stamp9g20  = "stamp9g20"
| 8| 
| 9| COMPATIBLE_MACHINE_portuxg20 = "portuxg20"
|10| KBRANCH_portuxg20  = "standard/default/arm-versatile-926ejs"
|11| KMACHINE_portux9g20  = "portuxg20"
|12| 
|13| SRC_URI += "file://hardware.cfg                  \
|14|             file://non-hardware.cfg              \
|15|            "
|16| 
|17| SRC_URI_append_stamp9g20 = "file://portuxg20.cfg \
|18|             file://portuxg20-preempt-rt.scc      \
|19|             file://portuxg20.scc                 \
|20|             file://portuxg20-standard.scc        \
|21|             "
|22| 
|23| SRC_URI_append_portuxg20 = "file://stamp9g20.cfg \
|24|             file://stamp9g20-preempt-rt.scc      \
|25|             file://stamp9g20.scc                 \
|26|             file://stamp9g20-standard.scc        \
|27|            "

The code which is -generating- responsible for this warning is:

(from "meta/classes/kernel-yocto.bbclass")

| 1| python do_kernel_configcheck() {
| 2|     import bb, re, string, sys, commands
| 3| 
| 4|     bb.plain("NOTE: validating kernel configuration")
| 5| 
| 6|     pathprefix = "export PATH=%s:%s; " % (d.getVar('PATH', True), "${S}/scripts/util/")
| 7|     cmd = d.expand("cd ${B}/..; kconf_check -config- ${B} ${S} ${B} ${KBRANCH}")
| 8|     ret, result = commands.getstatusoutput("%s%s" % (pathprefix, cmd))
| 9| 
|10|     bb.plain( "%s" % result )
|11| }

Cheers, Markus


             reply	other threads:[~2012-08-08 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 19:35 Markus Hubig [this message]
2012-08-08 19:39 ` Strange WARNING while do_kernel_configcheck() Bruce Ashfield
2012-08-09 10:43   ` Markus Hubig
2012-08-09 12:32     ` 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=20120808193528.GA20546@imko.de \
    --to=mhubig@imko.de \
    --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.