linux/poky.git/meta/files, branch 2.1_M1

toolchain-shar-extract.sh: ensure cleaned environment will work for ext SDK

2015-12-08T17:22:31+00:00

In OE-Core revision 6d2074d477596971dc52027dd87b02af7f39138d we added a line which re-executes the script with a cleaned environment using env -i; unfortunately that caused a regression in the extensible SDK on Ubuntu 14.04 - strangely, there it seems that the value you get for PATH under env -i contains '.' which triggers a sanity check failure when preparing the build system. Do a belt-and-braces fix - source /etc/environment if it exists (so you get a more complete PATH value) and then filter any nastiness out of PATH for good measure. (Ubuntu 15.04 doesn't seem to suffer from the same problem.) (From OE-Core rev: 5175d9a6955c1783fc35ab6832b6be4cbb9fc01b) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: proper fix for additional env setup scripts

2015-12-08T10:20:47+00:00

buildtools-tarball uses a custom env setup script, which isn't named the same as the default; thus unfortunately OE-Core revision a36469c97c9cb335de1e95dea5141038f337df95 broke installation of buildtools-tarball. Revert that and implement a more robust mechanism. (From OE-Core rev: 00e081b81ba8118959b724269ba9d18d42aba8a4) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: Ensure it's ran in clean environment

2015-12-01T21:32:02+00:00

Fixes [YOCTO #8698] -- https://bugzilla.yoctoproject.org/show_bug.cgi?id=8698 If prior to running the toolchain installation script a toolchain environment script is sourced then the toolchain installation will fail. This because the environment is now set for the sourced toolchain and doesn't suit the installation. In particular PATH points to the toolchain executables. The fix makes the script recursively call itself a second time with a clean environment. Tested by sourcing a previous successfully installed environment, erasing the previous installation directory and then reinstalling in the same directory. (From OE-Core rev: 6d2074d477596971dc52027dd87b02af7f39138d) Signed-off-by: George Nita Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: do not allow $ in paths for ext SDK

2015-12-01T21:32:02+00:00

If you put an $ character in the path, SDK installation fails during the preparation stage, so add this to the disallowed characters. Fixes [YOCTO #8625]. (From OE-Core rev: 654f4785f719552f4e78e14a5a901c07d00ce68d) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-shar-relocate: don't assume last state of env_setup_script is good

2015-12-01T21:32:02+00:00

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. (From OE-Core rev: a36469c97c9cb335de1e95dea5141038f337df95) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: print full-length title underline

2015-10-20T09:12:01+00:00

Print a line that's the full length of the title that it's underneath. (From OE-Core rev: 83729437c584fc74577a2b15dbb2ae094788339d) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

classes/populate_sdk_ext: prevent image construction from executing on install

2015-10-20T09:12:01+00:00

In order to prepare the build system within the extensible SDK, we actually go ahead and build the targets specified by SDK_TARGETS (by default the image the SDK was built for). Assuming that's an image, we don't actually need to build the image itself - we just need to have everything done up to the point before building the image, so that we have everything needed in the sysroot. In order to do this, create temporary bbappends for each of the targets in the workspace layer that stub out do_rootfs and related tasks if they exist. This is a little bit of a hack but is the least intrusive fix at this point. To make things a bit tidier, I have split out the preparation commands into a separate script so we can run that in the appropriate environment rather than all the commands separately. Fixes [YOCTO #7590]. (From OE-Core rev: d2a2962897b89731a5705b0cbc7c6f36aa53dcc8) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

toolchain-shar-extract.sh: provide proper path for env_setup_script

2015-10-19T16:57:58+00:00

The toolchain install script suggest the user to source env_setup_script from wrong path now. eg: " Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . /opt/poky/2.0//opt/poky/2.0/environment-setup-armv5e-poky-linux-gnueabi " fix it. (From OE-Core rev: b388468deda8d81df80d1509226196a5390183a8) Signed-off-by: Maxin B. John Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

common-licenses: use correct GFDL-1.1 license text

2015-10-19T16:57:57+00:00

It seems that the GFDL 1.1 license file that was originally committed was actually the 1.2 version. Replace it with the 1.1 version fetched from http://www.gnu.org/licenses/old-licenses/fdl-1.1.txt. (From OE-Core rev: d22252a9e0729abb5e1dd39fc2b6359caf948c43) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-shar-extract: Correct environment-setup script names for multilib

2015-10-01T06:43:32+00:00

Currently a lib32-core-image-* SDK prints an incorrect environment-setup-* file name when installing the SDK. Instead of printing the wrong thing, list the environment setup files present in the SDK. As it happens this fixes the message printed with buildtools-tarball too which someone reported to me about the same time as I finished this patch! (From OE-Core rev: c2fa59f46bbc86985e6c8e4d5d514a07a9ade884) Signed-off-by: Richard Purdie