From: Ross Burton <Ross.Burton@arm.com>
To: "danismostlikely@gmail.com" <danismostlikely@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Daniel McGregor <daniel.mcgregor@vecima.com>
Subject: Re: [OE-core] [PATCH 2/3] gcc: set the default target arch
Date: Thu, 29 Sep 2022 11:19:15 +0000 [thread overview]
Message-ID: <133AE478-7799-4555-9260-2706CF3E11E9@arm.com> (raw)
In-Reply-To: <20220928221320.1763684-2-danismostlikely@gmail.com>
On 28 Sep 2022, at 23:13, Dan McGregor via lists.openembedded.org <danismostlikely=gmail.com@lists.openembedded.org> wrote:
>
> From: Daniel McGregor <daniel.mcgregor@vecima.com>
>
> The default x86-64 architecture for target gcc (ie, the one in poky
> build appliances) is native. Since we have a variety of build systems
> it will occasionally produce instructions that don't work on all of
> our development system.
>
> Instead, set gcc's default architecture to the one specified in
> TUNE_CC_ARCH, that guarantees that gcc-runtime and any binaries
> produced are compatible with the target machine type.
Can you explain the use-case here? These are target binaries, so why is the development system relevant?
Ross
next prev parent reply other threads:[~2022-09-29 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 22:13 [PATCH 1/3] coreutils: add openssl PACKAGECONFIG Dan McGregor
2022-09-28 22:13 ` [PATCH 2/3] gcc: set the default target arch Dan McGregor
2022-09-29 11:19 ` Ross Burton [this message]
[not found] ` <08a4803c-628e-c898-eef4-7d40775e27bf@vecima.com>
2022-09-29 15:33 ` [OE-core] " Ross Burton
2022-09-28 22:13 ` [PATCH 3/3] systemd: generate manpages indexes Dan McGregor
2022-09-29 7:16 ` [OE-core] " Richard Purdie
2022-09-29 15:41 ` Dan McGregor
2022-09-29 19:03 ` Dan McGregor
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=133AE478-7799-4555-9260-2706CF3E11E9@arm.com \
--to=ross.burton@arm.com \
--cc=daniel.mcgregor@vecima.com \
--cc=danismostlikely@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox