If I download the fresh buildroot (as of 2024), I can see that when I don’t explicitly select the option to build with u-boot, on running make help I will not see anything related to u-boot. On the other hand, if I run menuconfig and select u-boot, I will see the u-boot related configuration options. How does this mechanism work?

I’m working on a linux system using buildroot. I have implemented using the rootfs overlay the script to launch a kernel driver. The script is named S98modules. I did the make to compile the filesystem and I verified it using QEMU.
At the startup of QEMU I see the error message: /etc/init.d/rcS: line 23 /etc/init.d/S98modules: not found

I have two custom modules (lets say A and B where B depends on exported functions in A) with Config.in specified in respective sub folders within Buildroot/package folder. In the main Config.in I have specified the order , first source A’s Config.in then B’s. However this order is not maintained for some reason, B is compiled first and fails since I have A’s function calls in B and referenced thru a header file that has not been copied from original location to build location yet.
Why does B get compiled first, anybody have any clue? I have tried adding depends on B statement in B’s config but didnt make a difference.

I want to install Buildroot on a Debian 11. When installing the mandatory packages, however, I have the problem that the package which cannot be found. How can I still install this package?

I am working with a Linux-based system that I build using the build root so I wanted to add a tool that does compliance Testing called as openscap, I wanted to add this in the packages so that it becomes available in the menuconfig.