Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>,
	Jacob Kroon <jacob.kroon@gmail.com>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] gcc10: Don't default back to -fcommon
Date: Mon, 17 Aug 2020 13:27:31 +0100	[thread overview]
Message-ID: <a6f7694da55ae6f10cba9a5d216100e54d3c8808.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4OCH85UM8EH+bCOgHC5qh0Tw=1Rg6RPznNu=0y_pg4qyQ@mail.gmail.com>

On Sun, 2020-08-16 at 18:55 -0400, Bruce Ashfield wrote:
> 
> 
> On Sun, Aug 16, 2020 at 9:47 AM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > On Sat, 2020-08-15 at 19:41 -0700, Khem Raj wrote:
> > > Bruce,
> > > 
> > > We need 
> > > 
> > https://github.com/torvalds/linux/commit/168200b6d6ea0cb5765943ec5da5b8149701f36a
> > > backported to 5.4 kernels for perf to build with -fno-common can
> > you
> > > queue this in your kernel updates as soon as you can ?
> > 
> > I think we have other active kernels which will also need it as
> > even
> > with Khem's patch we still see failures:
> > 
> 
> I've taken care of linux-yocto now, I don't think there are any
> active use cases for those kernels that won't be covered.

I bumped the meta-yocto BSPs with a quickly hacked up patch but we
still see:

https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/2339

so I think there may be another patch we need somewhere...

(which matches what we saw with Khem's _append which also failed).

There is still some piece of this we're missing, maybe on non-IA.

Cheers,

Richard


  parent reply	other threads:[~2020-08-17 12:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  8:20 [PATCH] gcc10: Don't default back to -fcommon Jacob Kroon
2020-08-05  0:14 ` [OE-core] " Khem Raj
2020-08-05  5:05   ` Jacob Kroon
2020-08-05  6:00     ` Khem Raj
2020-08-05  6:17       ` Khem Raj
2020-08-05 13:15         ` Jacob Kroon
2020-08-05 13:26           ` Richard Purdie
2020-08-15 22:10         ` Richard Purdie
2020-08-16  1:56           ` Khem Raj
2020-08-16  2:41             ` Khem Raj
2020-08-16 13:47               ` Richard Purdie
2020-08-16 22:55                 ` Bruce Ashfield
2020-08-16 23:14                   ` Khem Raj
2020-08-17 12:27                   ` Richard Purdie [this message]
2020-08-17 14:15                     ` Bruce Ashfield
2020-08-17 14:45                       ` Richard Purdie
2020-08-17 19:47                     ` Khem Raj
2020-08-17 19:55                       ` Khem Raj
2020-08-17 21:07                         ` Bruce Ashfield
2020-08-18 11:57                       ` Martin Jansa
2020-08-18 12:21                         ` Bruce Ashfield
2020-08-18 16:03                           ` Martin Jansa
2020-08-18 16:34                             ` Khem Raj
2020-08-18 17:05                             ` Bruce Ashfield
2020-08-16 23:29                 ` Khem Raj

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=a6f7694da55ae6f10cba9a5d216100e54d3c8808.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=jacob.kroon@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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