On Sat, May 03, 2008 at 10:00:09AM +0200, Christian T. Steigies wrote:
- ext4 does not seem to compile: [...] m68k-linux-gnu-strip vmlinux.tmp gzip -9c vmlinux.tmp >vmlinux.gz rm vmlinux.tmp Building modules, stage 2. MODPOST 468 modules ERROR: "generic_find_next_le_bit" [fs/ext4/ext4dev.ko] undefined! ERROR: "m68k_mmutype" [drivers/uio/uio.ko] undefined! WARNING: modpost: Found 2 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' Is ext4 supposed to work on m68k? Would anybody mind if I disable it for debian-m68k? I would not want to use ext4 on my other machines yet, so thats what I am going to try next.
And with EXT4DEV_FS disabled, I get this: MODPOST vmlinux.o WARNING: modpost: Found 1 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 KSYM .tmp_kallsyms1.S AS .tmp_kallsyms1.o LD .tmp_vmlinux2 KSYM .tmp_kallsyms2.S AS .tmp_kallsyms2.o LD vmlinux SYSMAP System.map SYSMAP .tmp_System.map cp vmlinux vmlinux.tmp m68k-linux-gnu-strip vmlinux.tmp gzip -9c vmlinux.tmp >vmlinux.gz rm vmlinux.tmp Building modules, stage 2. MODPOST 466 modules ERROR: "m68k_mmutype" [drivers/uio/uio.ko] undefined! Hmm? Christian -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
