From: Neil Brown <neilb@suse.de>
To: chuck.lever@oracle.com
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Garrick Staples <garrick@usc.edu>,
nfs@lists.sourceforge.net
Subject: Re: wonky autotools question
Date: Sat, 28 Jul 2007 08:31:57 +1000 [thread overview]
Message-ID: <18090.29277.10351.295141@notabene.brown> (raw)
In-Reply-To: message from Chuck Lever on Friday July 27
On Friday July 27, chuck.lever@oracle.com wrote:
>
> Though really, it does make sense to set -Wall for the whole package.
> Would anyone mind if I sent a patch that did that?
I'd be keen on
-Wall -Werror -Wstrict-prototypes
though I suspect we need a lot of cleanup before all of those can
pass, and we -Werror would have to be conditional on using the
internal rpcgen as the libc one generates code that produced warning.
I guess I really should try pushing those rpcgen fixes upstream to
glibc...
NeilBrown
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-07-27 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 19:48 wonky autotools question Chuck Lever
2007-07-27 20:08 ` J. Bruce Fields
2007-07-27 20:17 ` Chuck Lever
2007-07-27 20:29 ` Garrick Staples
2007-07-27 21:41 ` Chuck Lever
2007-07-27 22:31 ` Neil Brown [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=18090.29277.10351.295141@notabene.brown \
--to=neilb@suse.de \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=garrick@usc.edu \
--cc=nfs@lists.sourceforge.net \
/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