From: "Lee Trager" <lt73@cs.drexel.edu>
To: Michele Petrazzo <michele.petrazzo@unipex.it>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: compilation problem on last unstable
Date: Wed, 17 Dec 2008 13:14:47 -0500 [thread overview]
Message-ID: <20081217181447.GA2986@tux64-01> (raw)
In-Reply-To: <loom.20081217T174132-393@post.gmane.org>
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
prev parent reply other threads:[~2008-12-17 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 17:43 compilation problem on last unstable Michele Petrazzo
2008-12-17 18:14 ` Lee Trager [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081217181447.GA2986@tux64-01 \
--to=lt73@cs.drexel.edu \
--cc=linux-btrfs@vger.kernel.org \
--cc=michele.petrazzo@unipex.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox