All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the kspp-gustavo tree
Date: Wed, 20 Oct 2021 09:20:25 -0700	[thread overview]
Message-ID: <202110200920.8B67A8A6@keescook> (raw)
In-Reply-To: <20211020161851.GA1297326@embeddedor>

On Wed, Oct 20, 2021 at 11:18:51AM -0500, Gustavo A. R. Silva wrote:
> Hi Stephen,
> 
> On Mon, Oct 18, 2021 at 07:30:48PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the kspp-gustavo tree, today's linux-next build (sparc64
> > defconfig) failed like this:
> > 
> > sparc64-linux-gcc: error: unrecognized command line option '-Wcast-function-type'; did you mean '-Wbad-function-cast'?
> > 
> > $ sparc64-linux-gcc --version
> > sparc64-linux-gcc (Custom f51944395b6aa154) 7.3.1 20180130
> 
> I think this should work just fine with GCC 8.x

Does -Wcast-function-type need to be used via cc-option ?

-Kees

> 
> Thanks
> --
> Gustavo
> 
> > 
> > Caused by commit
> > 
> >   21078041965e ("Makefile: Enable -Wcast-function-type")
> > 
> > I have reverted that commit for today.
> > 
> > -- 
> > Cheers,
> > Stephen Rothwell
> 
> 

-- 
Kees Cook

  reply	other threads:[~2021-10-20 16:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18  8:30 linux-next: build failure after merge of the kspp-gustavo tree Stephen Rothwell
2021-10-20 16:18 ` Gustavo A. R. Silva
2021-10-20 16:20   ` Kees Cook [this message]
2021-10-25  1:55 ` Stephen Rothwell
2021-10-25 19:19   ` Kees Cook
2021-10-25 19:31     ` Gustavo A. R. Silva
2021-10-25 19:34       ` Kees Cook
  -- strict thread matches above, loose matches on Subject: below --
2023-11-21  2:19 Stephen Rothwell
2023-11-21 16:31 ` Gustavo A. R. Silva
2023-11-21 23:15   ` Stephen Rothwell
2023-11-17  0:33 Stephen Rothwell
2023-11-17  0:39 ` Gustavo A. R. Silva
2021-10-18  7:15 Stephen Rothwell
2021-10-18 17:13 ` Gustavo A. R. Silva
2021-10-25  1:54 ` Stephen Rothwell
2021-10-25  2:11   ` Gustavo A. R. Silva
2021-10-25  2:42     ` Steven Rostedt
2021-10-25  4:30       ` Stephen Rothwell
2021-10-25 11:35         ` Steven Rostedt
2021-10-14 23:48 Stephen Rothwell
2021-10-15  0:07 ` Gustavo A. R. Silva
2021-10-15  8:02   ` Stephen Rothwell
2021-09-29 23:59 Stephen Rothwell
2021-09-30  0:11 ` Gustavo A. R. Silva
2020-08-17 23:38 Stephen Rothwell
2020-08-18  0:06 ` Gustavo A. R. Silva
2020-08-17 23:34 Stephen Rothwell
2020-08-17 23:46 ` Gustavo A. R. Silva

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=202110200920.8B67A8A6@keescook \
    --to=keescook@chromium.org \
    --cc=gustavo@embeddedor.com \
    --cc=gustavoars@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.