xfs-sources kernel does not compile if "Processor type and features -> Symmetric multi-processing support" is disabled. In particular, /usr/src/linux- 2.4.18-xfs/kernel/ksyms.c gets a whole bunch of redefined symbols warnings all relating to CONFIG_SMP. Workaround: I just enabled SMP, even though I do not have a SMP system. Will this make the system run slower or unstably?
Hmmm, I would back up your /usr/src/linux/.config and then do: make mrproper cp /path/to/.config . make oldconfig make dep make bzImage and see if it works. Let me know either way.
This happened for me also during the initial installprocess 2 days ago. Enabling SMP made it work. No possibility to add XFS-support to gentoo-sources? :)
I found this out yesterday when doing a fresh 1.1 gcc3 build. I didnt try the smp thing. I just cleared out the source and reemerged xfs-sources. I thought it may have been a problem with needing kernel headers to compile everything, but them being different versions thatn whats in 2.4.18-xfs. That worked for me.
After doing a make mrproper, the kernel compiles. However, now when I do update- modules, I get errors from depmod: depmod: *** Unresolved symbols in /lib/modules/2.4.18- xfs/kernel/net/ipv4/netfilter/ip_conntrack.o depmod: *** Unresolved symbols in /lib/modules/2.4.18- xfs/kernel/net/ipv4/netfilter/ip_tables.o depmod: *** Unresolved symbols in /lib/modules/2.4.18- xfs/kernel/net/ipv4/netfilter/ipt_REJECT.o depmod: *** Unresolved symbols in /lib/modules/2.4.18- xfs/kernel/net/ipv4/netfilter/iptable_filter.o depmod: *** Unresolved symbols in /lib/modules/2.4.18- xfs/kernel/net/ipv4/netfilter/iptable_mangle.o depmod: *** Unresolved symbols in /lib/modules/2.4.18- xfs/kernel/net/ipv4/netfilter/iptable_nat.o I have 28 modules in that directory, but only those 6 fail. What does that mean? All of the files have the same timestamp, so they were created together. Is there anywhere I should look for garbage that needs to be deleted?
Noah -- I'm not sure why you're getting those unresolved symbols, but the XFS/SMP bug appears to be resolved so I'm closing this bug.