On 03/04/25 16:28, Bastian Blank wrote:
Please reference the bug report for this. Removing a file needs to produce a file not found error if it is required.
What bug report? Is this a suggestion to file one against the upstream kernel?
But this means this library needs to be shipped in linux-kbuild and properly referenced in the build.
Miguel said they are unwilling to commit to macros being config-independent, so it can't go in linux-kbuild as-is. To be clear, are you suggesting that it be made config-independent so it can be built in the package for the build architecture (in a cross-compilation scenario), and then used for arbitrary target architectures, hence why it must be config-independent?
Related to this, I have a question for Miguel: assuming that macros can be made config-independent, can one then use the libmacros.so built with some kernel for building modules for another kernel (let's say same version and either a different config or a different architecture)? Or libmacros.so is specific to the build?