From: Dave Chinner <david@fromorbit.com>
To: Martin Michlmayr <tbm@hpe.com>, 822369@bugs.debian.org
Cc: submit@bugs.debian.org
Subject: Bug#822369: xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
Date: Tue, 26 Apr 2016 08:14:03 +1000 [thread overview]
Message-ID: <20160425221403.GB18496@dastard> (raw)
In-Reply-To: <20160423210831.GA19384@jirafa.cyrius.com>
On Sat, Apr 23, 2016 at 02:08:31PM -0700, Martin Michlmayr wrote:
> Package: xfsprogs
> Version: 4.3.0+nmu1
> Severity: serious
>
> This package fails to build in unstable:
>
> > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
> ...
> > [CC] fiemap.o
> > In file included from ../include/xfs.h:58:0,
> > from io.h:19,
> > from fiemap.c:24:
> > ../include/xfs/xfs_fs.h:42:8: error: redefinition of 'struct fsxattr'
> > struct fsxattr {
> > ^
> > In file included from fiemap.c:22:0:
> > /usr/include/linux/fs.h:155:8: note: originally defined here
> > struct fsxattr {
> > ^
> > ../include/buildrules:59: recipe for target 'fiemap.o' failed
> > make[3]: *** [fiemap.o] Error 1
> > include/buildrules:35: recipe for target 'io' failed
Kernel uapi change in 4.5 caused it. Upgrade to xfsprogs 4.5.0.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-25 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160423205226.67773120316@dl580gen9-02.hlinux>
2016-04-23 21:08 ` Bug#822369: xfsprogs: FTBFS: error: redefinition of 'struct fsxattr' Martin Michlmayr
2016-04-25 22:14 ` Dave Chinner [this message]
2017-01-15 18:15 ` Bug#822369: marked as done (xfsprogs: FTBFS: error: redefinition of 'struct fsxattr') Debian Bug Tracking System
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=20160425221403.GB18496@dastard \
--to=david@fromorbit.com \
--cc=822369@bugs.debian.org \
--cc=submit@bugs.debian.org \
--cc=tbm@hpe.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).