linux/poky.git/meta/classes, branch yocto-2.1.1

devshell.bbclass: fix double unbuffering

2016-07-06T16:25:48+00:00

stdout is already unbuffered in bitbake code. Attempt to do it again in devshell.bbclass causes this crash when running devpyshell: File "scripts/oepydevshell-internal.py", line 29, in pty = open(sys.argv[1], "w+b", 0) IOError: [Errno 13] Permission denied: '/dev/pts/6' (From OE-Core rev: 90a12e07ee22df900fa740c6c2f1efe41e93b9f4) Signed-off-by: Ed Bartosh Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

image.bbclass: do exact match for rootfs type

2016-06-29T18:37:19+00:00

Do exact match for rootfs type, instead of pattern match, to avoid unexpected build error due to redundant rootfs type build. E.g. when building ext2.gz.u-boot, both .gz.u-boot and .u-boot are matched, the following build error will appear, actually .u-boot is not needed. | mkimage: Can't open .../core-image-minimal--.rootfs.ext2.gz: No such file or directory (From OE-Core rev: 46bc438374de74af76d288520c6252c9b7840767) (From OE-Core rev: 1d0ea655e266e7c5acc9c282fa91406fbe9bfb85) Signed-off-by: Zhenhua Luo Signed-off-by: Richard Purdie

useradd-staticids.bbclass: Allow missing UIDs/GIDs to generate warnings

2016-06-29T18:36:02+00:00

Previously when USERADD_ERROR_DYNAMIC was set to "1", an exception was raised if no numeric UID/GID could be determined for a user/group. Now it is possible to set it to either "error", which results in the old behavior, or "warn" in which case a warning is issued instead. For backwards compatibility reasons, it is still possible to set USERADD_ERROR_DYNAMIC to "1" and get an exception in case of failure. (From OE-Core rev: 58c82f79efee8e68fa63b96a32f54660afb15769) (From OE-Core rev: 5a37852e4ab3a7438cab372b288663535ecdfee1) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit 3037e0df9b1a0e1cb5332ab8026245b61515fc33) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

useradd-staticids.bbclass: Restore failure on missing UIDs/GIDs

2016-06-29T18:36:02+00:00

A regression was introduced with commit 3149319a whereby setting USERADD_ERROR_DYNAMIC no longer resulted in an error for users and groups that were missing numeric UIDs and GIDs but were not mentioned at all in any passwd or groups file. [YOCTO #9777] (From OE-Core rev: adc0f830a695c417b4d282fa580c5231e1f0afbe) (From OE-Core rev: b64316f34a45dcf7a31e0486e51799fcd6b0ed2d) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit c99750d17e7eaeaa16e5a8510d64e89cef856411) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

gcc-runtime, libgcc: Symlink c++ header and startup files in target_triplet for SDK use

2016-06-29T18:36:01+00:00

We build SDKs such that gcc-cross-candian is built for only one target *-*-linux and then use -muclibc or -mmusl to let it compile code for other libc variants. This works fine when libc = glibc however it does not work for c++ programs when libc != glibc since there are c++ headers installed under ${includedir}/c++/${BINV}/${TARGET_SYS} which is fine when gcc-runtime and gcc-cross-candian uses same --target options gxx includedir searches in right triplet, but it fails with musl/uclibc since gcc will look for glibc based triplet but gcc-runtime will install them under musl/uclibc triplet. This patch symlinks the musl/uclibc triplet to glibc triplet when libc != glibc This fixes SDKs for musl/uclibc (From OE-Core rev: 610c48be139b046860a234baccf13d1e6fafe2b4) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

] syslinux.bbclass: Added configurable SYSLINUX_ALLOWOPTIONS variable

2016-06-29T18:36:00+00:00

The new variable allows for images to be created without an editable boot line in syslinux. Default behavior remains unchanged. Backport from master (935578c139a260c18e437419be82d7fd7e8be81a) (From OE-Core rev: 9bbacbe563c1c7dd4761b30da1c10e247aa49cd8) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

classes/base: get_lic_checksum_file_list imporve validaton of url's

2016-06-29T18:36:00+00:00

When specify an URL different that supported file:// the function returns an empty path causing an exception without notice the user that the URL is Malformed. [YOCTO #9211] (From OE-Core rev: 6c28251d3d187b60ceb534055dbd8b4fffd06429) (From OE-Core rev: 81c1327c33e4e9cfcb0f264c19f71e9144c852d6) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

metadata_scm.bbclass: Do not assume ${COREBASE} is a Git repo

2016-06-29T18:35:59+00:00

The functions base_detect_revision() and base_detect_branch() try to extract SCM meta information from the path returned by base_get_scmbasepath(), which currently returns ${COREBASE}. However, making the assumption that ${COREBASE} contains SCM meta information can be false. It is true for Poky, but not necessarily other environments. A better option is to look for the SCM meta information based on the meta layer. Since this works as expected for Git but not SVN, the call to base_get_metadata_svn_revision() from base_detect_revision() was also removed. This is not expected to affect anyone (partly based on the comment in base_get_metadata_svn_revision()). (From OE-Core rev: 53fd0a4a37023642a770a9fbf3cd5511d3c82af7) (From OE-Core rev: 59b7a5b64c19afc342ca72ccee99cdcfb818e341) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

populate_sdk_ext: Change lockedsigs task mismatch to a warning

2016-06-29T18:35:59+00:00

It has been determined that it is highly likely that users might get signatures that don't match in an extensible sdk. This doesn't necessarily happen with oe-core, so we can set the mismatch to an error during testing if we like. However, for the case where users are creating their own sdks, we don't need an error halting their progress. locked-sigs will still function as it should. (From OE-Core rev: 6ba86d847275126bf435f144e7d029d10e7ab17d) (From OE-Core rev: 0822edc390eea27f68bc257531d84959e3cc1efe) Signed-off-by: Randy Witt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

populate_sdk_ext.bbclass : Show logfile in case the SDK EXT installation failed

2016-06-29T18:35:59+00:00

To avoid lots of output in the SDK EXT installation phase, system redirects it to a logfile ($target_sdk_dir/preparing_build_system.log) but in case of error, the contents should be shown so debugging could be faster. [YOCTO #9576] (From OE-Core rev: 227d2cbf9e0b8c35fa6644e3d72e0699db9607fa) (From OE-Core rev: 502442403e3cdab11e34d355610b07ae4a6db7bb) Signed-off-by: Leonardo Sandoval Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie