On 02/15/2011 11:35 PM, Yuri D'Elia wrote:
> 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 fix 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 
> ‘btrfs_issue_discard’:
> /var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: ‘BLKDEV_IFL_WAIT’ 
> undeclared (first use in this function)
> /var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: (Each undeclared 
> identifier is reported only once
> /var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: for each function it 
> appears in.)
> /var/lib/dkms/btrfs/git/build/extent-tree.c:1747: error: ‘BLKDEV_IFL_BARRIER’ 
> 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?

in commit fbd9b09a177a481eda256447c881f014f29034fe:
include/linux/blkdev.h:

#define BLKDEV_IFL_WAIT         (1 << BLKDEV_WAIT)
#define BLKDEV_IFL_BARRIER      (1 << BLKDEV_BARRIER)
#define BLKDEV_IFL_SECURE       (1 << BLKDEV_SECURE)

Maybe this is helpful.:)

thanks,
liubo

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

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

Reply via email to