Kernel version, GCC and modules

Question

Several issues with modules occurred after today's kernel upgrade.
I think that the kernel that is pushed should be compiled with the compiler that we have in our systems.
If the kernel is compiled with a different gcc than the one that we have (today's 4.0.1 kernel is compiled with gcc-5.1) then we get issues with modules that we need to compile (e.g. vmware).
I solved worked around this issue by uncommenting the testing and the testing-multilib (i got skype) repo, to download gcc-5.1 and all its deps, compile the vmware modules with it and downgrade everything back.
Last edited by redsolja (2015-04-30 08:10:56)

Answer 1

redsolja wrote:
eduncan911 wrote:
redsolja wrote:
More to the topic, I think that there is a better solution/workaround for this, especially for a new installation.
You can just recompile the archlinux kernel, using exactly the same configuration file, but with your own gcc version (4.9.2). I think that this will enable compiling the vmware (and other) modules easier.
I would suggest using kernels and abs.
Just coming back to say you were right!  Rebuilding the kernel using the gcc version is the cleanest approach to stay on tip (and I'm assuming rebuilding the kernel every time a new version is released).
https://bbs.archlinux.org/viewtopic.php … 7#p1526907
I don't think that you 'll need to compile the kernel each time a new kernel is released. I guess gcc-5.1 isn't that far from getting into [core]. Just remember there are at least 3 workarounds for this:
enable [testing] repository and issue a pacman -Syyu. After that, compile the modules that you want to compile with the new gcc version. This is will work for as long as gcc-5.1 is in [testing] AND the kernel is compiled with that version. To get the gcc version that compiled the kernel you are booting, issue a journalctl -b and close to the top, you should see a line that looks like this:
arch kernel: Linux version 4.0.1-1-ARCH (builduser@tobias) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015
recompile the kernel with the gcc version that your system has. This is the most helpful article i think
downgrade. I would suggest downgrade
I am pretty sure that people will come with more workarounds for this, but I find these to to be the simplest.
Thanks.  Yep, those are options.  But for vmware I did try all 3.
#1 i could get to compile with patched source under gcc 5.1 in testing but the binary would hard lock the VM guest.  I did this on two different machines and two Arch setups.  So i don't think it was me.
#3 downgrading the kernel couldn't be done on a new install without the pacman cache for the previous kernel.  someone did link me to the ARM archives and i was in the process of locking down my pacman to a specific date.  but that started to feel dirty, limiting my entire system just to get an older kernel.  one of the main reasons i'm switching to Arch is to have the latest and greatest.  but if i time lock my pacman, what's the point?
hence, why i ended up with #2 - just use ABS and recompile the existing kernel and headers.
thanks again!  it was really helpful!
Last edited by eduncan911 (2015-05-08 12:26:38)