Hide Forgot
Description of problem: Source supplied in the distribution don't compile correctly with the same configuration stored in configs. It gives error in cipe module, and in all optional components Version-Release number of selected component (if applicable): The one in RedHat 9.0 Shrike How reproducible: Steps to Reproduce: 1.make xconfig 2.load athlon single processor configuration 3.make deps 4.make bzImage / make install 4.make modules <- here it gives error and never go till the end
you forgot "make mrproper" as first step
I've seen this before (see Red Hat Bugzilla # 75152). I can reproduce this bug (88129) by doing : "cd /usr/src/linux-2.4" "make clean" "make mrproper" "make xconfig" (choose 'load configuration from file') \ enter "configs/kernel-2.4.20-athlon.config" "make dep && make bzImage && make modules" The compile process then aborts with : <snip> fs/fs.o(.text+0x350f2): In function `zisofs_readpage': : undefined reference to `zlib_inflateInit_' fs/fs.o(.text+0x351f4): In function `zisofs_readpage': : undefined reference to `zlib_inflate' fs/fs.o(.text+0x352a6): In function `zisofs_readpage': : undefined reference to `zlib_inflateEnd' fs/fs.o(.text.init+0xaac): In function `mnt_init': : undefined reference to `init_rootfs' fs/fs.o(.text.init+0xf31): In function `zisofs_init': : undefined reference to `zlib_inflate_workspacesize' make[1]: *** [kallsyms] Fout 1 make[1]: Weggaan uit map `/usr/src/linux-2.4.20-8' make: *** [vmlinux] Fout 2 <snip> This behaviour can be fixed by copying the configuration to ".config" first : "cd /usr/src/linux-2.4" "make clean" "make mrproper" "cp configs/kernel-2.4.20-athlon.config .config" "make xconfig" (choose 'save & exit') "make dep && make bzImage && make modules" This really looks like a bug to me. The reporter of this bug does nothing wrong. It's also probably a dupe of Red Hat Bugzilla # 75152.
make xconfig is flaky. A make oldconfig afterwards usually rights it too. This isn't something that's going to be fixed before EOL of RHL9
*** Bug 109160 has been marked as a duplicate of this bug. ***