Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Arun Bhanu <btrfs@arunbhanu.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Problem with building btrfs into the kernel instead of module
Date: Thu, 9 Oct 2008 01:41:13 +0800	[thread overview]
Message-ID: <20081008174113.GA6491@deepthought> (raw)
In-Reply-To: <Pine.LNX.4.64.0810071243090.31477@cobra.newdream.net>

* Sage Weil (sage@newdream.net) wrote:
> On Wed, 8 Oct 2008, Arun Bhanu wrote:
> > Hi
> > 
> > I have compiled btrfs into the kernel instead of building as module.
> > Then I create a btrfs filesystem on a partition and try to mount it and
> > I get the following error.
> 
> fs/btrfs/Makefile is a bit wonky.  This at least makes it work both ways:

Thanks. With your patch applied, it is working as expected in both
cases.

> diff --git a/fs/btrfs/Makefile b/fs/btrfs/Makefile
> index 48b7909..7125716 100644
> --- a/fs/btrfs/Makefile
> +++ b/fs/btrfs/Makefile
> @@ -1,7 +1,7 @@
>  ifneq ($(KERNELRELEASE),)
>  # kbuild part of makefile
>  
> -obj-m  := btrfs.o
> +obj-$(CONFIG_BTRFS_FS) := btrfs.o
>  btrfs-y := super.o ctree.o extent-tree.o print-tree.o root-tree.o 
> dir-item.o \
>            file-item.o inode-item.o inode-map.o disk-io.o \
>            transaction.o inode.o file.o tree-defrag.o \
> @@ -14,7 +14,7 @@ else
>  
>  KERNELDIR := /lib/modules/`uname -r`/build
>  all:
> -       $(MAKE) -C $(KERNELDIR) M=`pwd` modules
> +       $(MAKE) -C $(KERNELDIR) M=`pwd` CONFIG_BTRFS_FS=m modules
>  
>  modules_install:
>         $(MAKE) -C $(KERNELDIR) M=`pwd` modules_install
> 

-Arun

      reply	other threads:[~2008-10-08 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 18:22 Problem with building btrfs into the kernel instead of module Arun Bhanu
2008-10-07 19:44 ` Sage Weil
2008-10-08 17:41   ` Arun Bhanu [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=20081008174113.GA6491@deepthought \
    --to=btrfs@arunbhanu.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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