From: Dave Chinner <david@fromorbit.com>
To: Martin Furuhjelm <martin.furuhjelm@seagate.com>
Cc: scameron@beardog.cce.hp.com, fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Problem building xfsprogs
Date: Wed, 23 Jul 2014 07:56:57 +1000 [thread overview]
Message-ID: <20140722215656.GQ4453@dastard> (raw)
In-Reply-To: <CAK2EqxR93J8441Ajj8no7_Pu1WSDLaVsKG=_FLMYvTnOUEzKGQ@mail.gmail.com>
On Tue, Jul 22, 2014 at 03:14:42PM -0600, Martin Furuhjelm wrote:
> I have just recently gone through the process of attempting to build and
> run xfstests based on the current sources from oss.sgi.com.
> Not having exactly the correct packages and kernel version creates
> problems. The build on FEDORA fails complaining about too many symlinks, I
> was successful on SUSE V 13 updated to kernel v3.15 and adding the
> following packages before attempting git and the build:
>
> git gcc libtool automake make gettext-tools libattr-devel libacl-devel
> libuuid-devel ncurses-devel quota indent libcap-progs btrfsprogs
>
> I then git and built xfsprogs followed by xfsdump and finally xfstests
>
> After adding the fsgqa group and user the appropriate definitions of
> TEST_DEV and SCRATCH_DEV the quick test (./check -g quick)
> runs with 5 errors on xfs and one error on ext4.
>
> If you just want xfstest to run - you may want to start with SUSE and the
> procedure above.
Perhaps it would be good to document that in the INSTALL file? Can
you write a patch to do that, please?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-07-22 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140722160641.GU17967@beardog.cce.hp.com>
2014-07-22 20:56 ` Problem building xfsprogs 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
2014-07-22 21:14 ` Martin Furuhjelm
2014-07-22 21:18 ` Eric Sandeen
2014-07-22 21:20 ` scameron
2014-07-22 21:56 ` Dave Chinner [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=20140722215656.GQ4453@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=martin.furuhjelm@seagate.com \
--cc=scameron@beardog.cce.hp.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