From: Steve Dickson <SteveD@RedHat.com>
To: Yang Bo <phoooyb@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] nfs-utils: configure.ac: Do not fatalize -Wstrict-prototypes with internal rpcgen.
Date: Thu, 29 Nov 2018 15:01:24 -0500 [thread overview]
Message-ID: <cb0346c2-3550-b93c-a74c-4ec4b2579aab@RedHat.com> (raw)
In-Reply-To: <5be14884.1c69fb81.a6fae.51d4@mx.google.com>
On 11/6/18 2:53 AM, Yang Bo wrote:
> The internal rpcgen is not able to generate -Wstrict-prototypes free code,
> the problematic files are:
>
> ./tests/nsm_client/nlm_sm_inter_svc.c
> ./support/nsm/sm_inter_svc.c
>
> Signed-off-by: Yang Bo <rslovers@yandex.com>
Committed....
steved.
> ---
> configure.ac | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/configure.ac b/configure.ac
> index 3caeebc..ad2985c 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -149,6 +149,7 @@ AC_ARG_WITH(rpcgen,
> [AC_HELP_STRING([--with-rpcgen=internal], [use internal rpcgen instead of system one])],
> rpcgen_path=$withval,
> rpcgen_path=yes )
> + rpcgen_cflags=-Werror=strict-prototypes
> RPCGEN_PATH=
> if test "$rpcgen_path" = "yes"; then
> for p in /usr/local/bin/rpcgen /usr/bin/rpcgen /bin/rpcgen
> @@ -157,6 +158,7 @@ AC_ARG_WITH(rpcgen,
> RPCGEN_PATH=$rpcgen_path
> else
> RPCGEN_PATH=internal
> + rpcgen_cflags=-Wstrict-prototypes
> fi
> AC_SUBST(RPCGEN_PATH)
> AM_CONDITIONAL(CONFIG_RPCGEN, [test "$RPCGEN_PATH" = "internal"])
> @@ -542,7 +544,7 @@ my_am_cflags="\
> -pipe \
> -Wall \
> -Wextra \
> - -Werror=strict-prototypes \
> + $rpcgen_cflags \
> -Werror=missing-prototypes \
> -Werror=missing-declarations \
> -Werror=format=2 \
>
prev parent reply other threads:[~2018-11-29 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 7:53 [PATCH 2/2] nfs-utils: configure.ac: Do not fatalize -Wstrict-prototypes with internal rpcgen Yang Bo
2018-11-29 20:01 ` Steve Dickson [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=cb0346c2-3550-b93c-a74c-4ec4b2579aab@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=phoooyb@gmail.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