From: Chuck Lever <chuck.lever@oracle.com>
To: nfs@lists.sourceforge.net
Subject: wonky autotools question
Date: Fri, 27 Jul 2007 15:48:06 -0400 [thread overview]
Message-ID: <46AA4BF6.6090002@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 412 bytes --]
Hi all-
It would be nice to enable more static code checking in nfs-utils (I'm
especially interested in utils/mount/). Is there a clean way to add
additional CFLAGS, like -Wall, to utils/mount/Makefile using the
autotools set up? How about a lint or sparse target?
I'm not just interested in autotools foo, but also in knowing how the
nfs-utils maintainers prefer this sort of thing to be done. Thanks!
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 259 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-07-27 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 19:48 Chuck Lever [this message]
2007-07-27 20:08 ` wonky autotools question 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
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=46AA4BF6.6090002@oracle.com \
--to=chuck.lever@oracle.com \
--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 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.