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: Ross Burton <ross@burtonini.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] gcc: Update to latest on release/gcc-11 branch
Date: Wed, 26 May 2021 17:43:13 +0200	[thread overview]
Message-ID: <CA+chaQcHqvid8LUX+H4tWi=wgOKHnvNY0rtEGZ7a3KqvDFAuYQ@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1soOUcqa6huRjbn5QgP0hkBaFafS2PkgWHbVazW4R0NRnQ@mail.gmail.com>

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

I'm seeing different error with gcc-sanitizers and this new revision:

work-shared/gcc-11.1.0-r0/gcc-11.1.0/libsanitizer/lsan/lsan_common_linux.cpp:164:25:
error: invalid conversion from 'void (*)(void*)' to 'void* (*)(void*)'
[-fpermissive]

will double-check if it was introduced by this upgrade or something else in
oe-core master update today and also if there is a fix in even newer gcc
already.

On Wed, May 26, 2021 at 4:19 PM Khem Raj <raj.khem@gmail.com> wrote:

> On Wed, May 26, 2021 at 3:55 AM Ross Burton <ross@burtonini.com> wrote:
> >
> > I think this breaks non-Linux builds.  All of our Zephyr targets now
> fail:
> >
> > ERROR: gcc-runtime-11.1.0-r0 do_package:
> > QA Issue: gcc-runtime: Files/directories were installed but not
> > shipped in any package:
> > /usr/lib/-gdb.py
>
> this should have had some prefix. do you have this script around if so
> then share
>
> >
> > Ross
> >
> > Ross
> >
> > On Mon, 24 May 2021 at 16:21, Khem Raj <raj.khem@gmail.com> wrote:
> > >
> > > There has been 150+ fixes made available after gcc 11.1.0
> > > was released, details of these fixes is here
> > >
> > >
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff_plain;hp=releases/gcc-11.1.0;h=9ee61d2b51d
> > >
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > ---
> > > v2: Use download mirror to fetch the patch
> > >
> > >  meta/recipes-devtools/gcc/gcc-11.1.inc | 8 ++++++--
> > >  1 file changed, 6 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/meta/recipes-devtools/gcc/gcc-11.1.inc
> b/meta/recipes-devtools/gcc/gcc-11.1.inc
> > > index 713002266a..aa7ac9be59 100644
> > > --- a/meta/recipes-devtools/gcc/gcc-11.1.inc
> > > +++ b/meta/recipes-devtools/gcc/gcc-11.1.inc
> > > @@ -6,7 +6,7 @@ PV = "11.1.0"
> > >
> > >  # BINV should be incremented to a revision after a minor gcc release
> > >
> > > -BINV = "11.1.0"
> > > +BINV = "11.1.1"
> > >
> > >  FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
> > >
> > > @@ -25,7 +25,10 @@ LIC_FILES_CHKSUM = "\
> > >
> > >  #RELEASE ?= "5b2ac9b40c325e9209c0bd55955db84aad4a0cc5"
> > >  #BASEURI ?= "
> https://github.com/gcc-mirror/gcc/archive/${RELEASE}.zip;downloadfilename=gcc-${PV}-${RELEASE}.zip
> "
> > > -BASEURI ?= "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.xz"
> > > +
> > > +BASEURI ?= "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.xz \
> > > +
> http://downloads.yoctoproject.org/mirror/sources/gcc-11.1.0-9ee61d2b51df012c659359873637cc2162ecccf3.patch;apply=yes;name=backports
> \
> > > +           "
> > >  SRC_URI = "\
> > >             ${BASEURI} \
> > >             file://0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch \
> > > @@ -67,6 +70,7 @@ SRC_URI = "\
> > >
>  file://0037-libatomic-Do-not-enforce-march-on-aarch64.patch \
> > >  "
> > >  SRC_URI[sha256sum] =
> "4c4a6fb8a8396059241c2e674b85b351c26a5d678274007f076957afa1cc9ddf"
> > > +SRC_URI[backports.sha256sum] =
> "69274bebd6c069a13443d4af61070e854740a639ec4d66eedf3e80070363587b"
> > >
> > >  S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${PV}"
> > >
> > > --
> > > 2.31.1
> > >
> > >
> > >
> > >
>
> 
>
>

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

  reply	other threads:[~2021-05-26 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 15:21 [PATCH v2] gcc: Update to latest on release/gcc-11 branch Khem Raj
2021-05-26 10:55 ` [OE-core] " Ross Burton
2021-05-26 14:18   ` Khem Raj
2021-05-26 15:43     ` Martin Jansa [this message]
     [not found]     ` <1682A83F9B9CCAC9.4904@lists.openembedded.org>
2021-05-26 17:09       ` Martin Jansa
     [not found]       ` <1682ACF8BD246772.22476@lists.openembedded.org>
2021-05-29 13:09         ` Martin Jansa
2021-05-29 17:16           ` 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+chaQcHqvid8LUX+H4tWi=wgOKHnvNY0rtEGZ7a3KqvDFAuYQ@mail.gmail.com' \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross@burtonini.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 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.