From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-fsdevel@vger.kernel.org
Cc: miklos@szeredi.hu, akpm <akpm@osdl.org>
Subject: [PATCH] FUSE depends on BLOCK
Date: Thu, 16 Nov 2006 21:38:06 -0800 [thread overview]
Message-ID: <20061116213806.4b11c49b.randy.dunlap@oracle.com> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
Should FUSE depend on BLOCK? Without that and with BLOCK=n, I get:
inode.c:(.text+0x3acc5): undefined reference to `sb_set_blocksize'
inode.c:(.text+0x3a393): undefined reference to `get_sb_bdev'
fs/built-in.o:(.data+0xd718): undefined reference to `kill_block_super
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
fs/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-2619-rc5mm2.orig/fs/Kconfig
+++ linux-2619-rc5mm2/fs/Kconfig
@@ -622,6 +622,7 @@ config AUTOFS4_FS
config FUSE_FS
tristate "Filesystem in Userspace support"
+ depends on BLOCK
help
With FUSE it is possible to implement a fully functional filesystem
in a userspace program.
---
reply other threads:[~2006-11-17 5:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061116213806.4b11c49b.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).