Messages in this thread | | | From | Gerald Roth <> | Subject | 2.4.18-rc2-aa1 compilation failure | Date | Thu, 21 Feb 2002 01:30:51 +0100 |
| |
make[3]: Entering directory `/usr/src/linux/fs/reiserfs' make[3]: Circular /usr/src/linux/include/asm/pgalloc.h <- /usr/src/linux/include/linux/highmem.h dependency dropped. gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -DKBUILD_BASENAME=bitmap -c -o bitmap.o bitmap.c bitmap.c: In function `reiserfs_free_prealloc_block': bitmap.c:142: warning: unused variable `s' gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -DKBUILD_BASENAME=do_balan -c -o do_balan.o do_balan.c gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -DKBUILD_BASENAME=namei -c -o namei.o namei.c gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -DKBUILD_BASENAME=inode -c -o inode.o inode.c inode.c: In function `reiserfs_direct_io': inode.c:2097: `filp' undeclared (first use in this function) inode.c:2097: (Each undeclared identifier is reported only once inode.c:2097: for each function it appears in.) make[3]: *** [inode.o] Error 1 make[3]: Leaving directory `/usr/src/linux/fs/reiserfs' make[2]: *** [first_rule] Error 2 make[2]: Leaving directory `/usr/src/linux/fs/reiserfs' make[1]: *** [_subdir_reiserfs] Error 2 make[1]: Leaving directory `/usr/src/linux/fs' make: *** [_dir_fs] Error 2
hth gerald - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |