linux/poky.git/meta/classes/icecc.bbclass, branch uninative-3.5

icecc.bbclass: replace deprecated bash command substitution

2022-02-08T14:20:18+00:00

- build some packages with icecc enabled is not supported because of the folling that disables the icecc: DEBUG: while parsing set_icecc_env, unable to handle non-literal command '$ICECC_CC' - it can be replicated with: bitbake make && bitbake make -c cleansstate && bitbake make -DD grep ICECC_CC tmp/log/cooker/qemux86-64/console-latest.log - bash command substitution backquote deprecated https://www.gnu.org/software/bash/manual/html_node/Command-Substitution.html https://mywiki.wooledge.org/BashFAQ/082 (From OE-Core rev: b4e3983f38af5a5484b33de43449ae85b7e4f104) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

autotools/base/icecc: Remove prepend from function names

2021-07-29T23:11:51+00:00

Using prepend as part of a function name is a poor choice. Whilst we're about to make the syntax explict, improve the names anyway making the conversion easier and the intent clear that this isn't an override. (From OE-Core rev: 9d002acae720b0a8e96a6734424a142b86880461) Signed-off-by: Richard Purdie

icecc: Demote "could not get ICECC_CC" warning to note

2021-05-28T05:41:02+00:00

For many components, it is perfectly correct not to have gcc or g++ in the PATH, notably when INHIBIT_DEFAULT_DEPS is set. We were getting a flood of warnings when icecc was enabled, eg: WARNING: base-files-3.0.14-r89.tait.8.6 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: base-files-3.0.14-r89.tait.8.6 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: base-files-3.0.14-r89.tait.8.6 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: busybox-inittab-1.33.0-r0 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: busybox-inittab-1.33.0-r0 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: busybox-inittab-1.33.0-r0 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: linux-libc-headers-3.14-r0 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: linux-libc-headers-3.14-r0 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: linux-libc-headers-3.14-r0 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX Demote this message to a "NOTE". It still appears in log.do_configure and friends: NOTE: Cannot use icecc: could not get ICECC_CC or ICECC_CXX (From OE-Core rev: 720254152ca57c19acf1f156d47fd47af0afa20d) Signed-off-by: Douglas Royds Signed-off-by: Richard Purdie

Revert "icecc: Don't use icecc when INHIBIT_DEFAULT_DEPS is set"

2021-05-28T05:41:02+00:00

Although this silenced the warnings, it also turned off icecc for gcc-cross and friends, binutils-cross, and importantly, the linux kernel. This reverts commit 0315aabeff8e6483b737d0e23d6841f1394ad3c8. [YOCTO #13863] (From OE-Core rev: a0e86951498db15221d8bcf6ac3ba5016b3ca144) Signed-off-by: Douglas Royds Signed-off-by: Richard Purdie

icecc.bbclass: replace superfluous "+=" with "="

2020-02-14T13:07:23+00:00

(From OE-Core rev: 8cd1150a813ba7aa395f3f62c6b91a3561e81c92) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

icecc: Export ICECC_CC and friends via wrapper-script

2019-10-23T15:30:36+00:00

By exporting ICECC_CC, ICECC_CXX, and ICECC_VERSION in a wrapper-script, and putting this wrapper-script in the PATH, the Makefiles generated by CMake or the autotools are able to function correctly outside of bitbake. This provides a convenient developer workflow in which the modify-compile-unittest cycle can happen directly in the ${B} directory. The `rm -f $ICE_PATH/$compiler` line is transitional, and can go at some later date (October 2020 or later, perhaps). (From OE-Core rev: 40d74cb1d0ddce930267e49764cacb263b244091) Signed-off-by: Douglas Royds Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

icecc: Don't use icecc when INHIBIT_DEFAULT_DEPS is set

2019-10-02T19:22:25+00:00

We don't have a compiler, so no icecc. Silences a spew of warnings of the form: do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX (From OE-Core rev: 0315aabeff8e6483b737d0e23d6841f1394ad3c8) Signed-off-by: Douglas Royds Signed-off-by: Richard Purdie

icecc: blacklist pixman

2019-09-16T22:02:45+00:00

pixman declares prng_state as `omp threadprivate`, causing linker errors: prng_state: TLS reference mismatches non-TLS reference (From OE-Core rev: a95953fccc7c05650710e45103c3e9fa06d1ff4d) Signed-off-by: Tim Blechmann Signed-off-by: Richard Purdie

icecc: blacklist systemtap

2019-08-28T10:31:21+00:00

compiling systemtap with icecc causes the following build failure > build/tmp/work/silvermont-64-poky-linux/systemtap/4.0-r0/recipe-sysroot/usr/include/python3.7m/modsupport.h:120:66: note: in definition of macro 'PyModule_AddIntMacro' > HelperSDT/_HelperSDT.c:145:34: error: 'PyTrace_RETURN' undeclared (first use in this function); did you mean 'PyTrace_C_RETURN'? (From OE-Core rev: 66719424096eb0d3470647579364efe1556dc7b6) Signed-off-by: Tim Blechmann Signed-off-by: Richard Purdie