From: Jeff Mahoney <jeffm@suse.com>
To: Steven Haigh <netwiz@crc.id.au>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs 4.6 won't build on CentOS6
Date: Thu, 23 Jun 2016 21:58:31 -0400 [thread overview]
Message-ID: <576C93C7.3030605@suse.com> (raw)
In-Reply-To: <3864856543476b0f69224f6b6be3ed26@crc.id.au>
[-- Attachment #1.1: Type: text/plain, Size: 1004 bytes --]
On 6/23/16 9:49 PM, Steven Haigh wrote:
> I've tried to build the new tools for CentOS 6 / Scientific Linux 6 /
> RHEL 6 etc.
>
> During the build process, I see:
> cmds-fi-du.c: In function 'du_calc_file_space':
> cmds-fi-du.c:330: error: 'FIEMAP_EXTENT_SHARED' undeclared (first use in
> this function)
> cmds-fi-du.c:330: error: (Each undeclared identifier is reported only once
> cmds-fi-du.c:330: error: for each function it appears in.)
> make: *** [cmds-fi-du.o] Error 1
>
> I'm guessing this is probably due to a different GCC version used? I'm
> guessing this is a simple fix for someone with knowhow... :)
>
This is due to too-old headers. That define was added in 2.6.33.
#define FIEMAP_EXTENT_SHARED 0x00002000 /* Space shared with other
* files. */
Just add that above that routine and you'll be good to go. The right fix
is to add it to the tools, ofc.
-Jeff
--
Jeff Mahoney
SUSE Labs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2016-06-24 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 1:49 btrfs-progs 4.6 won't build on CentOS6 Steven Haigh
2016-06-24 1:58 ` Jeff Mahoney [this message]
2016-06-24 3:22 ` Eric Sandeen
2016-06-24 3:26 ` Qu Wenruo
2016-06-24 3:28 ` Steven Haigh
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=576C93C7.3030605@suse.com \
--to=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=netwiz@crc.id.au \
/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).