From: Rich Johnston <rjohnston@sgi.com>
To: Boris Ranto <ranto.boris@gmail.com>
Cc: Boris Ranto <branto@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 2/5] xfstests: Use libtool to install applications
Date: Wed, 17 Apr 2013 09:51:15 -0500 [thread overview]
Message-ID: <516EB6E3.9040903@sgi.com> (raw)
In-Reply-To: <CAFZPdfgFjRS2rFUekfSr4dT+-sfuji-0uUo1i7VE6=9GZOnzfg@mail.gmail.com>
Boris,
Most people do not install xfstests, as it is not required to run the
tests. Is there a reason you need to install xfstests? It is designed
to be run from the directory you did the git clone from. Path is not
critical so you could move it anywhere you wish.
i.e.
git clone git://oss.sgi.com/xfs/cmds/xfstests
mv xfstests /new/path/new_xfsdirname
cd /new/path/new_xfsdirname
./check -g auto
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-17 14:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 17:26 [PATCH 0/5] Use libtool to install apps and remove relative lib paths Rich Johnston
2012-08-28 17:26 ` [PATCH 1/5] xfstests: Use libtool to install lstat64 Rich Johnston
2012-09-03 5:31 ` Dave Chinner
2012-08-28 17:26 ` [PATCH 2/5] xfstests: Use libtool to install applications Rich Johnston
2012-09-03 5:36 ` Dave Chinner
2013-04-16 15:54 ` Boris Ranto
2013-04-17 14:51 ` Rich Johnston [this message]
2013-04-17 15:56 ` Eric Sandeen
2013-04-18 12:25 ` Boris Ranto
2013-04-18 12:46 ` Greg Freemyer
2013-04-18 13:37 ` Boris Ranto
2012-08-28 17:26 ` [PATCH 3/5] xftests: Use installed libraries only Rich Johnston
2012-09-03 5:37 ` Dave Chinner
2012-08-28 17:26 ` [PATCH 4/5] dmapi: " Rich Johnston
2012-09-03 5:38 ` Dave Chinner
2012-08-28 17:26 ` [PATCH 5/5] xfsdump: " Rich Johnston
2012-09-03 5:39 ` Dave Chinner
2012-09-04 16:07 ` [PATCH 0/5] Use libtool to install apps and remove relative lib paths Ben Myers
2012-09-06 18:43 ` Rich Johnston
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=516EB6E3.9040903@sgi.com \
--to=rjohnston@sgi.com \
--cc=branto@redhat.com \
--cc=ranto.boris@gmail.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