Linux NFS development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Andreas Radke <andreas.radke@mailbox.org>,
	Steve Dickson <SteveD@RedHat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: ANNOUNCE: nfs-utils-2.3.1 released.
Date: Thu, 04 Jan 2018 16:11:19 +1100	[thread overview]
Message-ID: <87a7xudx8o.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20171221212516.031618d8@laptop64.home>

[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]

On Thu, Dec 21 2017, Andreas Radke wrote:

> This new version fails make check here now:
>
> nsm_client.c:147:12: warning: this statement may fall through [-Wimplicit-fallthrough=]
>     my_prog = atoi(optarg);
>     ~~~~~~~~^~~~~~~~~~~~~~
> nsm_client.c:148:3: note: here
>    case 'v':
>    ^~~~

What do you think Jeff, you introduced this code 8 years ago and this
switch statement has always been broken.
Does anyone use this code?  Should we fix it, it just remove it?



> make[4]: *** No rule to make target '../../support/nfs/libnfs.a',
> needed by 'nsm_client'.

This looks like a bug in automake???  ../../support/nfs/libnfs.a is
listed as _LDADD

https://www.gnu.org/software/automake/manual/html_node/Program-and-Library-Variables.html#index-maude_005fAR

which should add it to the 'ld' command, but I don't see that it should
be added as a dependency.

> make[4]: Target 'nsm_client' not remade because of errors.
> make[3]: *** [Makefile:565: check-am] Error 2
> make[2]: *** [Makefile:567: check] Error 2
> statdb_dump.c: In function ‘dump_host’:
> statdb_dump.c:38:17: warning: unused parameter ‘timestamp’ [-Wunused-parameter]
>     const time_t timestamp)
>                  ^~~~~~~~~

This arg has to be there because it is part of an external API.
As the function is passed as an arg to an extern function, gcc could
deduce that the signature cannot be changed just because the arg isn't
needed.


> statdb_dump.c: In function ‘main’:
> statdb_dump.c:91:10: warning: unused parameter ‘argc’ [-Wunused-parameter]
>  main(int argc, char **argv)
>           ^~~~

This arg doesn't need to be used (obviously) but cannot be removed.
So this is a dumb warning too.

Maybe we should add __attribute__((unused)) ??

> make[3]: *** No rule to make target '../support/nfs/libnfs.a', needed by 'statdb_dump'.
> make[3]: Target 'statdb_dump' not remade because of errors.
> make[2]: *** [Makefile:1028: check-am] Error 2
> make[1]: *** [Makefile:717: check-recursive] Error 1
> make[1]: Target 'check' not remade because of errors.
>

I assume you get these errors by running "make check" without first
running "make"??
If you run "make" first, the errors go away, and you are left with the
warnings.

Maybe they are worth fixing .... let's see what Jeff thinks.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-01-04  5:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 16:49 ANNOUNCE: nfs-utils-2.3.1 released Steve Dickson
2017-12-21 20:25 ` Andreas Radke
2018-01-04  5:11   ` NeilBrown [this message]
2018-01-04 13:59     ` Jeff Layton
2018-01-04 20:37       ` Steve Dickson
2018-01-05 12:11         ` Jeff Layton
2018-01-04 20:35     ` Steve Dickson

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=87a7xudx8o.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=SteveD@RedHat.com \
    --cc=andreas.radke@mailbox.org \
    --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