From: Eric Sandeen <sandeen@redhat.com>
To: Abhay Sachan <lkp.abhay@gmail.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs build fails for 4.8
Date: Wed, 12 Oct 2016 09:54:47 -0500 [thread overview]
Message-ID: <fa581ec0-b89b-fd5b-ffde-a4edb83e2ad8@redhat.com> (raw)
In-Reply-To: <CAKHchJwi-pEzaKkh72K-f+3ELA_H1VPiaoMGW7kgaHo_ZC3=4g@mail.gmail.com>
On 10/12/16 9:45 AM, Abhay Sachan wrote:
> Hi Qu,
> I am running latest 4.8.1, which I compiled on the machine itself.
You likely still have the fiemap.h from Centos' kernel-headers
rpm, which is from an older kernel and does not define it.
-Eric
> Linux vm88 4.8.1 #1 SMP Thu Oct 13 10:33:08 IST 2016 x86_64 x86_64
> x86_64 GNU/Linux
>
> Regards,
> Abhay
>
> On Wed, Oct 12, 2016 at 7:31 PM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>
>> On 10/12/2016 09:58 PM, Abhay Sachan wrote:
>>>
>>> Hi,
>>> I tried building latest btrfs progs on CentOS 6, "./configure" failed
>>> with the error:
>>>
>>> checking for FIEMAP_EXTENT_SHARED defined in linux/fiemap.h... no
>>> configure: error: no definition of FIEMAP_EXTENT_SHARED found
>>>
>>> Any ideas what am I lacking in the system?
>>
>>
>> Your kernel is too old and its header doesn't support FIEMAP_EXTENT_SHARED
>> flag for fiemap ioctl.
>>
>> And since that flag is very important for tools like "btrfs filesystem du",
>> for old kernel doesn't support EXTENT_SHARED flag, we have no choice but
>> abort configuration.
>>
>> Thanks,
>> Qu
>>
>>>
>>> Regards,
>>> Abhay
>>> --
>>> 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 prev parent reply other threads:[~2016-10-12 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 13:58 Btrfs progs build fails for 4.8 Abhay Sachan
2016-10-12 14:01 ` Qu Wenruo
2016-10-12 14:45 ` Abhay Sachan
2016-10-12 14:54 ` Eric Sandeen [this message]
2016-10-12 17:26 ` David Sterba
2016-10-13 7:25 ` Qu Wenruo
2016-10-14 15:49 ` David Sterba
2016-10-14 17:00 ` Eric Sandeen
2016-10-14 17:03 ` [PATCH] btrfs-progs: define FIEMAP_EXTENT_SHARED locally if needed Eric Sandeen
2016-10-14 17:08 ` Btrfs progs build fails for 4.8 David Sterba
2016-10-14 16:54 ` David Sterba
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=fa581ec0-b89b-fd5b-ffde-a4edb83e2ad8@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp.abhay@gmail.com \
--cc=quwenruo.btrfs@gmx.com \
/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).