From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Fix target cflags for gcc cross builds
Date: Thu, 14 Jan 2016 15:04:40 -0600 [thread overview]
Message-ID: <cover.1452805356.git.peter.seebach@windriver.com> (raw)
In some cases, CFLAGS_FOR_TARGET may need to have tune-specific compiler
flags, particularly if you're trying to build a multilib compiler which
won't automatically pick the right ABI, bit size, etc. by default if
invoked without them. After some experimentation and thought, I concluded
that cross gcc should use these in CFLAGS_FOR_TARGET, but crosssdk shouldn't.
This appears to work, at least for the reasonably obvious cases.
We did this back in November, and I thought I submitted it then, but
apparently the email never made it out. Rebased against current master.
The following changes since commit 541315d6c56df6448f64c262f99d43d5c1e9400b:
update_font_cache: only scan system font directories (2016-01-11 23:23:18 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/gcc_target_args
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/gcc_target_args
Peter Seebach (1):
Use TUNE_CCARGS for target compilation
meta/classes/crosssdk.bbclass | 4 ++++
meta/recipes-devtools/gcc/gcc-configure-common.inc | 2 +-
meta/recipes-devtools/gcc/gcc-cross.inc | 2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
--
2.3.1
next reply other threads:[~2016-01-14 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:04 Peter Seebach [this message]
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
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=cover.1452805356.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.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 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.