From: valdis.kletnieks@vt.edu
To: Arnaldo Carvalho de Melo <acme@redhat.com>
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 14:37:57 -0400 [thread overview]
Message-ID: <147690.1521657477@turing-police.cc.vt.edu> (raw)
In-Reply-To: <20180321132938.GA3749@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Wed, 21 Mar 2018 10:29:38 -0300, Arnaldo Carvalho de Melo said:
> Em Tue, Mar 20, 2018 at 12:43:32PM -0400, valdis.kletnieks@vt.edu escreveu:
> > 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
Confirming that fixes the problem...
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
prev parent reply other threads:[~2018-03-21 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 16:43 valdis.kletnieks
2018-03-21 13:29 ` Arnaldo Carvalho de Melo
2018-03-21 18:37 ` valdis.kletnieks [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=147690.1521657477@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@redhat.com \
--cc=labbott@redhat.com \
--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®