summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorJean-Francois Dagenais <jeff.dagenais@gmail.com>2015-11-16 14:37:16 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-12-01 21:30:52 +0000
commita36469c97c9cb335de1e95dea5141038f337df95 (patch)
tree39a9a165d6bb9cb313da08326f9ff35941d4bc07 /scripts
parent259d1d1889b9349498d3f995a09466ce89bd3fcf (diff)
downloadopenembedded-core-a36469c97c9cb335de1e95dea5141038f337df95.tar.gz
openembedded-core-a36469c97c9cb335de1e95dea5141038f337df95.tar.bz2
openembedded-core-a36469c97c9cb335de1e95dea5141038f337df95.zip
toolchain-shar-relocate: don't assume last state of env_setup_script is good
In the case where many environment-setup-* files exist, the incorrect filename might be lastly set in env_setup_script, which leads to incorrect behaviour for the initialization of native_sysroot. The scenario I had was that our custom meta-toolchain-*.bb, which inherits populate_sdk, defined another environment-setup-* file to dump variable information for qt-creator. The file is named like so in order for the sdk shell script to pick it up and fix the SDK paths in the file. Since it (coincidentally) alphabetically comes after ...-core2, it was last set in env_setup_script and the grep OECORE_NATIVE_SYSROOT would simply be blank. The apparent symptom was "...relocate_sdk.py: Argument list too long" since the find command would not be searching in the right path. Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions