compilation problem on last unstable

compilation problem on last unstable

[Michele Petrazzo]

Hi,
I just tried to compile the last unstable version, but:

  CC [M]  /home/michele/btrfs-unstable-standalone/inode.o
/home/michele/btrfs-unstable-standalone/inode.c: In function =E2=80=98b=
trfs_new_inode=E2=80=99:
/home/michele/btrfs-unstable-standalone/inode.c:3470: error: implicit
declaration of function =E2=80=98current_fsuid=E2=80=99
/home/michele/btrfs-unstable-standalone/inode.c:3471: error: implicit
declaration of function =E2=80=98current_fsgid=E2=80=99
/home/michele/btrfs-unstable-standalone/inode.c: In function=20
=E2=80=98btrfs_cache_create=E2=80=99:
/home/michele/btrfs-unstable-standalone/inode.c:4527: warning: passing =
argument
5 of =E2=80=98kmem_cache_create=E2=80=99 from incompatible pointer type
/home/michele/btrfs-unstable-standalone/inode.c: At top level:
/home/michele/btrfs-unstable-standalone/inode.c:4966: warning: initiali=
zation
from incompatible pointer type
/home/michele/btrfs-unstable-standalone/inode.c:4970: warning: initiali=
zation
from incompatible pointer type
/home/michele/btrfs-unstable-standalone/inode.c:5024: warning: initiali=
zation
from incompatible pointer type
/home/michele/btrfs-unstable-standalone/inode.c:5030: warning: initiali=
zation
from incompatible pointer type
/home/michele/btrfs-unstable-standalone/inode.c:5040: warning: initiali=
zation
from incompatible pointer type
make[2]: *** [/home/michele/btrfs-unstable-standalone/inode.o] Error 1
make[1]: *** [_module_/home/michele/btrfs-unstable-standalone] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make: *** [all] Error 2
michele:~/btrfs-unstable-standalone$=20


michele:~/btrfs-unstable-standalone$ uname -r
2.6.26-1-686

from debian=20

Thanks,
Michele

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: compilation problem on last unstable

[Lee Trager]

On Wed, Dec 17, 2008 at 05:43:50PM +0000, Michele Petrazzo wrote:
> Hi,
> I just tried to compile the last unstable version, but:
> 
>   CC [M]  /home/michele/btrfs-unstable-standalone/inode.o
> /home/michele/btrfs-unstable-standalone/inode.c: In function ???btrfs_new_inode???:
> /home/michele/btrfs-unstable-standalone/inode.c:3470: error: implicit
> declaration of function ???current_fsuid???
> /home/michele/btrfs-unstable-standalone/inode.c:3471: error: implicit
> declaration of function ???current_fsgid???
> /home/michele/btrfs-unstable-standalone/inode.c: In function 
> ???btrfs_cache_create???:
> /home/michele/btrfs-unstable-standalone/inode.c:4527: warning: passing argument
> 5 of ???kmem_cache_create??? from incompatible pointer type
> /home/michele/btrfs-unstable-standalone/inode.c: At top level:
> /home/michele/btrfs-unstable-standalone/inode.c:4966: warning: initialization
> from incompatible pointer type
> /home/michele/btrfs-unstable-standalone/inode.c:4970: warning: initialization
> from incompatible pointer type
> /home/michele/btrfs-unstable-standalone/inode.c:5024: warning: initialization
> from incompatible pointer type
> /home/michele/btrfs-unstable-standalone/inode.c:5030: warning: initialization
> from incompatible pointer type
> /home/michele/btrfs-unstable-standalone/inode.c:5040: warning: initialization
> from incompatible pointer type
> make[2]: *** [/home/michele/btrfs-unstable-standalone/inode.o] Error 1
> make[1]: *** [_module_/home/michele/btrfs-unstable-standalone] Error 2
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
> make: *** [all] Error 2
> michele:~/btrfs-unstable-standalone$ 
> 
> 
> michele:~/btrfs-unstable-standalone$ uname -r
> 2.6.26-1-686
> 
> from debian 
Currently btrfs only compiles on 2.6.27 and above although support all
the way back to 2.6.18 is planned. I'm currently using Ubuntu 8.10 for
all btrfs testing.
> 
> Thanks,
> Michele
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html