Re: Package for development of out-of-tree kernel modules written in Rust
On Thu, Apr 03, 2025 at 07:23:56PM +0200, NoisyCoil wrote:
> 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?
I would assume it's rustc that's broken. It gives a diagnostic that is
not at all related to the thing you claimed to have removed for testing.
> > 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.
What the heck is this good for, where config dependency would be useful?
> 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?
It's the basic setup of the Debian Linux package. linux-kbuild is for
the build arch, aka the system the build runs on; linux-headers-* is for
the host arch, aka the system the kernel is built for.
So, either "macros" is static and unchanging, then we can just build it
and don't care. Or it is dynamic, then it needs to be built next to the
external module and not be shipped at all.
Bastian
--
A father doesn't destroy his children.
-- Lt. Carolyn Palamas, "Who Mourns for Adonais?",
stardate 3468.1.
Reply to: