``` checking for sed --in-place... --in-place checking for cppcheck... no checking for shellcheck... yes checking for checkbashisms... no checking for parallel... no checking kernel source and build directories... done checking kernel source directory... /usr/src/linux checking kernel build directory... /usr/src/linux checking kernel source version... 6.0.11-gentoo checking for kernel config option compatibility... done checking whether CONFIG_MODULES is defined... no configure: error: *** This kernel does not include the required loadable module *** support! *** *** To build OpenZFS as a loadable Linux kernel module *** enable loadable module support by setting *** `CONFIG_MODULES=y` in the kernel configuration and run *** `make modules_prepare` in the Linux source tree. *** *** If you don't intend to enable loadable kernel module *** support, please compile OpenZFS as a Linux kernel built-in. *** *** Prepare the Linux source tree by running `make prepare`, *** use the OpenZFS `--enable-linux-builtin` configure option, *** copy the OpenZFS sources into the Linux source tree using *** `./copy-builtin <linux source directory>`, *** set `CONFIG_ZFS=y` in the kernel configuration and compile *** kernel as usual. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-fs/zfs-kmod-2.1.9/work/zfs-2.1.9/config.log * ERROR: sys-fs/zfs-kmod-2.1.9::gentoo failed (configure phase): * econf failed * * Call stack: * ebuild.sh, line 136: Called src_configure * environment, line 3342: Called econf 'HOSTCC=x86_64-pc-linux-gnu-gcc' '--bindir=/bin' '--sbindir=/sbin' '--with-config=kernel' '--with-linux=/usr/src/linux' '--with-linux-obj=/usr/src/linux' '--disable-debug' * phase-helpers.sh, line 730: Called __helpers_die 'econf failed' * isolated-functions.sh, line 112: Called die * The specific snippet of code: * die "$@" * * If you need support, post the output of `emerge --info '=sys-fs/zfs-kmod-2.1.9::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-fs/zfs-kmod-2.1.9::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-fs/zfs-kmod-2.1.9/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/zfs-kmod-2.1.9/temp/environment'. * Working directory: '/var/tmp/portage/sys-fs/zfs-kmod-2.1.9/work/zfs-2.1.9' * S: '/var/tmp/portage/sys-fs/zfs-kmod-2.1.9/work/zfs-2.1.9' ``` ``` $ zgrep -i config_modules /proc/config.gz CONFIG_MODULES_USE_ELF_RELA=y CONFIG_MODULES=y CONFIG_MODULES_TREE_LOOKUP=y ``` ``` $ grep -i config_modules /usr/src/linux/.config CONFIG_MODULES_USE_ELF_RELA=y CONFIG_MODULES=y CONFIG_MODULES_TREE_LOOKUP=y ``` ``` $ uname -a Linux cbrspc7 6.0.11-gentoo #1 SMP PREEMPT_DYNAMIC Sun Dec 4 21:20:42 EST 2022 x86_64 AMD Ryzen 9 5950X 16-Core Processor AuthenticAMD GNU/Linux ```
Created attachment 849736 [details] /var/tmp/portage/sys-fs/zfs-kmod-2.1.9/work/zfs-2.1.9/config.log
I can reproduce this using =sys-kernel/gentoo-kernel-6.1.8
This comment [1] suggests that this might be to do with GCC versioning. I'm using =sys-devel/gcc-12.2.1_p20230121-r1, but marius appears to be using =sys-devel/gcc-11.3.1_p20221209. [1]: https://github.com/openzfs/zfs/issues/13625#issuecomment-1176732405
This tends to be a generic error that means the kernel can't configure properly (like e.g. mismatched compiler). For example, a new GCC snapshot might mean that it can no longer find the right paths. But this is less of an issue now we use --with-major-version-only.
(In reply to Sam James from comment #4) > This tends to be a generic error that means the kernel can't configure > properly (like e.g. mismatched compiler). Re-emerging gentoo-kernel after upgrading to gcc 12, then zfs-kmod seemed to work for me.
(In reply to Emily Rowlands from comment #5) > (In reply to Sam James from comment #4) > > This tends to be a generic error that means the kernel can't configure > > properly (like e.g. mismatched compiler). > > Re-emerging gentoo-kernel after upgrading to gcc 12, then zfs-kmod seemed to > work for me. Ah, yeah, we can't help with the major version jumps at all. But at least this will happen once per year or so now instead (only when major version changes).
Thank you, it was indeed due to a GCC version update. Recompiling the kernel with the newer GCC version fixed this issue.
