public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tetsuji Rai <maverick6664@gmail.com>
To: "Martin Liška" <mliska@suse.cz>, gcc@gcc.gnu.org
Subject: Re: gcc 10.0.1 20200506 build fails to compile linux kernel
Date: Wed, 6 May 2020 21:01:22 +0900	[thread overview]
Message-ID: <c49ce455-63cd-c2ea-dfc0-6447b55f0763@gmail.com> (raw)
In-Reply-To: <45685814-0b88-ee87-f9a2-83d3946f299b@suse.cz>

Hi Martin,

Thank you for your reply!

Spot on!

It was my kernel config problem associated with stronger stack
protection of gcc-10, not a gcc problem.  But I can't find this in
kernel.org bugzilla or bugzilla.redhat.com (searched with "gcc 10" and
"gcc-10".)

It happens not in qemu or any VM, but on a native machine.  As in
https://bugzilla.redhat.com/show_bug.cgi?id=1796780 (this is the first
url in the page you mentioned), turning CONFIG_STACKPROTECTOR_STRONG
off, lo and behold, the kernel works perfectly!! And as a matter of
course, it works for the latest kernel 5.6.11 also.

My problem was that I brought my custom kernel config file from Fedora
31 with gcc-9.   I should have started from the prototype config file
/boot/config-5.6.8-300.fc32.x86_64, where CONFIG_STACKPROTECTOR_STRONG
is off for its native gcc.

Thank you very much!!

-Tetsuji

On 5/6/20 4:19 PM, Martin Liška wrote:
> On 5/6/20 6:44 AM, Tetsuji Rai via Gcc wrote:
>> I wonder how Fedora project built its own kernel.  I can't build custom
>> kernel with it.
>>
>> What's wrong with 10.1-RC or how can I report my problem?
>
> Hi.
>
> Is it possible that you reached
> https://lore.kernel.org/lkml/20200417190607.GY2424@tucnak/T/ ?
>
> I can try to reproduce that but please file a bug at or bugzilla and
> provide
> steps how to reproduce the issue. Can you also reproduce it within a
> qemu VM?
>
> Thanks,
> Martin

  reply	other threads:[~2020-05-06 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06  4:44 Tetsuji Rai
2020-05-06  7:19 ` Martin Liška
2020-05-06 12:01   ` Tetsuji Rai [this message]
2020-05-06 12:28     ` Martin Liška

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=c49ce455-63cd-c2ea-dfc0-6447b55f0763@gmail.com \
    --to=maverick6664@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).