From: Gabriel C <nix.or.die@googlemail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: Linux 5.8-rc1
Date: Tue, 16 Jun 2020 23:19:27 +0200 [thread overview]
Message-ID: <CAEJqkghK8cjtsKUGn0bJ8nurzu2saNcVOAKJ43BtmgANWMY38Q@mail.gmail.com> (raw)
In-Reply-To: <20200616203741.GA13437@zn.tnic>
Am Di., 16. Juni 2020 um 22:37 Uhr schrieb Borislav Petkov <bp@alien8.de>:
>
> On Tue, Jun 16, 2020 at 10:11:46PM +0200, Gabriel C wrote:
> > I didn't look closer at that but from the error, it seems to be,
> > some missing -fstack-protector* vs -fno-stack-protector* checks
> > somewhere.
>
> Can you give exact .config?
>
> Also, what compiler exactly?
Sure, config and compiler information uploaded to there:
http://crazy.dev.frugalware.org/kernel/
>
> I have
>
> CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
> CONFIG_KEXEC_FILE=y
> CONFIG_HAVE_STACKPROTECTOR=y
> CONFIG_CC_HAS_STACKPROTECTOR_NONE=y
> CONFIG_STACKPROTECTOR=y
> CONFIG_STACKPROTECTOR_STRONG=y
>
> here and gcc9 builds it fine.
I have gcc 9.2.1 20200215.
prev parent reply other threads:[~2020-06-16 21:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 20:44 Linux 5.8-rc1 Linus Torvalds
2020-06-15 1:59 ` linux-next: stats (Was: Linux 5.8-rc1) Stephen Rothwell
2020-06-16 20:11 ` Linux 5.8-rc1 Gabriel C
2020-06-16 20:33 ` Arvind Sankar
2020-06-16 21:17 ` Gabriel C
2020-06-16 21:25 ` Arvind Sankar
2020-06-16 22:00 ` Gabriel C
2020-06-16 22:28 ` Arvind Sankar
2020-06-16 21:35 ` Gabriel C
2020-06-16 22:25 ` [PATCH] x86/purgatory: Add -fno-stack-protector Arvind Sankar
2020-06-17 0:06 ` Linus Torvalds
2020-06-16 20:37 ` Linux 5.8-rc1 Borislav Petkov
2020-06-16 21:19 ` Gabriel C [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=CAEJqkghK8cjtsKUGn0bJ8nurzu2saNcVOAKJ43BtmgANWMY38Q@mail.gmail.com \
--to=nix.or.die@googlemail.com \
--cc=bp@alien8.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).