From: Yuri D'Elia <wavexx@users.sf.net>
To: linux-btrfs@vger.kernel.org
Subject: Building btrfs as a dkms module on Debian
Date: Tue, 15 Feb 2011 16:35:19 +0100 [thread overview]
Message-ID: <20110215163519.d9c7f40f.wavexx@users.sf.net> (raw)
Hi everyone. I was trying to test a more recent version of btrfs on my =
current kernel (2.6.37) using dkms, without success.
I followed these instructions:
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories
- cloned the repo
- symlinked to /usr/src/btrfs-git
- patched version.sh:
Please note version.sh requires bash (better to change the shebang or f=
ix the script).
Even with the patch, version.sh run on a shallow repository generates a=
"-dirty" version. I assume this is OK, even though there are no local =
changes.
- run version.sh
- dkms add -m btrfs -v git
- dkms build -m btrfs -v git fails with:
/var/lib/dkms/btrfs/git/build/extent-tree.c: In function =E2=80=98btrfs=
_issue_discard=E2=80=99:
/var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: =E2=80=98BLKDE=
V_IFL_WAIT=E2=80=99 undeclared (first use in this function)
/var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: (Each undeclar=
ed identifier is reported only once
/var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: for each funct=
ion it appears in.)
/var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: =E2=80=98BLKDE=
V_IFL_BARRIER=E2=80=99 undeclared (first use in this function)
I assume BLKDEV_IFL_WAIT/BARRIER was added in later kernels?
Is there a way to make it build btrfs for 2.6.37?
Thanks
--
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
next reply other threads:[~2011-02-15 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 15:35 Yuri D'Elia [this message]
2011-02-16 2:51 ` Building btrfs as a dkms module on Debian liubo
2011-02-16 17:44 ` Yuri D'Elia
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=20110215163519.d9c7f40f.wavexx@users.sf.net \
--to=wavexx@users.sf.net \
--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;
as well as URLs for NNTP newsgroup(s).