diff options
author | Kevin Tian <kevin.tian@intel.com> | 2010-12-30 12:36:50 +0800 |
---|---|---|
committer | Saul Wold <sgw@linux.intel.com> | 2011-01-02 01:25:40 -0800 |
commit | f13cb20ed19c41b9ff85ef1c9ec0883a21d1d5bf (patch) | |
tree | 72357a65b1f773db850cd1f47e049996d35b5744 /meta/recipes-graphics/clutter/clutter-gst/autofoo-9db4a61a25677764bb927369c5c68ada958fb65c.patch | |
parent | 2e3cdcb067f9c90f18a2b27d99caa63aa23c488f (diff) | |
download | openembedded-core-f13cb20ed19c41b9ff85ef1c9ec0883a21d1d5bf.tar.gz openembedded-core-f13cb20ed19c41b9ff85ef1c9ec0883a21d1d5bf.tar.bz2 openembedded-core-f13cb20ed19c41b9ff85ef1c9ec0883a21d1d5bf.tar.xz openembedded-core-f13cb20ed19c41b9ff85ef1c9ec0883a21d1d5bf.zip |
gcc-4.5.1: make c++ include path relative to "--sysroot"
So far c++ include path is not relative to "--sysroot", which brings
trouble if we want to use the toolchain in a new environment where
the original build directory generating that toolchain is not
available. It's firstly exposed in multiple SDK sysroots support, and
then in the case when sstate packages are used, where c++ standard
headers are missing because gcc tries to search original build dir.
This patch makes c++ include path now relative to "--sysroot", and
then once "--sysroot" is assigned correctly in new environment, c++
include paths can be searched as expected.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Diffstat (limited to 'meta/recipes-graphics/clutter/clutter-gst/autofoo-9db4a61a25677764bb927369c5c68ada958fb65c.patch')
0 files changed, 0 insertions, 0 deletions