All of lore.kernel.org
 help / color / mirror / Atom feed
* Strange WARNING while do_kernel_configcheck()
@ 2012-08-08 19:35 Markus Hubig
  2012-08-08 19:39 ` Bruce Ashfield
  0 siblings, 1 reply; 4+ messages in thread
From: Markus Hubig @ 2012-08-08 19:35 UTC (permalink / raw)
  To: Yocto Project Mailing List

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Strange WARNING while do_kernel_configcheck()
  2012-08-08 19:35 Strange WARNING while do_kernel_configcheck() Markus Hubig
@ 2012-08-08 19:39 ` Bruce Ashfield
  2012-08-09 10:43   ` Markus Hubig
  0 siblings, 1 reply; 4+ messages in thread
From: Bruce Ashfield @ 2012-08-08 19:39 UTC (permalink / raw)
  To: Yocto Project Mailing List

On 12-08-08 03:35 PM, Markus Hubig wrote:
> 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?

Nope. But there was an interface change to that tool in particular in
master, so if you've ended up with kern-tools that are mismatched to
the bbclass .. you'd end up with them looking in the wrong place.

Cheers,

Bruce

>
> | 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
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Strange WARNING while do_kernel_configcheck()
  2012-08-08 19:39 ` Bruce Ashfield
@ 2012-08-09 10:43   ` Markus Hubig
  2012-08-09 12:32     ` Bruce Ashfield
  0 siblings, 1 reply; 4+ messages in thread
From: Markus Hubig @ 2012-08-09 10:43 UTC (permalink / raw)
  To: yocto

On Wed, Aug 08, 2012 at 03:39:48PM -0400, Bruce Ashfield wrote:
> On 12-08-08 03:35 PM, Markus Hubig wrote:
> >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?
> 
> Nope. But there was an interface change to that tool in particular in
> master, so if you've ended up with kern-tools that are mismatched to
> the bbclass .. you'd end up with them looking in the wrong place.

Hmm ok but since I use denzil, and denzil provides the bbclass *and* the
kernel revision for the meta branch ... why don't they match?

Cheers, Markus


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Strange WARNING while do_kernel_configcheck()
  2012-08-09 10:43   ` Markus Hubig
@ 2012-08-09 12:32     ` Bruce Ashfield
  0 siblings, 0 replies; 4+ messages in thread
From: Bruce Ashfield @ 2012-08-09 12:32 UTC (permalink / raw)
  To: yocto

On Thu, Aug 9, 2012 at 6:43 AM, Markus Hubig <mhubig@imko.de> wrote:
> On Wed, Aug 08, 2012 at 03:39:48PM -0400, Bruce Ashfield wrote:
>> On 12-08-08 03:35 PM, Markus Hubig wrote:
>> >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?
>>
>> Nope. But there was an interface change to that tool in particular in
>> master, so if you've ended up with kern-tools that are mismatched to
>> the bbclass .. you'd end up with them looking in the wrong place.
>
> Hmm ok but since I use denzil, and denzil provides the bbclass *and* the
> kernel revision for the meta branch ... why don't they match?

It could be one of the updates merged back to the -stable release. I'll fire up
a denzil build in the next while to see if I get the same results.

Cheers,

Bruce

>
> Cheers, Markus
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-08-09 12:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-08 19:35 Strange WARNING while do_kernel_configcheck() Markus Hubig
2012-08-08 19:39 ` Bruce Ashfield
2012-08-09 10:43   ` Markus Hubig
2012-08-09 12:32     ` Bruce Ashfield

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.