All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sumit Garg" <sumit.garg@linaro.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Ryan Harkin <ryan.harkin@linaro.org>,
	Khem Raj <raj.khem@gmail.com>,
	 yocto@lists.yoctoproject.org,
	Ralph Siemsen <ralph.siemsen@linaro.org>,
	 Jon Mason <Jon.Mason@arm.com>,
	Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	 openembedded <openembedded@lists.linaro.org>
Subject: Re: [yocto] dunfell gcc-sanitizers-arm-8.3 fails to build
Date: Sat, 1 Aug 2020 19:49:13 +0530	[thread overview]
Message-ID: <CAFA6WYMkfqNRvd51Mmi=2wZNGwz0Xi7Y_Uhy4BhS4kDnvkoyRw@mail.gmail.com> (raw)
In-Reply-To: <16272A3CFA65FC0B.22952@lists.yoctoproject.org>

On Sat, 1 Aug 2020 at 19:40, Sumit Garg via lists.yoctoproject.org
<sumit.garg=linaro.org@lists.yoctoproject.org> wrote:
>
> On Sat, 1 Aug 2020 at 14:57, Ryan Harkin <ryan.harkin@linaro.org> wrote:
> >
> >
> >
> > On Sat, 1 Aug 2020 at 10:09, Ryan Harkin <ryan.harkin@linaro.org> wrote:
> >>
> >> Hi Khem,
> >>
> >> On Fri, 31 Jul 2020, 21:58 Khem Raj, <raj.khem@gmail.com> wrote:
> >>>
> >>> On Fri, Jul 31, 2020 at 8:35 AM Ryan Harkin <ryan.harkin@linaro.org> wrote:
> >>> >
> >>> > Hello,
> >>> >
> >>> > I'm migrating from Warrior to Dunfell and I'm getting a curious build failure in gcc-sanitizers.
> >>> >
> >>> > Here's the full gory detail:
> >>> >     https://pastebin.ubuntu.com/p/nh4cDKMvgS/
> >>> >
> >>> > However, the main error is this:
> >>> >
> >>> > | In file included from ../../../../../../../../../work-shared/gcc-arm-8.3-r2019.03/git/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:193:
> >>> > | ../../../../../../../../../work-shared/gcc-arm-8.3-r2019.03/git/libsanitizer/sanitizer_common/sanitizer_internal_defs.h:317:72: error: size of array 'assertion_failed__1152' is negative
> >>> > |      typedef char IMPL_PASTE(assertion_failed_##_, line)[2*(int)(pred)-1]
> >>> >
> >>> > I have no idea where to begin with this. I don't even know why gcc-sanitizers is included in the build, what it does, or why I need it. I'm building an image with dev packages and gcc, so I guess that's why.
> >>> >
> >>> > I've hacked meta-arm to patch sanitizer_platform_limits_posix.cc to null out the macros and that builds fine. I'm sure it won't work, should someone want to use it, mind you.
> >>> >
> >>> > Is there something obvious that I should be doing as part of a Warrior -> Dunfell migration to get this to work?
> >>> >
> >>> > note: Warrior used meta-linaro-toolchain and for Dunfell, it's moved to meta-arm-toolchain.
> >>> >
> >>>
> >>> is gcc 8.3 the latest for linaro
> >>
> >>
> >> I assume so. I haven't attempted to change the default.
> >
> >
> > I'm sorry, that's incorrect: local.conf has an over-ride to specify 8.3.
> > I've just removed it and now it's using 9.3. And it's building fine.
> >

It's using GCC 9.3 from OE core. If you wish to use Arm toolchain then
you need to override the default OE core GCC version with Arm
toolchain GCC version:

GCCVERSION = "arm-9.2"

-Sumit

> > Sumit, do you know if there's a reason for using 9.2 in RPB instead of 9.3?
> >
>
> Arm GCC 9.3 toolchain isn't released yet (see here [1]).
>
> [1] https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads
>
> -Sumit
>
> >>
> >>>
> >>> > Regards,
> >>> > Ryan.
> >>> >
> 

  parent reply	other threads:[~2020-08-01 14:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 15:35 dunfell gcc-sanitizers-arm-8.3 fails to build Ryan Harkin
2020-07-31 20:58 ` [yocto] " Khem Raj
2020-08-01  9:09   ` Ryan Harkin
2020-08-01  9:26     ` Ryan Harkin
2020-08-01 14:10       ` Sumit Garg
     [not found]       ` <16272A3CFA65FC0B.22952@lists.yoctoproject.org>
2020-08-01 14:19         ` Sumit Garg [this message]
2020-08-02  7:30           ` Ryan Harkin
2020-08-01  6:50 ` Sumit Garg
2020-08-01  9:11   ` Ryan Harkin
2020-08-01 14:07     ` Sumit Garg

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='CAFA6WYMkfqNRvd51Mmi=2wZNGwz0Xi7Y_Uhy4BhS4kDnvkoyRw@mail.gmail.com' \
    --to=sumit.garg@linaro.org \
    --cc=Jon.Mason@arm.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded@lists.linaro.org \
    --cc=raj.khem@gmail.com \
    --cc=ralph.siemsen@linaro.org \
    --cc=ryan.harkin@linaro.org \
    --cc=yocto@lists.yoctoproject.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.