From: Nathan Scott <nathans@debian.org>
To: Jose M Calhariz <jose@calhariz.com>
Cc: xfs@oss.sgi.com
Subject: Re: Problems compiling xfsdump on Debian unstable
Date: Sun, 1 Nov 2015 22:25:58 -0500 (EST) [thread overview]
Message-ID: <1847596501.219026.1446434758818.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <56362B71.4070709@calhariz.com>
Hi Jose,
----- Original Message -----
> I am trying to compile the latest xfsdump from the git repository.
The underlying problem was related to changes in xfsprogs header files
which had unanticipated dependencies in xfsdump - Dave has been working
through all these issues (iow, removing the unanticipated dependencies,
by updating xfsdump code) and the next release of xfsdump will resolve
this build failure. It's not a trivial change though, so our best bet
(IMO) is to wait on those upstream changes from Dave and then get a new
package build into unstable & testing.
cheers.
--
Nathan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-11-02 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 15:10 Problems compiling xfsdump on Debian unstable Jose M Calhariz
2015-11-01 22:34 ` Dave Chinner
2015-11-02 3:25 ` Nathan Scott [this message]
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=1847596501.219026.1446434758818.JavaMail.zimbra@redhat.com \
--to=nathans@debian.org \
--cc=jose@calhariz.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