make bzImage fails with the following... kernel/kernel.o(.kstrtab+0xcd5): multiple definition of `__kstrtab_kmap_pte' arch/i386/kernel/kernel.o(.kstrtab+0x8ba): first defined here kernel/kernel.o(__ksymtab+0x2c8): multiple definition of `__ksymtab_kmap_prot' arch/i386/kernel/kernel.o(__ksymtab+0x238): first defined here kernel/kernel.o(__ksymtab+0x2d0): multiple definition of `__ksymtab_kmap_pte' arch/i386/kernel/kernel.o(__ksymtab+0x240): first defined here kernel/kernel.o(.kstrtab+0xcbd): multiple definition of `__kstrtab_kmap_prot' arch/i386/kernel/kernel.o(.kstrtab+0x8a2): first defined here make: *** [vmlinux] Error 1
Created attachment 3659 [details] .config file for failed build
did you have "USE=crypto" set when you merged the kernel? (USE=crypto adds an additional 3 patches for encrypted filesystems to the kernel)
problem located. Highmem support appears to be the culprit, I assume that you have over >=1gb of ram since you had highmem turned on. I am investigating a fix for this and will add it as soon as possible to either a lolo-sources or another gentoo-sources release.
A temporary fix for your system is to use the features of the 3.5GB address space patch and turn off highmem but set the User Addressable Space to 2GB, what this will do is allow the kernel to address 2GB of memory but only allow any single userland process to malloc() up to 2GB of memory instead of the standard 1GB of kernel memory and up to 3GB/process split. As long as you don't have any rendering programs or the like that will try to use > 2GB of memory, I recommend this so that you can see the other benefits of the gentoo- linux kernel immediatly rather than waiting for a fix from me.
Yes, I have 1GB of mem. Your suggested workaround works for me. Thanks.
fixed, added patch, remerging gentoo-sources should solve this... but using the different split rather than the highmem support is higher performance.
