[yocto] kernel menuconfig unusable Was: Updated Yocto Hands-on Kernel Lab available
On Fri, Feb 15, 2013 at 9:29 PM, Tom Zanussi wrote: > I'm happy to announce that an updated version of the Yocto 'Hands-on > Kernel Lab' has been released and is available here: This is awesome, and much appreciated (especially by those of us who can't make it out to these events). Following the lab, however, I very quickly ran into the dreaded "kernel menuconfig unusable" issue. Is there any way Liang Li's suggested fix[1] could make it into mainline and the danny branch which is used for these labs? Is there a better fix? Is there another way around this issue, perhaps with a pure conf/local.conf setting? Thanks and best regards, Trevor [1] http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html NOTE: simply setting OE_TERMINAL to "xterm" doesn't fix the problem, it only changes the terminal :-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel menuconfig unusable Was: Updated Yocto Hands-on Kernel Lab available
On Sun, 2013-02-17 at 16:22 -0500, Trevor Woerner wrote: > On Fri, Feb 15, 2013 at 9:29 PM, Tom Zanussi wrote: > > I'm happy to announce that an updated version of the Yocto 'Hands-on > > Kernel Lab' has been released and is available here: > > This is awesome, and much appreciated (especially by those of us who > can't make it out to these events). > > Following the lab, however, I very quickly ran into the dreaded > "kernel menuconfig unusable" issue. Is there any way Liang Li's > suggested fix[1] could make it into mainline and the danny branch > which is used for these labs? Is there a better fix? Is there another > way around this issue, perhaps with a pure conf/local.conf setting? > Yeah, I ran into this too on Fedora 17, but not Ubuntu. I thought it was a local thing and basically 'powered through it' and changed the settings, knowing I was seeing double. I don't know what the proper fix for this is - if it's the patch you pointed to, I'm not sure why it wasn't pulled in. If not, I guess a bug should be opened for it. Tom > Thanks and best regards, > Trevor > > [1] > http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html > > NOTE: simply setting OE_TERMINAL to "xterm" doesn't fix the problem, > it only changes the terminal :-) > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel menuconfig unusable Was: Updated Yocto Hands-on Kernel Lab available
On Sun, Feb 17, 2013 at 6:15 PM, Tom Zanussi wrote: > I guess a bug > should be opened for it. I have created https://bugzilla.yoctoproject.org/show_bug.cgi?id=3898 in the hope it doesn't get dropped again. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: Updated Yocto Hands-on Kernel Lab available
...sorry, I meant to CC the list too
-- Forwarded message --
From: Trevor Woerner
Date: Sun, Feb 17, 2013 at 9:15 PM
Subject: Re: [yocto] Updated Yocto Hands-on Kernel Lab available
To: Tom Zanussi
Hi Tom,
I can see how the kernel *.bb files get pulled in due to the following
line in each lab's layer configuration (${LAYERDIR}/conf/layer.conf):
BBFILES := "... ${LAYERDIR}/recipes-*/*/*.bb ..."
Since the *.bb files are located under
${LAYERDIR}/recipes-kernel/linux/.bb this matched the above
pattern.
What I can't figure out is why, for example, in lab1 are the kernel
patch files located in
${LAYERDIR}/recipes-kernel/linux/linux
while the kernel patch files for lab2 are in
${LAYERDIR}/recipes-kernel/linux/files
Does bitbake find the patch files for lab1 in a subdirectory called
"linux" because the recipe's name is linux_3.0.18.bb? Because I don't
see anything in that particular recipe which would suggest it
(bitbake) should look there (linux). And when I go to lab2 and rename
the "files" directory to "linux-yocto" the build doesn't work, so this
behaviour would seem to discount the belief that a patch directory
name can take on the recipe name and be found.
Best regards,
Trevor
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: Updated Yocto Hands-on Kernel Lab available
On Sun, 2013-02-17 at 21:16 -0500, Trevor Woerner wrote:
> ...sorry, I meant to CC the list too
>
>
> -- Forwarded message --
> From: Trevor Woerner
> Date: Sun, Feb 17, 2013 at 9:15 PM
> Subject: Re: [yocto] Updated Yocto Hands-on Kernel Lab available
> To: Tom Zanussi
>
>
> Hi Tom,
>
> I can see how the kernel *.bb files get pulled in due to the following
> line in each lab's layer configuration (${LAYERDIR}/conf/layer.conf):
>
> BBFILES := "... ${LAYERDIR}/recipes-*/*/*.bb ..."
>
> Since the *.bb files are located under
> ${LAYERDIR}/recipes-kernel/linux/.bb this matched the above
> pattern.
>
> What I can't figure out is why, for example, in lab1 are the kernel
> patch files located in
>
> ${LAYERDIR}/recipes-kernel/linux/linux
>
> while the kernel patch files for lab2 are in
>
> ${LAYERDIR}/recipes-kernel/linux/files
>
> Does bitbake find the patch files for lab1 in a subdirectory called
> "linux" because the recipe's name is linux_3.0.18.bb? Because I don't
> see anything in that particular recipe which would suggest it
> (bitbake) should look there (linux). And when I go to lab2 and rename
> the "files" directory to "linux-yocto" the build doesn't work, so this
> behaviour would seem to discount the belief that a patch directory
> name can take on the recipe name and be found.
>
Hi,
Yes, in lab1 bitbake finds the patch files because they're in the
'linux' subdirectory. It should also be able to find them if you
renamed that directory to 'linux-3.0.18', and it would also find them in
the 'files' directory. These subdirectories are added to FILESPATH in
base.bbclass:
FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}",
"${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"
Those are relative to a .bb, which is what we have in lab1 - the kernel
recipe is linux_3.0.18.bb.
In lab2, we have a linux-yocto_3.4.bbappend file rather than a .bb file.
If you look at the .bbappend, you can see:
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
which is what we need to add to the .bbappend to get bitbake to look in
the 'files' subdirectory under the .bbappend - since the FILESPATH is
relative to the base recipe in meta/, linux-yocto_3.4.bb, and not
our .bbappend, bitbake won't find the files under our .bbappend unless
we add our .bbappend's 'files' subdir to FILESPATH via FILESEXTRAPATHS.
If you wanted to change the name of the directory under the .bbappend to
'linux-yocto', you could just use:
FILESEXTRAPATHS_prepend := "${THISDIR}/linux-yocto:"
or better:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
Tom
> Best regards,
> Trevor
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
