From: Steve French <smfrench@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
fstests@vger.kernel.org
Subject: Re: xfstests and ext4
Date: Mon, 17 Nov 2014 20:35:39 -0600 [thread overview]
Message-ID: <CAH2r5mti8hVXqmKu9kJg4Xk=5nkESCAQys1BFXhR6JSDVHOTEA@mail.gmail.com> (raw)
In-Reply-To: <20141117203804.GO23575@dastard>
On Mon, Nov 17, 2014 at 2:38 PM, Dave Chinner <david@fromorbit.com> wrote:
> the other as a base64 encoded attachment so can't be quoted and
> replied to easily. In future, can you send patches as separate
> emails according to:
Yes. WIll do. It is a pain in test VMs to setup git with gmail two
phase authentication
but doable if I set it up to send mail from a different host.
>> Building Linux:
>> - cd into the xfstests directory
>> + - install prerequisite packages
>> + For example, for Ubuntu:
>> + "sudo apt-get install xfslibs-dev uuid-dev libtool e2fsprogs
>> + automake gcc libuuid1 libuuidm-ocaml-dev attr libattr1-dev
> ^^^^^^^^^^^^^^^^^^
>
> What in xfstests is dependent on ocaml?
That libuuidm-ocaml-dev looks unneeded now (I ended up pulling in one
of the tools a different
way so whatever that pulled in looks superfluous now) - in an earlier
try at this I built a few
of the tools. But there is one missing. I missed in the cut-and-pastes
an obvious very
important dependency when I was transcribing the dependency list -
"quota" I will add
that to the list and remove the libuuidm-ocaml-dev off now that I have
confirmed the dependencies
list again today on a fresh Ubuntu install.
--
Thanks,
Steve
next prev parent reply other threads:[~2014-11-18 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 23:38 xfstests and ext4 Steve French
2014-11-14 0:02 ` Dave Chinner
2014-11-14 1:20 ` Steve French
2014-11-17 20:38 ` Dave Chinner
2014-11-18 2:35 ` Steve French [this message]
2014-11-18 20:28 ` Dave Chinner
2014-11-19 19:07 ` Christoph Hellwig
2014-11-19 20:02 ` Theodore Ts'o
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='CAH2r5mti8hVXqmKu9kJg4Xk=5nkESCAQys1BFXhR6JSDVHOTEA@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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.