From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfsdump: fix build issues
Date: Tue, 15 Jul 2014 15:45:04 +1000 [thread overview]
Message-ID: <1405403106-3084-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
it's clearly been a while since I built xfsdump, because it didn't
compile in my current dev environment. These patches are needed to
make it compile again. Once there are reviewed and merged, I'll do a
point release for the xfsdump package....
I also noticed that 'make deb' issues a huge number of
set-but-not-used variable warnings, which means that the debian
package is building with different compiler flags to the normal
build. We should fix that at some point.
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-07-15 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 5:45 Dave Chinner [this message]
2014-07-15 5:45 ` [PATCH 1/2] dump: don't redefine min() or max() Dave Chinner
2014-07-15 10:20 ` Christoph Hellwig
2014-07-15 5:45 ` [PATCH 2/2] dump: fix translation build errors Dave Chinner
2014-07-15 10:21 ` Christoph Hellwig
2014-07-15 14:55 ` Jakub Bogusz
2014-07-15 15:40 ` Christoph Hellwig
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=1405403106-3084-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.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