linux/poky.git/meta/classes/sanity.bbclass, branch dylan

classes/sanity: check for suid root command evility

2013-08-12T12:14:21+00:00

Some users have been found to have an unnamed third-party piece of software installed which sets chmod, chown and mknod as suid root as part of its installation process. This interferes with the operation of pseudo and can result in files really being owned by root within the build output, and therefore breaks the build, apart from being a security issue. Check for this and bail out if it is found. Reported-by: Nicolas Dechesne (From OE-Core master rev: 08d61529f3c7a48ec82e1f8c9c28c7b2e5238934) (From OE-Core rev: 041342a518e1d33349eb52e11750e155a5647735) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sanity.bbclass: Attach the missing value to a format string.

2013-05-22T16:14:04+00:00

The tuning changes to sanity.bbclass were almost right, but one of the messages had a %s with no % operator. (From OE-Core master rev: cf5e40598ae9a83f22cabedc7b72000beb62703c) (From OE-Core rev: b47906121f4440e32f6efef04827f49be5ced657) Signed-off-by: Peter Seebach Signed-off-by: Richard Purdie

classes/sanity: fix handling of bblayers.conf updating

2013-04-13T22:49:33+00:00

Fix the fairly long-standing problem of treating a newer bblayers.conf in the same manner as an older one (reporting that it had been updated even if nothing was done). The recent work to do a reparse without having to manually re-run bitbake turned this from an annoyance into an endless loop, so it had to be fixed. As part of fixing this the following changes have been made: * Extensions are now implemented using a function list, so distro layers can add their own functions which should either succeed (indicating they have successfully updated the file) or raise an exception (indicating nothing could be done). The functions are called in succession until one succeeds, at which point we reparse. * If we can't do the update, the error message now says "older/newer" instead of just "older" since we only know the version is different. (From OE-Core rev: 46b00fdfc9d1e3dc180de087bae2682a1baa2954) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

fix march sanity check issue

2013-03-22T17:01:30+00:00

1. check if gcc_test is really generate before os.remove("gcc_test") to avoid following error: ERROR: Execution of event handler 'check_sanity_eventhandler' failed Traceback (most recent call last): File "check_sanity_eventhandler(e)", line 4, in check_sanity_eventhandler(e=) File "sanity.bbclass", line 107, in check_sanity(sanity_data=) File "sanity.bbclass", line 22, in check_gcc_march(sanity_data=) OSError: [Errno 2] No such file or directory: 'gcc_test' 2. set result to False when build failed with -march=native to ensure -march=native is appended to BUILD_CFLAGS when host gcc really supports this flag, otherwise following error appears when build native packages. | cap_text.c:1: error: bad value (native) for -march= switch | cap_text.c:1: error: bad value (native) for -mtune= switch (From OE-Core rev: 4a4228fe250c8b23a5deeb25825d61c6e84a47a2) Signed-off-by: Zhenhua Luo Signed-off-by: Richard Purdie

sanity.bbclass:check if necessary to add march to BUILD_CFLAGS

2013-03-07T11:14:36+00:00

1, There are a set of GCC built-in functions for atomic memory access. The definition given in the Intel documentation allows only for the use of the types int, long, long long as well as their unsigned counterparts. GCC will allow any integral scalar or pointer type that is 1, 2, 4, 8 or 16 bytes in length, suffix `_n' where n is the size of the data type.Such as: __sync_fetch_and_add_n __sync_fetch_and_sub_n __sync_fetch_and_or_n __sync_fetch_and_and_n __sync_fetch_and_xor_n __sync_fetch_and_nand_n The above builtins are intended to be compatible with those described in the Intel Itanium Processor-specific Application Binary Interface, section 7.4. 2, The glib-2.0-native and qemu-native invoke the above builtin function with suffix `_4', and glib-2.0-native uses __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4 to test the existance. 3, Not all above builtin functions are supported by all target processors.Such as i386 does not support the functions with suffix `_4', but i486 or later support. 4, Prior to GCC 4.5, on the Intel's processor, the default arch is i386 unless GCC is built with the --with-arch switch. Since GCC 4.5 the default arch is implied by the target. 5, If your host GCC is older than 4.5 and it is built without the --with-arch switch, when you use the GCC to compile target, you should specify -march to tell GCC what the target's arch is, otherwise i386 is used as default. Above all, when use older GCC to compile glib-2.0-native or glib-2.0-native, and the GCC incorrectly uses i386 as default, the above builtin function with suffix `_4' is not referenced. We should have a check in sanity.bbclass to tell the user if necessary to add march to BUILD_CFLAGS in this situation. http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/_005f_005fsync-Builtins.html#_005f_005fsync-Builtins http://gcc.gnu.org/ml/gcc-help/2009-06/msg00037.html http://gcc.gnu.org/gcc-4.5/changes.html http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47460 http://llvm.org/bugs/show_bug.cgi?id=11174 http://download.intel.com/design/itanium/downloads/245370.pdf [YOCTO #3563] (From OE-Core rev: 38042ed8586b3abe427af33debc2402caeca52cb) Signed-off-by: Hongxu Jia Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sanity.bbclass: always use oe.lsb.distro_identifier method

2013-03-02T13:00:56+00:00

* even when /etc/redhat-release or /etc/SuSE-release exists * don't read /etc/lsb-release manually, NATIVELSBSTRING is not reading it too (From OE-Core rev: 3dba05d74821f08cd96a18351805c8812ddd626c) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

sanity: use lsb distro_identifier

2013-03-01T13:03:30+00:00

* distro_identifier returns lsb_data['Distributor ID']-lsb_data['Release'] which in some cases is different then lsb_release -d -s, e.g. Distributor ID: Ubuntu Description: Ubuntu 12.04 LTS Release: 12.04 Codename: precise But we probably don't need to sanity list each point release in LTS and sstate is already using distro_identifier as prefix for native sstate archives * This will need update to SANITY_TESTED_DISTROS (at least s/Ubuntu 12.04 LTS/Ubuntu-12.04/g etc), that's why sending as RFC first. (From OE-Core rev: a32ea459ca168792161af2d521a14fe00cffb4b3) Signed-off-by: Martin Jansa Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sanity: check_path_length: replace tab with 8 spaces

2013-02-19T16:47:35+00:00

(From OE-Core rev: de3f2367c46a213d07d834c7e874d2a4a0697026) Signed-off-by: Martin Jansa Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sanity.bbclass: when bblayers.conf is updated, it invokes a reparse

2013-02-15T12:17:35+00:00

When bblayers.conf is updated(when sanity check is running), it should tell to bitbake to reparse configuration files. I will send a patch to bitbake-devel, with the actions needed in bitbake and hob. [YOCTO #3213] (From OE-Core rev: 5db1ff93f7204b43b7242fc7ef415216eb632ed8) Signed-off-by: Cristiana Voicu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sanity.bbclass: Check for DISPLAY for qemutests in BB_ORIGENV now

2013-02-07T09:17:44+00:00

(From OE-Core rev: e43f8f917e4069d74b467dfd6aa29ff762e83a5e) Signed-off-by: Richard Purdie