From: Andreas Radke <andreas.radke@mailbox.org>
To: Steve Dickson <SteveD@RedHat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: ANNOUNCE: nfs-utils-2.3.1 released.
Date: Thu, 21 Dec 2017 21:25:16 +0100 [thread overview]
Message-ID: <20171221212516.031618d8@laptop64.home> (raw)
In-Reply-To: <1a56bb72-cc10-ba74-2b04-4df588804ef5@RedHat.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
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':
^~~~
make[4]: *** No rule to make target '../../support/nfs/libnfs.a', needed by 'nsm_client'.
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)
^~~~~~~~~
statdb_dump.c: In function ‘main’:
statdb_dump.c:91:10: warning: unused parameter ‘argc’ [-Wunused-parameter]
main(int argc, char **argv)
^~~~
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.
Any idea?
Andy
Arch Linux
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-21 20:25 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 [this message]
2018-01-04 5:11 ` NeilBrown
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=20171221212516.031618d8@laptop64.home \
--to=andreas.radke@mailbox.org \
--cc=SteveD@RedHat.com \
--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