Skip to main content ↑ ↓
Topic: virtualbox-host-dkms: Compile only for GCC kernels: module freezes clang kernels (Read 278 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

virtualbox-host-dkms: Compile only for GCC kernels: module freezes clang kernels

Ahoj,

according to this comment from VirtualBox upstream:
Quote
We do not officially support CLANG on Linux host (only GCC is supported).
clang compiled Linux kernels are not supported by the VirtualBox host kernel modules.
And I experience kernel freeze when I actually do that.

So I suggest to add some logic to the virtualbox PKGBUILD that the package virtualbox-host-dkms only compiles a module for Linux kernels compiled with gcc, not with clang.

Regards!

Re: virtualbox-host-dkms: Compile only for GCC kernels: module freezes clang kernels

Reply #1 –
I don't know if I get it right, but we're already using gcc. You can check on the same PKGBUILD you left on the link.

marzosh

Re: virtualbox-host-dkms: Compile only for GCC kernels: module freezes clang kernels

Reply #2 –
Quote from: marzosh – on
I don't know if I get it right, but we're already using gcc. You can check on the same PKGBUILD you left on the link.
I mean when someone has a custom compiled kernel, and has this compiled using CLANG.

As I have.

And then install virtualbox-host-dkms.

It then, _after_ installing the package, builds virtualbox host modules via DKMS also for CLANG compiled kernels, and it builds them with CLANG.

And when I then launch a VirtualBox VM, the system hard-freezes.
 

Re: virtualbox-host-dkms: Compile only for GCC kernels: module freezes clang kernels

Reply #3 –
Briefly looking, this seems like upstream and intended behavior by dkms If it detects that the kernel is compiled with clang, it will use clang for dkms so nothing in that package would change this.

I'm not even sure if what you are attempting would even work anyway. I thought all modules need to be compiled by the same compiler. At the very least, I know things go wrong if gcc versions mismatch so mixing clang and gcc sounds like a recipe for failure. If you need this module, I would suggest just sticking to gcc for your kernel. But regardless, this is beyond our control AFAIK. Artix is a gnu distro so we use gcc for everything by default.