[BUG] Linux-2.6.33.3-rt19 Compile Error With PohmelFS

From: Tarkan Erimer
Date: Mon May 03 2010 - 05:50:40 EST



This is an openSUSE 11.3 Milestone 6 with GCC-4.5. When I tried to compile, I
got the following error message related to inode.c.

Tarkan

CC drivers/staging/staging.o
LD drivers/staging/built-in.o
LD drivers/staging/pohmelfs/built-in.o
CC [M] drivers/staging/pohmelfs/inode.o
drivers/staging/pohmelfs/inode.c: In function âpohmelfs_put_superâ:
drivers/staging/pohmelfs/inode.c:1293:3: warning: passing argument 1 of
âatomic_readâ from incompatible pointer type
/usr/src/linux-2.6.33.3/arch/x86/include/asm/atomic_64.h:21:19: note: expected
âconst struct atomic_t *â but argument is of type âunsigned int *â
drivers/staging/pohmelfs/inode.c:1296:6: warning: passing argument 1 of
âatomic_readâ from incompatible pointer type
/usr/src/linux-2.6.33.3/arch/x86/include/asm/atomic_64.h:21:19: note: expected
âconst struct atomic_t *â but argument is of type âunsigned int *â
drivers/staging/pohmelfs/inode.c:1297:4: warning: passing argument 1 of
âatomic_readâ from incompatible pointer type
/usr/src/linux-2.6.33.3/arch/x86/include/asm/atomic_64.h:21:19: note: expected
âconst struct atomic_t *â but argument is of type âunsigned int *â
drivers/staging/pohmelfs/inode.c:1305:2: error: request for member ânextâ in
something not a structure or union
drivers/staging/pohmelfs/inode.c:1305:2: warning: comparison of distinct
pointer types lacks a cast
drivers/staging/pohmelfs/inode.c:1317:3: warning: passing argument 1 of
âatomic_readâ from incompatible pointer type
/usr/src/linux-2.6.33.3/arch/x86/include/asm/atomic_64.h:21:19: note: expected
âconst struct atomic_t *â but argument is of type âunsigned int *â
make[5]: *** [drivers/staging/pohmelfs/inode.o] Error 1
make[4]: *** [drivers/staging/pohmelfs] Error 2
make[3]: *** [drivers/staging] Error 2
make[2]: *** [drivers] Error 2
make[1]: *** [binrpm-pkg] Error 2
make: *** [binrpm-pkg] Error 2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/