>>> Emerging (1 of 1) sys-fs/vhba-20211218-r1::local-repo * vhba-module-20211218.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 6.0.8-gentoo-ipwire * Checking for suitable kernel configuration options ... [ ok ] * Checking for suitable kernel configuration options ... [ ok ] >>> Unpacking source... >>> Unpacking vhba-module-20211218.tar.xz to /var/tmp/portage/sys-fs/vhba-20211218-r1/work >>> Source unpacked in /var/tmp/portage/sys-fs/vhba-20211218-r1/work >>> Preparing source in /var/tmp/portage/sys-fs/vhba-20211218-r1/work/vhba-module-20211218 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/sys-fs/vhba-20211218-r1/work/vhba-module-20211218 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/sys-fs/vhba-20211218-r1/work/vhba-module-20211218 ... ln: failed to create symbolic link 'Module.symvers': File exists * Preparing vhba module make -j3 -l3 HOSTCC=x86_64-pc-linux-gnu-gcc 'LDFLAGS=-m elf_x86_64' KDIR=/usr/src/linux modules make -C /usr/src/linux M=/var/tmp/portage/sys-fs/vhba-20211218-r1/work/vhba-module-20211218 modules make[1]: Entering directory '/usr/src/linux-6.0.8-gentoo' warning: the compiler differs from the one used to build the kernel The kernel was built by: gcc (Gentoo 12.2.1_p20221008 p1) 12.2.1 20221008 You are using: x86_64-pc-linux-gnu-gcc (Gentoo 12.2.1_p20221008 p1) 12.2.1 20221008 Maybe I'm missing something somewhere... Reproducible: Always
Same goes with other external module, e.g. net-misc/r8168. Cf https://bugs.gentoo.org/892003
Sorry, the above reference link content is faulty. Here's a valid snippet instead: make -C /usr/src/linux M=/var/tmp/portage/net-misc/r8168-8.051.02/work/r8168-8.051.02/src modules make[1]: Entering directory '/usr/src/linux-5.15.86-gentoo' warning: the compiler differs from the one used to build the kernel The kernel was built by: gcc (Gentoo 12.2.1_p20230121-r1 p10) 12.2.1 20230121 You are using: x86_64-pc-linux-gnu-gcc (Gentoo 12.2.1_p20230121-r1 p10) 12.2.1 20230121
How are you building your kernel? If doing it manually, it probably calls gcc via 'gcc' and not the full tuple name, while ebuilds prefer it in full as behaviour can vary. CONFIG_CC_VERSION_TEXT in e.g. /proc/config.gz should tell you. In any case, it's not a problem, just noisy.
(In reply to Sam James from comment #3) > How are you building your kernel? If doing it manually, it probably calls > gcc via 'gcc' and not the full tuple name, while ebuilds prefer it in full > as behaviour can vary. > > CONFIG_CC_VERSION_TEXT in e.g. /proc/config.gz should tell you. In any case, > it's not a problem, just noisy. Same here. I'm building kernel manually (make install). Which command to use to get the same compiler names?
Seems fixed as it doesn't occur any longer in sys-fs/vhba-20211218-r2. Closing
