Re: [OE-core] What does "do_menuconfig is disabled" really mean?
On 16-05-2024 13:58, Mike Looijmans via lists.openembedded.org wrote:
On 16-05-2024 13:41, Mike Looijmans via lists.openembedded.org wrote:
On 16-05-2024 13:34, Ross Burton wrote:
On 16 May 2024, at 12:03, Mike Looijmans via lists.openembedded.org
wrote:
Using scartgap branch, trying to create a kernel recipe for a custom
LS1028 machine.
The recipe in meta-freescale for the ls1028ardb is hopelessly outdated and
produces a 5.10 kernel.
So for my custom board based on the ls1028 I want to create a recipe that
builds a mainline kernel (I don't need GPU or fancy things that require
firmware or special drivers, so mainline should be fine).
I started out trying to get linux-yocto to build for my board, so copied
the "skeleton" recipe, adjusted a bit (add COMPATIBLE_MACHINE and a
defconfig).
But when I then run "bitbake -c menuconfig virtual/kernel" I always get
this message:
ERROR: linux-yocto-*-6.6+git-r0 do_menuconfig: do_menuconfig is disabled,
please check KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.
I tried starting with a copy of recipes like linux-fscl, same error. Always.
(note: I've run "menuconfig" a million times by now, for dozens of boards,
so it's not the system).
I tried adding
KCONFIG_CONFIG_ENABLE_MENUCONFIG="true"
to my recipe, but that also had no effect.
The log file also contains no information whatsoever.
What's the real issue?
cml1.bbclass has this:
KCONFIG_CONFIG_ENABLE_MENUCONFIG ??= “true"
…
if not bb.utils.to_boolean(d.getVar("KCONFIG_CONFIG_ENABLE_MENUCONFIG")):
bb.fatal("do_menuconfig is disabled, please check
KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.”)
So if you’re seeing that message then _something_ is assigning that
variable to false. Use bitbake-getvar to identify what that is.
Interesting, that points to "uboot-config.bbclass:147" which sets it to
false. I'm not building u-boot here, I'm building the kernel?
$ bitbake-getvar -r linux-fslc KCONFIG_CONFIG_ENABLE_MENUCONFIG
#
# $KCONFIG_CONFIG_ENABLE_MENUCONFIG [3 operations]
# set /.../oe-core/meta/classes-recipe/cml1.bbclass:35
# [_defaultval] "true"
# set uboot-config.bbclass:147
[__anon_148__..._oe_core_meta_classes_recipe_uboot_config_bbclass]
# "false"
# set uboot-config.bbclass:147
[__anon_148__..._oe_core_meta_classes_recipe_uboot_config_bbclass]
# "false"
# pre-expansion value:
# "false"
KCONFIG_CONFIG_ENABLE_MENUCONFIG="false"
This is because of using "fitImage":
meta/classes-recipe/kernel-fitimage.bbclass:inherit kernel-uboot
kernel-artifact-names uboot-config
I can specify this in the kernel recipe to make this error go away:
UBOOT_CONFIG = "tfa"
But then the menuconfig command just exits silently and does nothing whatsoever.
So the issue turns out to be that setting KERNEL_IMAGETYPES = "fitImage"
breaks menuconfig for the kernel in the scartgap branch.
Only way I've been able to run menuconfig is to temporarily change
KERNEL_IMAGETYPES to something else, then do the kernel configuration and when
done change it back again.
M.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199510):
https://lists.openembedded.org/g/openembedded-core/message/199510
Mute This Topic: https://lists.openembedded.org/mt/106132236/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] What does "do_menuconfig is disabled" really mean?
On 16-05-2024 13:41, Mike Looijmans via lists.openembedded.org wrote:
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topic.nl
W: www.topic.nl
Please consider the environment before printing this e-mail
On 16-05-2024 13:34, Ross Burton wrote:
On 16 May 2024, at 12:03, Mike Looijmans via lists.openembedded.org
wrote:
Using scartgap branch, trying to create a kernel recipe for a custom LS1028
machine.
The recipe in meta-freescale for the ls1028ardb is hopelessly outdated and
produces a 5.10 kernel.
So for my custom board based on the ls1028 I want to create a recipe that
builds a mainline kernel (I don't need GPU or fancy things that require
firmware or special drivers, so mainline should be fine).
I started out trying to get linux-yocto to build for my board, so copied
the "skeleton" recipe, adjusted a bit (add COMPATIBLE_MACHINE and a
defconfig).
But when I then run "bitbake -c menuconfig virtual/kernel" I always get
this message:
ERROR: linux-yocto-*-6.6+git-r0 do_menuconfig: do_menuconfig is disabled,
please check KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.
I tried starting with a copy of recipes like linux-fscl, same error. Always.
(note: I've run "menuconfig" a million times by now, for dozens of boards,
so it's not the system).
I tried adding
KCONFIG_CONFIG_ENABLE_MENUCONFIG="true"
to my recipe, but that also had no effect.
The log file also contains no information whatsoever.
What's the real issue?
cml1.bbclass has this:
KCONFIG_CONFIG_ENABLE_MENUCONFIG ??= “true"
…
if not bb.utils.to_boolean(d.getVar("KCONFIG_CONFIG_ENABLE_MENUCONFIG")):
bb.fatal("do_menuconfig is disabled, please check
KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.”)
So if you’re seeing that message then _something_ is assigning that variable
to false. Use bitbake-getvar to identify what that is.
Interesting, that points to "uboot-config.bbclass:147" which sets it to false.
I'm not building u-boot here, I'm building the kernel?
$ bitbake-getvar -r linux-fslc KCONFIG_CONFIG_ENABLE_MENUCONFIG
#
# $KCONFIG_CONFIG_ENABLE_MENUCONFIG [3 operations]
# set /.../oe-core/meta/classes-recipe/cml1.bbclass:35
# [_defaultval] "true"
# set uboot-config.bbclass:147
[__anon_148__..._oe_core_meta_classes_recipe_uboot_config_bbclass]
# "false"
# set uboot-config.bbclass:147
[__anon_148__..._oe_core_meta_classes_recipe_uboot_config_bbclass]
# "false"
# pre-expansion value:
# "false"
KCONFIG_CONFIG_ENABLE_MENUCONFIG="false"
This is because of using "fitImage":
meta/classes-recipe/kernel-fitimage.bbclass:inherit kernel-uboot
kernel-artifact-names uboot-config
I can specify this in the kernel recipe to make this error go away:
UBOOT_CONFIG = "tfa"
But then the menuconfig command just exits silently and does nothing whatsoever.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199484):
https://lists.openembedded.org/g/openembedded-core/message/199484
Mute This Topic: https://lists.openembedded.org/mt/106132236/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] What does "do_menuconfig is disabled" really mean?
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topic.nl
W: www.topic.nl
Please consider the environment before printing this e-mail
On 16-05-2024 13:34, Ross Burton wrote:
On 16 May 2024, at 12:03, Mike Looijmans via lists.openembedded.org
wrote:
Using scartgap branch, trying to create a kernel recipe for a custom LS1028
machine.
The recipe in meta-freescale for the ls1028ardb is hopelessly outdated and
produces a 5.10 kernel.
So for my custom board based on the ls1028 I want to create a recipe that
builds a mainline kernel (I don't need GPU or fancy things that require
firmware or special drivers, so mainline should be fine).
I started out trying to get linux-yocto to build for my board, so copied the
"skeleton" recipe, adjusted a bit (add COMPATIBLE_MACHINE and a defconfig).
But when I then run "bitbake -c menuconfig virtual/kernel" I always get this
message:
ERROR: linux-yocto-*-6.6+git-r0 do_menuconfig: do_menuconfig is disabled,
please check KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.
I tried starting with a copy of recipes like linux-fscl, same error. Always.
(note: I've run "menuconfig" a million times by now, for dozens of boards, so
it's not the system).
I tried adding
KCONFIG_CONFIG_ENABLE_MENUCONFIG="true"
to my recipe, but that also had no effect.
The log file also contains no information whatsoever.
What's the real issue?
cml1.bbclass has this:
KCONFIG_CONFIG_ENABLE_MENUCONFIG ??= “true"
…
if not bb.utils.to_boolean(d.getVar("KCONFIG_CONFIG_ENABLE_MENUCONFIG")):
bb.fatal("do_menuconfig is disabled, please check
KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.”)
So if you’re seeing that message then _something_ is assigning that variable to
false. Use bitbake-getvar to identify what that is.
Interesting, that points to "uboot-config.bbclass:147" which sets it to false.
I'm not building u-boot here, I'm building the kernel?
$ bitbake-getvar -r linux-fslc KCONFIG_CONFIG_ENABLE_MENUCONFIG
#
# $KCONFIG_CONFIG_ENABLE_MENUCONFIG [3 operations]
# set /.../oe-core/meta/classes-recipe/cml1.bbclass:35
# [_defaultval] "true"
# set uboot-config.bbclass:147
[__anon_148__..._oe_core_meta_classes_recipe_uboot_config_bbclass]
# "false"
# set uboot-config.bbclass:147
[__anon_148__..._oe_core_meta_classes_recipe_uboot_config_bbclass]
# "false"
# pre-expansion value:
# "false"
KCONFIG_CONFIG_ENABLE_MENUCONFIG="false"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199483):
https://lists.openembedded.org/g/openembedded-core/message/199483
Mute This Topic: https://lists.openembedded.org/mt/106132236/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] What does "do_menuconfig is disabled" really mean?
On 16 May 2024, at 12:03, Mike Looijmans via lists.openembedded.org
wrote:
>
> Using scartgap branch, trying to create a kernel recipe for a custom LS1028
> machine.
>
> The recipe in meta-freescale for the ls1028ardb is hopelessly outdated and
> produces a 5.10 kernel.
>
> So for my custom board based on the ls1028 I want to create a recipe that
> builds a mainline kernel (I don't need GPU or fancy things that require
> firmware or special drivers, so mainline should be fine).
>
> I started out trying to get linux-yocto to build for my board, so copied the
> "skeleton" recipe, adjusted a bit (add COMPATIBLE_MACHINE and a defconfig).
>
> But when I then run "bitbake -c menuconfig virtual/kernel" I always get this
> message:
>
> ERROR: linux-yocto-*-6.6+git-r0 do_menuconfig: do_menuconfig is disabled,
> please check KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.
>
> I tried starting with a copy of recipes like linux-fscl, same error. Always.
>
> (note: I've run "menuconfig" a million times by now, for dozens of boards, so
> it's not the system).
>
> I tried adding
> KCONFIG_CONFIG_ENABLE_MENUCONFIG="true"
> to my recipe, but that also had no effect.
>
> The log file also contains no information whatsoever.
>
> What's the real issue?
cml1.bbclass has this:
KCONFIG_CONFIG_ENABLE_MENUCONFIG ??= “true"
…
if not bb.utils.to_boolean(d.getVar("KCONFIG_CONFIG_ENABLE_MENUCONFIG")):
bb.fatal("do_menuconfig is disabled, please check
KCONFIG_CONFIG_ENABLE_MENUCONFIG variable.”)
So if you’re seeing that message then _something_ is assigning that variable to
false. Use bitbake-getvar to identify what that is.
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199482):
https://lists.openembedded.org/g/openembedded-core/message/199482
Mute This Topic: https://lists.openembedded.org/mt/106132236/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] What does "do_menuconfig is disabled" really mean?
Using scartgap branch, trying to create a kernel recipe for a custom LS1028 machine. The recipe in meta-freescale for the ls1028ardb is hopelessly outdated and produces a 5.10 kernel. So for my custom board based on the ls1028 I want to create a recipe that builds a mainline kernel (I don't need GPU or fancy things that require firmware or special drivers, so mainline should be fine). I started out trying to get linux-yocto to build for my board, so copied the "skeleton" recipe, adjusted a bit (add COMPATIBLE_MACHINE and a defconfig). But when I then run "bitbake -c menuconfig virtual/kernel" I always get this message: ERROR: linux-yocto-*-6.6+git-r0 do_menuconfig: do_menuconfig is disabled, please check KCONFIG_CONFIG_ENABLE_MENUCONFIG variable. I tried starting with a copy of recipes like linux-fscl, same error. Always. (note: I've run "menuconfig" a million times by now, for dozens of boards, so it's not the system). I tried adding KCONFIG_CONFIG_ENABLE_MENUCONFIG="true" to my recipe, but that also had no effect. The log file also contains no information whatsoever. What's the real issue? -- Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijm...@topic.nl W: www.topic.nl -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#199460): https://lists.openembedded.org/g/openembedded-core/message/199460 Mute This Topic: https://lists.openembedded.org/mt/106132236/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
