All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Jansa" <Martin.Jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 Bruce Ashfield <bruce.ashfield@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: Tue, 18 Aug 2020 13:57:26 +0200	[thread overview]
Message-ID: <CA+chaQeE25GYJEv4z329B4XR5SgAAEgx+OptqszNQmQ-Lsvu2A@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1spcEhgu0GE28h30uW60Qw8k+L_LO6qPD1YhSJ+69Pe18A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]

Yes, I'm seeing this weird concatenation with raspberrypi builds as well:

find: unknown predicate `-mthumb/arch'
arm-webos-linux-gnueabi-gcc: error: unrecognized command-line option
'-mthumb/include/uapi/asm-generic/errno.h'
arm-webos-linux-gnueabi-gcc: fatal error: no input files
compilation terminated.

But in this case it isn't fatal for the perf build, I've noticed it only
because it was failing with 5.4.51 currently in meta-raspberrypi and after
upgrade to 5.4.58 perf built OK, but this error message is still there in
log.do_compile.

On Mon, Aug 17, 2020 at 9:47 PM Khem Raj <raj.khem@gmail.com> wrote:

> On Mon, Aug 17, 2020 at 5:27 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > 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 seems to be concaternation of compiler options without space
>
> | arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option
> '-mfpu=neon/include/uapi/asm-generic/errno.h'
> | arm-poky-linux-gnueabi-gcc: note: valid arguments to '-mfpu=' are:
> auto crypto-neon-fp-armv8 fp-armv8 fpv4-sp-d16 fpv5-d16 fpv5-sp-d16
> neon neon-fp-armv8 neon-fp16 neon-vfpv3 neon-vfpv4 vfp vfp3 vfpv2
> vfpv3 vfpv3-d16 vfpv3-d16-fp16 vfpv3-fp16 vfpv3xd vfpv3xd-fp16 vfpv4
> vfpv4-d16
> | arm-poky-linux-gnueabi-gcc: fatal error: no input files
>
> but it also showed up on x86_64 in one of your prior builds, so I
> wonder if its something in kernel build system or is it processing
> TUNE_CCARGS in special ways.
>
> > There is still some piece of this we're missing, maybe on non-IA.
> >
> > Cheers,
> >
> > Richard
> >
> 
>

[-- Attachment #2: Type: text/html, Size: 3907 bytes --]

  parent reply	other threads:[~2020-08-18 11:57 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
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 [this message]
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=CA+chaQeE25GYJEv4z329B4XR5SgAAEgx+OptqszNQmQ-Lsvu2A@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=jacob.kroon@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.