Skip to content

Checking whether a certain CONFIG_* is set

Thomas Petazzoni buildroot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH v1 0/2] Checking whether a certain CONFIG_* is set

Dear Yann E. MORIN,

Quoted 9 lines · Yann E. MORIN

I think the plan I'll be goign with is to add a hidden Kconfig knob that packages that want to build a kernel module will have to select.

Then, if that option is set, we can force-on support for modules in linux.mk. Note: if the option is not set, we would *not* disable support for modules, and let it as set in the user-provided (def)config file.

So, all in all, that would solve the xtables-addons issue, because we would be handling CONFIG_MODULE explicitly.

Sounds good to me.

Quoted 7 lines

Now, there are two questions:

- will we need to _check_ for any arbitrary kernel option to be set, and offer packages a simple mean to do so?

- will we need to _force_ (on or off) any other kernel option, and offer packages a simple mean to do so?

We already do your second item.

In general, I'd like to keep the handling of the kernel configuration to be as minimal as possible. Otherwise, we'll quickly enter a situation where we need to enable different kernel options depending on the kernel version. It can quickly become a real nightmare. Buildroot has always been about the user knowing what (s)he is doing, including in terms of making sure that the kernel configuration matches what is done in userspace.

Thanks,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Read the cover letter in its thread