diff options
| author | Mark Hatle <mark.hatle@windriver.com> | 2013-06-24 09:44:30 -0500 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-06-25 17:43:43 +0100 |
| commit | be21c6e8e4f810e826538337dac6e34ed96e1f6f (patch) | |
| tree | 25469b8a1a57fada7441ebdfe188d1d80417931d /meta/classes | |
| parent | 9ceebb966e5294a270222475ab6317dcae2952fa (diff) | |
| download | openembedded-core-be21c6e8e4f810e826538337dac6e34ed96e1f6f.tar.gz openembedded-core-be21c6e8e4f810e826538337dac6e34ed96e1f6f.tar.bz2 openembedded-core-be21c6e8e4f810e826538337dac6e34ed96e1f6f.zip | |
gcc: When cross compiling a target gcc, target flags may be used on the host
The original fix worked some of the time, but not on all machines. Fix
this by applying the change in a different way. Following the example of
the existing BUILD_CFLAGS.
Below is the commit message from the original change to help explain why
this is needed:
Configure identifies a number of warning flags (WARN_CFLAGS and
WARN_CXXFLAGS) from the $CC value. The cross compiler may be different
from the host compiler and may not support the same set of flags. This
leads to problems such as:
cc1plus: error: unrecognized command line option "-Wno-narrowing"
cc1plus: error: unrecognized command line option "-Wno-overlength-strings"
Work around this problem by removing the warning flags from the
BUILD_CXXFLAGS value, in a way similar to the BUILD_CFLAGS.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta/classes')
0 files changed, 0 insertions, 0 deletions