From: Jim Rees <rees@umich.edu>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
peter honeyman <honey@citi.umich.edu>
Subject: Re: ANNOUNCE: nfs-utils-1.2.5 released.
Date: Mon, 26 Sep 2011 08:16:10 -0400 [thread overview]
Message-ID: <20110926121610.GA12412@umich.edu> (raw)
In-Reply-To: <4E8065C7.3060809@RedHat.com>
Steve Dickson wrote:
I'm not seeing this problem... I've run the configs on both F15 and F16
Try runing ./autogen.sh before running the ./configure script.
I did that and it didn't help. But it fixed itself after a few more tries
so I'm set now.
prev parent reply other threads:[~2011-09-26 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 12:55 ANNOUNCE: nfs-utils-1.2.5 released Steve Dickson
2011-09-25 5:10 ` Benny Halevy
2011-09-26 10:28 ` Steve Dickson
2011-09-25 8:39 ` NeilBrown
2011-09-25 14:13 ` Jim Rees
2011-09-26 10:40 ` Steve Dickson
2011-09-25 16:56 ` Jim Rees
2011-09-26 11:45 ` Steve Dickson
2011-09-26 12:16 ` Jim Rees [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=20110926121610.GA12412@umich.edu \
--to=rees@umich.edu \
--cc=SteveD@redhat.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).