All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Bunk" <bunk@stusta.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] gcc-target: Ensure buildtools-extended-tarball doesn't use arch=native
Date: Tue, 5 May 2020 13:14:27 +0300	[thread overview]
Message-ID: <20200505101427.GA19882@localhost> (raw)
In-Reply-To: <20200501164602.1540633-1-richard.purdie@linuxfoundation.org>

On Fri, May 01, 2020 at 05:46:01PM +0100, Richard Purdie wrote:
> A nativesdk BBCLASSEXTEND was added to gcc-target without realising this
> would pass arch=native through to it for x86-64. This heavily optimises
> gcc output for the host its running on meaning it can't be reused via
> sstate on other machines.
> 
> Add class-target overrides here to get the desired behaviour. All
> targets have been covered for completeness.
>...
> +EXTRA_OECONF_append_x86-64_class-target = " --with-arch=native"
>...

What do you expect --with-arch=native to do for the target
of a cross compiler?

cu
Adrian

  parent reply	other threads:[~2020-05-05 10:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 16:46 [PATCH 1/2] gcc-target: Ensure buildtools-extended-tarball doesn't use arch=native Richard Purdie
2020-05-01 16:46 ` [PATCH 2/2] abi_version/staging: Bump versions to force rebuild after sstate corruption Richard Purdie
2020-05-01 16:54 ` [OE-core] [PATCH 1/2] gcc-target: Ensure buildtools-extended-tarball doesn't use arch=native Khem Raj
2020-05-05 10:14 ` Adrian Bunk [this message]
2020-05-05 12:42   ` Richard Purdie

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=20200505101427.GA19882@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.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.