public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Chris Packham <chris.packham@alliedtelesis.co.nz>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Discussions about the Letux Kernel 
	<letux-kernel@openphoenux.org>
Subject: Re: [BUG v5.2-rc1] ARM build broken
Date: Mon, 20 May 2019 13:25:06 -0700	[thread overview]
Message-ID: <201905201324.1259BAB119@keescook> (raw)
In-Reply-To: <9A29E642-3A9D-4BBF-A203-9179D8FADA31@goldelico.com>

On Mon, May 20, 2019 at 09:35:45PM +0200, H. Nikolaus Schaller wrote:
> 
> > Am 20.05.2019 um 20:53 schrieb Kees Cook <keescook@chromium.org>:
> > 
> > 
> >> Build error:
> >> 
> >> HOSTCXX -fPIC scripts/gcc-plugins/arm_ssp_per_task_plugin.o - due to: scripts/gcc-plugins/gcc-common.h
> >> In file included from scripts/gcc-plugins/arm_ssp_per_task_plugin.c:3:0:
> >> scripts/gcc-plugins/gcc-common.h:153:0: warning: "__unused" redefined
> >> #define __unused __attribute__((__unused__))
> >> ^
> > 
> > Does the following patch fix your build? (I assume that line is just a
> > warning, but if not...)
> > 
> > diff --git a/scripts/gcc-plugins/gcc-common.h b/scripts/gcc-plugins/gcc-common.h
> > index 552d5efd7cb7..17f06079a712 100644
> > --- a/scripts/gcc-plugins/gcc-common.h
> > +++ b/scripts/gcc-plugins/gcc-common.h
> > @@ -150,8 +150,12 @@ void print_gimple_expr(FILE *, gimple, int, int);
> > void dump_gimple_stmt(pretty_printer *, gimple, int, int);
> > #endif
> > 
> > +#ifndef __unused
> > #define __unused __attribute__((__unused__))
> > +#endif
> > +#ifndef __visible
> > #define __visible __attribute__((visibility("default")))
> > +#endif
> > 
> > #define DECL_NAME_POINTER(node) IDENTIFIER_POINTER(DECL_NAME(node))
> > #define DECL_NAME_LENGTH(node) IDENTIFIER_LENGTH(DECL_NAME(node))
> 
> Yes, fixes this issue.

Ah, good! Okay, then the rest of the build errors were from not
finishing to build the plugin correctly. Thanks for debugging this; I'll
get the fix sent to Linus. :)

-- 
Kees Cook

  reply	other threads:[~2019-05-20 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DB08A04-D03A-4441-85DE-64A13E6D709C@goldelico.com>
2019-05-20 15:59 ` [BUG v5.2-rc1] ARM build broken Kees Cook
     [not found]   ` <D8F987B2-8F41-46DE-B298-89541D7A9774@goldelico.com>
2019-05-20 18:53     ` Kees Cook
2019-05-20 19:35       ` H. Nikolaus Schaller
2019-05-20 20:25         ` Kees Cook [this message]
2019-05-20 21:21       ` Chris Packham
2019-05-21 11:23         ` H. Nikolaus Schaller
2019-05-21 20:36           ` Kees Cook
2019-05-22  6:02             ` H. Nikolaus Schaller
2019-06-03  7:46               ` [Letux-kernel] " H. Nikolaus Schaller

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=201905201324.1259BAB119@keescook \
    --to=keescook@chromium.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=hns@goldelico.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /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