Fix target cflags for gcc cross builds
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | Use TUNE_CCARGS for target compilationmeta/ meta/ meta/ | +6 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] Fix target cflags for gcc cross builds
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(-)
Signature · 1 line
2.3.1