public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Tetsuji Rai <maverick6664@gmail.com>, gcc@gcc.gnu.org
Subject: Re: gcc 10.0.1 20200506 build fails to compile linux kernel
Date: Wed, 6 May 2020 09:19:59 +0200	[thread overview]
Message-ID: <45685814-0b88-ee87-f9a2-83d3946f299b@suse.cz> (raw)
In-Reply-To: <f4f5b462-1413-338b-872c-eed5a56f29a1@gmail.com>

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  7:20 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 [this message]
2020-05-06 12:01   ` Tetsuji Rai
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=45685814-0b88-ee87-f9a2-83d3946f299b@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=maverick6664@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).