Re: Package for development of out-of-tree kernel modules written in Rust
- To: Ben Hutchings <ben@decadent.org.uk>
- Cc: NoisyCoil <noisycoil@disroot.org>, debian-kernel@lists.debian.org, debian-rust@lists.debian.org
- Subject: Re: Package for development of out-of-tree kernel modules written in Rust
- From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
- Date: Sat, 3 May 2025 16:53:23 +0200
- Message-id: <[🔎] CANiq72nXi_EkScAit3vBtbF-4nk6uTJmef2pzCpRxsv+XEwLSQ@mail.gmail.com>
- In-reply-to: <f1c4ab4ec9b9c91ffa168ef1a58bb41ff26785e3.camel@decadent.org.uk>
- References: <CANiq72nOwV5yMXee5CC1gmRDs-ZULb89SeKL6pro2LuKBqLX=Q@mail.gmail.com> <f381b303b3858bdb2a4e389da7531f3109c99db7.camel@decadent.org.uk> <8294a676-b85d-4901-bd5b-64531733b100@disroot.org> <CANiq72mec5AvzaR3yAA4oUgjPtp6ZqLFaW7z=Ey4J5ZX5GFB2w@mail.gmail.com> <20250402203804.r5go6wipv3i6rmwv@shell.thinkmo.de> <20250402211027.yned7ytqevpygnpj@shell.thinkmo.de> <0fb7dc74-1ee5-4b30-8edd-c1db97bbaa85@disroot.org> <b684b03d-f333-4135-870e-e3db9f165926@disroot.org> <20250403142812.kf5ucbblwytoac7h@shell.thinkmo.de> <5058a094-6d9a-4164-aabc-34c3f0db4a75@disroot.org> <20250403183302.iao7vqal7uxh7zn4@shell.thinkmo.de> <CANiq72=9BTu_1nRF0f3EkD4a9GuF5HtOJpDKyBXMQ+-knzcstA@mail.gmail.com> <6b625d6c-4111-4645-9a24-cc02300d32fb@disroot.org> <CANiq72=2sBY9aEEUCFQobTqUB7E_=mebJnPjeD3_NmqjrXpdzg@mail.gmail.com> <f1c4ab4ec9b9c91ffa168ef1a58bb41ff26785e3.camel@decadent.org.uk>
On Wed, Apr 16, 2025 at 5:36 PM Ben Hutchings <ben@decadent.org.uk> wrote:
>
> I don't see why there would be a problem with mixing objects built using
> native and cross- C compilers with the same target and version. (Unless
> you enable gcc plugins, which we don't.)
It may work, but as far as I was told, it is not supported.
> Official Debian binary packages are built natively, but there is also a
> standard way to cross-build them and the kernel source package supports
> this. The resulting binary packages should be functionally identical.
I see -- thanks for the details Ben.
Some news related to this: the other day I needed the kernel config in
the procedural macros in order to do conditional compilation based on
the compilers features/version (which is how we usually do it in the
rest of the code), which may land on v6.16 or v6.17.
Cheers,
Miguel
Reply to: