From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem building kernel 4.0 with gcc5 Werror
Date: Mon, 11 May 2015 11:58:11 -0000 [thread overview]
Message-ID: <1431345487.2398.81.camel@x220> (raw)
In-Reply-To: <CAK5mtexcPDxzCSY5dSP3QD10F-ZYaVYkKHA25Nq9JFvwv1y+6g@mail.gmail.com>
On Sat, 2015-05-09 at 18:28 -0500, Victor Rodriguez wrote:
> I am trying to build the kernel 4.0 with gcc 5 . But I found the
> following problem :
>
> builtin-report.c comparison of constant ?-1? with boolean expression
> is always false
>
> THe problem is that gcc5 has new warnings:
>
> A new command-line option -Wbool-compare has been added for the C and
> C++ compilers, which warns about boolean expressions compared with an
> integer value different from true/false.
> https://gcc.gnu.org/gcc-5/changes.html
I think the problem is actually that the code is broken. See commit
fefd2d9619de ("perf report: Fix branch stack mode cannot be set") in
linux-next which links to
http://lkml.kernel.org/r/1423967617-28879-1-git-send-email-hekuang at huawei.com .
> I was checking the Makefile of tools/perf/ anda aprently they became
> every warning into an error. Werror
(tools/perf/Makefile.perf has this line
# Define WERROR=0 to disable treating any warnings as errors.
Perhaps that might help you get past this build error. I don't know, I
never tried it. But the best thing here seems to use that patch. I guess
it should eventually show up in the v4.0.y-stable tree.)
> Now I wonder if someone is working on this changes so I can take their pathces.
>
> Do you know any easy way that GCC use to avoid this kind of problems
>
> All the help is more than welcome
Hope this helps,
Paul Bolle
prev parent reply other threads:[~2015-05-11 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 23:28 Problem building kernel 4.0 with gcc5 Werror Victor Rodriguez
2015-05-11 11:58 ` Paul Bolle [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=1431345487.2398.81.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).