From: Theodore Ts'o <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: scameron@beardog.cce.hp.com, fstests@vger.kernel.org
Subject: Re: Problem building xfsprogs
Date: Tue, 22 Jul 2014 18:19:51 -0400 [thread overview]
Message-ID: <20140722221950.GQ25291@thunk.org> (raw)
In-Reply-To: <20140722220449.GR4453@dastard>
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. 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?
The only solution would be to either try to radically restrict which
tests run if various bits of infrastructure which xfstests depends on
aren't there (which means you don't get as much testing done, which is
certainly non-ideal), or you need to be willing to (optionally) build
various libaries and other support programs as part of the xfstests
build.
I didn't bother sending patches that would do any of this, because I
assumed they would have been rejected with extreme prejudice. Was I
wrong?
Are you really interested in making xfstests not depend on *anything*
(not xfsprogs, not the aio, acl, xattr, or quota library, etc., etc)
being available in its build-time and run-time environment? Because
that's the problem I needed to solve.
Cheers,
- Ted
next prev parent reply other threads:[~2014-07-22 22:22 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 [this message]
2014-07-22 23:04 ` Dave Chinner
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=20140722221950.GQ25291@thunk.org \
--to=tytso@mit.edu \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=scameron@beardog.cce.hp.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 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.