From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: valdis.kletnieks@vt.edu
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Laura Abbott <labbott@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: linux-next 20180320 compile failure - tools/lib/str_error_r.c
Date: Wed, 21 Mar 2018 10:29:38 -0300 [thread overview]
Message-ID: <20180321132938.GA3749@redhat.com> (raw)
In-Reply-To: <40533.1521564212@turing-police.cc.vt.edu>
Em Tue, Mar 20, 2018 at 12:43:32PM -0400, valdis.kletnieks@vt.edu escreveu:
> 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
>
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=854e55ad289e
- Arnaldo
next prev parent reply other threads:[~2018-03-21 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 16:43 linux-next 20180320 compile failure - tools/lib/str_error_r.c valdis.kletnieks
2018-03-21 13:29 ` Arnaldo Carvalho de Melo [this message]
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=20180321132938.GA3749@redhat.com \
--to=acme@redhat.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@redhat.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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.