From: Peter Seebach <peter.seebach@windriver.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Use TUNE_CCARGS for target compilation
Date: Thu, 14 Jan 2016 15:27:19 -0600 [thread overview]
Message-ID: <20160114152719.528e3065@seebs-worktop> (raw)
In-Reply-To: <CAJ86T=USrxx9LmAHpZXC9wnMDCZ1s-NT+Fq+H=ovLApjU8ks1A@mail.gmail.com>
On Thu, 14 Jan 2016 13:24:22 -0800
Andre McCurdy <armccurdy@gmail.com> wrote:
> Could that PPC64 issue be solved in the same way that the default arch
> is set in gcc-configure-common.inc for the various MIPS targets?
Huh. That might be a better choice. I hadn't noticed that default arch
selection thing. It would make sense to use that. I'll give it a look and see
whether it works.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2016-01-14 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:04 [PATCH 0/1] Fix target cflags for gcc cross builds Peter Seebach
2016-01-14 21:04 ` [PATCH 1/1] Use TUNE_CCARGS for target compilation Peter Seebach
2016-01-14 21:24 ` Andre McCurdy
2016-01-14 21:27 ` Peter Seebach [this message]
2016-01-14 21:29 ` Mark Hatle
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=20160114152719.528e3065@seebs-worktop \
--to=peter.seebach@windriver.com \
--cc=armccurdy@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