From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: scameron@beardog.cce.hp.com, fstests@vger.kernel.org
Subject: Re: Problem building xfsprogs
Date: Wed, 23 Jul 2014 09:04:24 +1000 [thread overview]
Message-ID: <20140722230424.GS4453@dastard> (raw)
In-Reply-To: <20140722221950.GQ25291@thunk.org>
On Tue, Jul 22, 2014 at 06:19:51PM -0400, Theodore Ts'o wrote:
> On Wed, Jul 23, 2014 at 08:04:49AM +1000, Dave Chinner wrote:
> > On Tue, Jul 22, 2014 at 05:51:51PM -0400, Theodore Ts'o wrote:
> > > On Tue, Jul 22, 2014 at 11:06:41AM -0500, scameron@beardog.cce.hp.com wrote:
> > > >
> > > > I'm trying to build xfsprogs (in order to run xfstests), and I'm running into this:
> > >
> > > What distribution are you building on? I had a frustrating enough
> > > time getting it to build on Ubuntu and Debian systems a while back
> > > (not xfstests' fault; sometimes the distro doesn't ship all of the
> > > header files or have recent enough libraries) that I created
> > > xfstests-bld which does a hermetic build of xfstests. That way, it
> > > doesn't depend on anything getting shipped by the distribution.
> >
> > That doesn't help us triage or fix up the problems people have, Ted.
> > xfstests needs to run on lots of different distros - even ones that
> > are years old - and so we need to understand and fix these problems,
> > not work around them.
> >
> > Perhaps you could spend some time and send patches to document the
> > build/installation procedure that you use so we can improve the
> > process for everyone?
>
> Xfstests depends on external libraries which might not be there, or
> might be out of date.
Yup, that's why we have:
a) autoconf
b) _requires_* rules
c) output filters
So that xfstests works in as wide a range of environments as
possible. We've been doing this since xfstests was first created -
it even works on different OSes, not just different Linux distros...
> Or the xfsprogs might be out of date, or again,
> non-existent. Do you really want to try to make xfststs work in such
> an environment?
I didn't say that. I'm not sure how you made the leap from being
asked "can you document the build dependencies you needed to solve"
to "lets make xfstests run without any external dependencies". I'm
trying to get someone to document the build dependencies in the
INSTALL file, not trying to justify the existence of your xfstests
fork ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-07-22 23:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 16:06 Problem building xfsprogs scameron
2014-07-22 20:56 ` Dave Chinner
2014-07-22 20:56 ` Dave Chinner
2014-07-22 21:09 ` scameron
2014-07-22 21:09 ` scameron
2014-07-22 21:47 ` Dave Chinner
2014-07-22 21:47 ` Dave Chinner
2014-07-23 14:01 ` scameron
2014-07-23 14:01 ` scameron
2014-07-23 22:19 ` Dave Chinner
2014-07-23 22:19 ` Dave Chinner
2014-07-22 21:50 ` Eric Sandeen
2014-07-22 21:50 ` Eric Sandeen
2014-07-22 21:14 ` Martin Furuhjelm
2014-07-22 21:18 ` Eric Sandeen
2014-07-22 21:18 ` Eric Sandeen
2014-07-22 21:20 ` scameron
2014-07-22 21:20 ` scameron
2014-07-22 21:56 ` Dave Chinner
2014-07-22 21:56 ` Dave Chinner
2014-07-22 21:51 ` Theodore Ts'o
2014-07-22 22:04 ` Dave Chinner
2014-07-22 22:19 ` Theodore Ts'o
2014-07-22 23:04 ` Dave Chinner [this message]
2014-07-23 0:38 ` Theodore Ts'o
2014-07-23 14:08 ` scameron
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=20140722230424.GS4453@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=scameron@beardog.cce.hp.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.