From: valdis.kletnieks@vt.edu
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: linux-next 20180320 compile failure - tools/lib/str_error_r.c
Date: Tue, 20 Mar 2018 12:43:32 -0400 [thread overview]
Message-ID: <40533.1521564212@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
Not sure who to blame here, or what changed in gcc between 0.16 and 0.19,
or what the proper fix is here....
next-20180307 with "gcc version 8.0.1 20180222 (Red Hat 8.0.1-0.16)" built and runs fine.
next-20180320 with "gcc (GCC) 8.0.1 20180317 (Red Hat 8.0.1-0.19)" dies a horrid death early
during the compile:
CC /usr/src/linux-next/tools/objtool/str_error_r.o
../lib/str_error_r.c: In function 'str_error_r':
../lib/str_error_r.c:25:3: error: passing argument 1 to restrict-qualified parameter aliases with argument 5 [-Werror=restrict]
snprintf(buf, buflen, "INTERNAL ERROR: strerror_r(%d, %p, %zd)=%d", errnum, buf, buflen, err);
^~~~~~~~
cc1: all warnings being treated as errors
mv: cannot stat '/usr/src/linux-next/tools/objtool/.str_error_r.o.tmp': No such file or directory
make[3]: *** [Build:22: /usr/src/linux-next/tools/objtool/str_error_r.o] Error 1
make[2]: *** [Makefile:46: /usr/src/linux-next/tools/objtool/objtool-in.o] Error 2
make[1]: *** [Makefile:63: objtool] Error 2
make: *** [Makefile:1681: tools/objtool] Error 2
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
next reply other threads:[~2018-03-20 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 16:43 valdis.kletnieks [this message]
2018-03-21 13:29 ` Arnaldo Carvalho de Melo
2018-03-21 18:37 ` valdis.kletnieks
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=40533.1521564212@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®