CONFIG_TARGET=x86_64 is invalid. Valid: target|subtarget|subtarget_target

For Developers
1

I'd like to run the kernel_menuconfig for x86/64 but am unsure about the syntax. I tried:
make kernel_menuconfig CONFIG_TARGET=x86_64 V=s

But that gave:

/scratch/union/include/target.mk:224: *** CONFIG_TARGET=x86_64 is invalid. Valid: target|subtarget|subtarget_target|env.  Stop.
make[2]: Leaving directory '/scratch/union/toolchain/fortify-headers'
time: toolchain/fortify-headers/compile#0.00#0.00#0.01
    ERROR: toolchain/fortify-headers failed to build.
make[1]: *** [toolchain/Makefile:93: toolchain/fortify-headers/compile] Error 1

My device is just x86/64 so what is the correct value of CONFIG_TARGET in this context?

2

CONFIG_TARGET=64?

According to this https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem#kernel_configuration_optional

3

That too throws the same error:

/scratch/union/include/target.mk:224: *** CONFIG_TARGET=64 is invalid. Valid: target|subtarget|subtarget_target|env.  Stop.
make[4]: Leaving directory '/scratch/union/target/linux'
time: target/linux/prereq#0.00#0.00#0.01
    ERROR: target/linux failed to build.
4

I found: https://github.com/openwrt/openwrt/commit/68e672f32df3d6b8a75534df5962ac99b693601b

I think this is what has changed the behavior. I am still unclear what a valid value is for this variable...

1 Like
5

I use this command make kernel_menuconfig CONFIG_TARGET=subtarget -j$(nproc)

2 Likes
6

Ah! subtarget is a literal not a variable which I assume is read from the .config ... makes sense now, thank you!

EDIT: I just updated the wiki.

7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.