public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: robert herndon <rherndon@sgi.com>
Cc: robert herndon <rherndon@elm.eagan>, xfs@oss.sgi.com
Subject: Re: [PATCH] Update xfstests' README to document method/necessity
Date: Tue, 02 Jun 2009 14:48:06 -0500	[thread overview]
Message-ID: <4A2581F6.8070705@sandeen.net> (raw)
In-Reply-To: <1243970604-13732-1-git-send-email-rherndon@attica.americas.sgi.com>

robert herndon wrote:
> From: robert herndon <rherndon@elm.eagan>
> 
> ---
>  README |   11 +++++++++++
>  1 files changed, 11 insertions(+), 0 deletions(-)
> 
> diff --git a/README b/README
> index 375e07c..f9725b4 100644
> --- a/README
> +++ b/README
> @@ -18,6 +18,17 @@ Preparing system for tests (IRIX and Linux):
>  
>      - compile XFS into your kernel or load XFS modules
>      - install user tools including mkfs.xfs, xfs_db & xfs_bmap
> +    - install header files required to build xfstests' programs:
> +
> +           # cd <...>/xfsprogs
> +           # make install-qa

With any luck, this will be going away soon, actually.

It's only required for loggen, and we're looking for ways around that.
See for example [PATCH, RFC] xfsprogs: add xfs_loggen and/or [PATCH 1/9
V2] Use xfs.h rather than libxfs.h on the list.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-06-02 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 19:23 [PATCH] Update xfstests' README to document method/necessity robert herndon
2009-06-02 19:48 ` Eric Sandeen [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=4A2581F6.8070705@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=rherndon@elm.eagan \
    --cc=rherndon@sgi.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