FS/XFS testing framework
 help / color / mirror / Atom feed
From: scameron@beardog.cce.hp.com
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org, scameron@beardog.cce.hp.com
Subject: Re: Problem building xfsprogs
Date: Wed, 23 Jul 2014 09:08:34 -0500	[thread overview]
Message-ID: <20140723140834.GJ14599@beardog.cce.hp.com> (raw)
In-Reply-To: <20140722215151.GO25291@thunk.org>

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?  

RHEL 6 update 5 on x86_64, which I would think is not considered
to be anything exotic.

[relliott@msablackburn include]$ cat /etc/*-release
LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Red Hat Enterprise Linux Server release 6.5 (Santiago)
Red Hat Enterprise Linux Server release 6.5 (Santiago)
[relliott@msablackburn include]$

But, I am not running the usual kernel, but this one

	git://git.infradead.org/users/hch/scsi.git

from this branch:

	remotes/origin/scsi-mq.4

with a ton of patches to the hpsa driver (not that xfsprogs should care about that.).

> 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.
> 
> It's also useful if you are running in a very restrictive run-time
> environment, such as what you might find in a highly opimized cloud
> data center, and you can't depend on any shared libraries, etc.  Or if
> you need to do a build for an embedded platform where again, you can't
> depend on anything getting provided by the distribution.
> 
> Anyway, give it a try and see if it helps,
> 
> 	git://git.kernel.org/pub/scm/fs/ext2/xfstests-bld.git
> 
> If you have any problems, let me know!

Thanks.  If other avenues don't work out it is something to try.

-- steve



      parent reply	other threads:[~2014-07-23 14:09 UTC|newest]

Thread overview: 16+ 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 21:09   ` scameron
2014-07-22 21:47     ` Dave Chinner
2014-07-23 14:01       ` scameron
2014-07-23 22:19         ` Dave Chinner
2014-07-22 21:50     ` Eric Sandeen
     [not found]   ` <CAK2EqxR93J8441Ajj8no7_Pu1WSDLaVsKG=_FLMYvTnOUEzKGQ@mail.gmail.com>
2014-07-22 21:18     ` Eric Sandeen
2014-07-22 21:20     ` scameron
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
2014-07-23  0:38         ` Theodore Ts'o
2014-07-23 14:08   ` scameron [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=20140723140834.GJ14599@beardog.cce.hp.com \
    --to=scameron@beardog.cce.hp.com \
    --cc=fstests@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox