meta-toolchain-qt: Fix environment population

The generation of the environment has change since the change to use a
meta-environment canadian package in the OE-Core, the SDK environment
setting has been broken. This uses the new subscript environment to
fix it.

(From OE-Core rev: e7b9e1df19062cfbcd72c90295829424cae6fbed)

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

toolchain-scripts.bbclass: Allow sourcing of subscript for environment

Sometimes we require extra environment settings to be available on the
environment for proper SDK work. This were done, in past, using
'_append' tasks however with the split of the environment in a
canadian package this has been broken.

The easier and more flexible solution is to use environment subscripts
which are sources by the main script. These are now looked at:

 $OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh

and sourced.

(From OE-Core rev: 457291f2ca084d1f43c0cca2175b448a22761887)

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: fetcher: fix BB_STRICT_CHECKSUM datatype check

Forcing strict to be a string, to avoid problems when performing comparisons

[YOCTO #6762]

(Bitbake rev: b8ed2098bdea2afd93ab4e3e1b834f3a31cb60de)

Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

package_ipk.bbclass: Fix SRC_URI whitespace handling

The SRC_URI may contain whitespace, but be otherwise empty.  This can happen
in the case:

MYSRC = ""
MYSRC_arm = "file://myarm.patch"
SRC_URI += "${MYSRC}"

Unless we strip blank spaces, to determine if it is empty, we can end up
generating a "Source: " line which in invalid.  This leads to the error:

  invalid Source: field is speified in the generated CONTROL file

(From OE-Core rev: 16cedc3bce6fc37543e9ef053cd7c589e523ca1c)

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bash: update and CVE-2014-6278 fix

Update both bash 3.2.48 (to 57), and bash 4.3 (to 30) to fix the remaining
'shellshock' security issues, CVE-2014-6278.

(From OE-Core rev: a2709547644ae417fbd5435e1372068c7cd5db4c)

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

linuxdoc-tools-native: Makedoc.sh uses /tmp and fails w/ noexec mount

The Makedoc.sh script uses the following line to set TMPDIR

export TMPDIR=`mktemp -d ${TMPDIR:-/tmp}/ldt.XXXXXXXXXX`;

and then later in the script:

chmod u+x $TMPDIR/linuxdoc

Since TMPDIR is not set the script will default to /tmp and if /tmp
is set to noexec (which is becoming more common), the chmod call fails.

(From OE-Core rev: 3a8b8812ac1b9a724f11b2011f8ee3416ac3d4df)

Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

package.bbclass: Reverse runtime symlinks should be tied to package generation

In case a package is not generated (is empty and does not has allow
empty flag set) the package data regarding reverse runtime dependency
shouldn't be done.

This were causing a false-positive in the meta-fsl-arm layer, when
building mesa, as:

,----[ Error during build of MX53 in meta-fsl-arm ]
| ERROR: The recipe mesa is trying to install files into a shared area
|  when those files already exist. Those files and their manifest
|  location are:
|    /.../build/build/tmp/sysroots/imx53qsb/pkgdata/runtime-reverse/libopenvg-dev
|    Matched in manifest-imx53qsb-amd-gpu-x11-bin-mx51.packagedata
| Please verify which recipe should provide the above files.
`----

Fixes [YOCTO: #6795]

(From OE-Core rev: 9ef8728514b02dd2e18e87645298d9ec2e8a785a)

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

LTP - realtime tests - fix bad robust mutex conditionals

The tests for robust mutexes contained conditional clauses which failed in
autoconf and/or used nonexistent variable names.  Modified these
conditional clauses to use only the variables actually created by
LTP autoconf for this purpose.

(From OE-Core rev: c0189ef8b58b1e63e227c5040cb1c9e915f225c2)

Signed-off-by: Gary S. Robertson <gary.robertson@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

LTP - realtime tests - fix bad PI mutex conditionals

The priority inheritance tests for mutexes used conditional variables
which were non-existent.  Changed the conditional clauses to use the
variables which were actually generated by LTP autoconf for that purpose.

(From OE-Core rev: 812114ad23def92306fbf9f7afb03cee4cbd10d4)

Signed-off-by: Gary S. Robertson <gary.robertson@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bash: Upgrade bash to latest patch level to fix CVEs

We upgrade bash_4.3 to patch revision 29, and bash_3.2.48 to 56.

There are numerous community bug fixes included with this set, but the key
items are:

bash32-052      CVE-2014-6271                           9/24/2014
bash32-053      CVE-2014-7169                           9/26/2014
bash32-054      exported function namespace change      9/27/2014
bash32-055      CVE-2014-7186/CVE-2014-7187             10/1/2014
bash32-056      CVE-2014-6277                           10/2/2014

bash43-025      CVE-2014-6271                           9/24/2014
bash43-026      CVE-2014-7169                           9/26/2014
bash43-027      exported function namespace change      9/27/2014
bash43-028      CVE-2014-7186/CVE-2014-7187             10/1/2014
bash43-029      CVE-2014-6277                           10/2/2014

(From OE-Core rev: 43deeff0c6b0ea7729d3e5f1887dfd1647dea1da)

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

pseudo*.bb: update to pseudo 1.6.2

pseudo 1.6.2 fixes problems with 64-bit inodes and some underlying issues
involving file renames that could occasionally cause very strange behaviors
files being deleted, linked, or renamed, mostly observed as strange
recovery if an inode got reused.

(From OE-Core rev: b2c6a032d6e5deb07e76ed75fcd0931fad6a748c)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

cross-canadian: Disable the packagedata stamp-extra-info

Similarly to native/cross disable this since otherwise the packagedata
can be marked as machine specific and if you switch machines
which share an architecture, you'll get toolchain overlapping files
errors.

(From OE-Core rev: 96d557be3dedd6aea6199b3d28fbb7f5549fad69)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

meta-environment: Deal with machines which change TARGET_OS

Some machines change TARGET_OS, cross-canadian resets this which
is not what we want in this specific case. This fixes spe toolchains
for example.

(From OE-Core rev: 0038634ee6e2b6035c023a2702547f20f67c103a)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gcc-runtime: Add linux-gnuspe symlink to fix c++ headers

Some architectures can mix different TARGET_OS values, in most cases
we just use one but in the ppc case, can use two different values. In this
case, to use one toolchain with both, we need to ensure the symlinks exist.

This isn't ideal but does fix the ppc toolchains for the release, after
which better ways of handling this can be investiaged. Without this, failures
in the C++ toolchain are seen.

(From OE-Core rev: 112641117f1152bad8a806f1aa872a67575d5316)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

kernel.bbclass: enable a link for external module building

Even though the kernel-dev package provides the required support for
building external kernel modules on the target, some commonly used scripts
and utilities fail as they are not finding the kernel module build support
files at the desired location.

Create the /lib/modules/<kernel-version>/build link on target pointing to
the sources provided by the kernel-dev package, to fix the issue.

Fixes Bug:
[YOCTO #2968]

(From OE-Core rev: aafa4bc896eb944aa4fc406807dd7e02f4b9b7ba)

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

kernel: Added bc-native as DEPENDS

The makefile checks for bc during for compilation

[YOCTO #6781]

(From OE-Core rev: c067e52cffe002de3b39aa1bced308dd532859c1)

Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

adt-installer: Fix to work with meta-environment changes

There is a proper sysroot specified in the meta-environment script now,
which isn't a bad thing. We adjust the sed expression to cope with this.

That means the SDK installations in non-default paths start to work again.

(From OE-Core rev: 3be7b59893ed77f63eeca35b686df06a1dafb53d)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

uninative-tarball: Update eglibc -> glibc

(From OE-Core rev: 2b85b3f33af5157cd4b6f8a6dc737015c85018c3)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

oeqa/dmesg: Whitelist usbhid failures

We fixed these in parselog but not here. This test really can just be
deleted now really.

(From OE-Core rev: c598dbdbaebf95cc26e95138b4c3fcb15af67a88)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

adt-installer: Set INHIBIT_DEFAULT_DEPS

We've been seeing an issue on the autobuilder due to the way it builds
package feed indexes. Packages get copied into the nightly build which
then creates indexes however this is done without the knowledge of
sstate. When adt-installer is built, it has dependencies on the toolchain
and when ipk files already exist, the build throws errors.

Since this recipe doesn't need a toolchain, we can remove the dependencies
to work around this for now. I'm not particularly happy with what the
autobuilder is doing but that is a post release issue.

(From OE-Core rev: 6055263b28698a2c79c1605aca2f3810d2aa140d)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

build-appliance-image: Update to dizzy head revision

(From OE-Core rev: 8e3e36bcafcb7a97006f8cc49e51c3a5b8e51a65)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

oeqa/parselogs: Ignore qemu usbhid errors

These are harmless from the USB pointer device we install, ignore them.

(From OE-Core rev: f5bdf41e78ff378fe23d8ba1543917bc64def62f)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gtk+3: Add missing MLPREFIX

Without this each tries to provide libgtk-3.0 which directly conflict when
using multilibs.

(From OE-Core rev: afc4412f9ff14dd45aba6a47bfc87e703f3c4763)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

meta-environment: Set libdir correctly to fix PKGCONFIG entries

Currently libdir is coming from cross-canadian which is incorrect. We
need to reset this to target_libdir so that the toolchains contain the
correct value.

(From OE-Core rev: 41f8f32c8da705ead464ee69bc5a1e120b137693)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

apt: apt-key binary was not being installed, including it in the installation

[YOCTO #6476]

(From OE-Core rev: d31fc181005734953c70ba9338d6a5eb88b6fe8b)

Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

perf: fix undefined pr_* routines

When cross compiling libunwind support for ARM a missing debug include means
that pr* macros are not expanded, and hence link failures on the undefined
functions.

Since we must be compatible with many versions of the kernel and perf, we
sed the proper include into the files, while the permanent fix goes upstream
to the mainline kernel.

(From OE-Core rev: 81bb7a163d7e3c0bdcc72894ef731521d58edf90)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

linux-yocto/3.17: update to v3.17-rc7

Updating the 3.17 tree to the rc7 release.

(From OE-Core rev: 6957ce3e726de5dbdcf3e94c5919916d88736e8d)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

linux-yocto/3.14/3.17: allmodconfig/allyesconfig build fixes

It was found that some of the recent feature merges for 3.14/3.17 are
not allmodconfig and allyesconfig safe.

Since this is a basic test before kernel patches are submitted, we've
fixed the features to meet this standard.

Integrating the following fixes from Paul Gortmaker:

  b4213d81ea3f fat: don't use obsolete random32 call in namei_vfat
  2cc7eba15c1f cryptodev: stomp dynamic version numbering for in tree builds
  5d1dda7aae4b Target/dif: Introduce protection-passthough-only mode
  3d9772d8facf vhost: fix compile fail due to reallocated acked_features field.
  efad59d3a174 virtio-scsi.h: Add virtio_scsi_cmd_req_pi + VIRTIO_SCSI_F_T10_PI bits
  902f34d36102 aufs: apply aufs3-mmap.patch from 3.14 branch
  30efc2e9484e aufs: import core files from aufs3.14 20140915
  e42f87adef10 Revert "aufs: aufs3-mmap.patch"
  a818774bd338 Revert "aufs: core aufs filesystem"

(From OE-Core rev: d1c40ccb522b5c5a61d5faab7e0f65491e201a27)

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

linux-yocto/3.14: revert BFP feature, and fix intel-common -rt

The BPF feature is causing build failures, so we are reverting it
for now.

In this update we also have the following fix for -rt:

  fb6271a942b5 intel: Remove the standard ktype nesting

(From OE-Core rev: 57a82d3bf0bf34bba9d0801057a4b8a6aa230228)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

linux-yocto/3.14/3.17: menuconfig and cryptodev

Two issues were reported with the 3.14 kernel, cryptodev was not properly
building and working on all devices, and menuconfig was not working on some
hosts.

To fix this, we pull in the latest cryptodev updates, and restore an old
ncurses patch for menuconfig.

(From OE-Core rev: 35f932314541067b16b60ed5bc054a80f973dd35)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

kern-tools: fix overly greedy path relocations

During patch processing a consolidated set of configs, patches and directives
is created under the kernel source tree being modified. During that processing,
absolutely paths are converted to relative. It has been found that if directories
are sufficiently similar, like so:

  /path/to/my-linux
  /path/to/my-linux-3.16

The processing will chop to much of some paths, resulting in invalid relative
directories (like -3.16 in the above example).

Importing the following two kern tools fixes for the issue:

  23345b8846fe kgit: retain trailing / in directory processing
  a8cf93a3bc94 kgit-s2q: move subject and diffstat mismatch to 'fuzzy' matching

[YOCTO: #6753]

(From OE-Core rev: 660c90458e8b4114e4a8deb920e44263e03a1ec6)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

build-appliance-image: Update to dizzy head revision

(From OE-Core rev: ae8319fb460b5d588044f6b00bf73255773f4ff0)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

perl: Improve sysroot regexp

When rebuilding libxml-parser-perl with a change to libdir, you see strange
build failures due to MakerMake looking in strange library paths. The error
is obtuse and hard to track down. I'm therefore proposing we change the regexp
once and for all to resolve the issue. Currently it only does a replacement
once, this change ensures it always gets set the correct value upon rebuilds.

(From OE-Core rev: 2c1c70eef4df66a0208f60ee51bd36d8f794144e)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gdb-cross-canadian: Add to sstate whitelist

The various gdb variants overwrite in datadir so whitelist this for now, they
are the same files and this is not an issue.

(From OE-Core rev: 472efca12108d26201d2236ff436a08845313f48)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gtk-doc-stub: update to latest commit

* fix build for packages with AC_CONFIG_MACRO_DIR set but not shipping macros
  causing:
  | ln: target 'm4/' is not a directory: No such file or directory
  | cp: cannot create regular file 'm4/': Not a directory
* In 2012 version was increased to 1.1

(From OE-Core rev: 748056672b2dc8d65107dde84c83171d9ba53091)

Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

mx: remove version from patch directory

(From OE-Core rev: 11bc6489d534ecf904b04ab9e9b6415d4415492a)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

rpm: add version 4.11.2

add patch to remove db3 from configure.ac
add inherit pkgconfig

(From OE-Core rev: 9a17f938e738a16a1ef9a00be6a8317d71f92573)

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

python-smartpm: Add patches for rpm4

Add DEPENDS for python-rpm package from either rpm4 or rpm5

Extend the smart-dflags patch to catch an exception if the api does exist

(From OE-Core rev: 756e499a95cc928688684cc52bde8e31306e6bbc)

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

rpm5: add python-rpm PROVIDES

Since python-smartpm depends on python-rpm, we should provide here as appropriate.

(From OE-Core rev: a3598f87bd22354cce2f2be06f09c2b24f2adb63)

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

nss: nss.pc is not target specific

RPM4 requires an nss-native component

(From OE-Core rev: f70efca58e9411feb251c9d00066f8631b167004)

Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

tzdata: update to 2014h

(From OE-Core rev: 1bfefe647911b46efa2f7aaf84dc02c25a9a158d)

Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

tzcode-native: update to 2014h

(From OE-Core rev: c50e5f1bc8c597ad055a243bef4591a7cfee6355)

Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

deb_packaging: Added support for multilib

The Package Manager implementation for deb didn't
take a look about multilib enabled variants.

Changes are made for generate apt.conf, sources.list and
debian repo index Release and Packages files.

[YOCTO #1502]

(From OE-Core rev: b5fb879b351cc23977f3e441f758101551297566)

Signed-off-by: Anibal Limon <anibal.ezau.limon.belmares@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

ltp: Add additional m4 path to autoconf.

The ltp code has some m4 macros that are deeper than the default depth
that the directory depth the autotools.bbclass checks. This causes some
macros to not be found and for supported features to not be enabled.

This patch adds the extra m4 path to the autoconf arguments.

(From OE-Core rev: 4d8fa4b7a02d1d53f75943607df7e8126e6dbeb8)

Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

sstate: Add rpm allarch to overwrite whitelist

The packagegroup allarch rpm files for multilib can overwrite each other since
they are in theory indentical (in contrast to the other backends). We therefore
need to whitelist this to avoid build failures now this overwrite failure
is fatal.

(From OE-Core rev: d59ade0ca2cf629937434fa423dfbf35ce1209fc)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

ltp: add PACKAGECONFIG for numactrl

(From OE-Core rev: 4c7873552e13dfdba96afca7562c398d2966ca71)

Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

squashfs-tools_4.3: modify SPDX_S variable

Modify SPDX_S to the source tree of squashfs instead of ${S}.

(From OE-Core rev: 1d79bea9dadd7e78fd558046497cb48b7d9b46e9)

Signed-off-by: leimaohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

icu.inc: modify SPDX_S variable

Modify SPDX_S to the source tree of icu instead of ${S}.

(From OE-Core rev: 69c8f17eb35ef42dcf538e39b80802c0a70548f9)

Signed-off-by: leimaohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

db_6.0.30: modify SPDX_S variable

Modify SPDX_S to the source tree of db-6.0.30 instead of ${S}.

(From OE-Core rev: 2e9d5ef3b58c298757190c6e13e5300fa1e9ed45)

Signed-off-by: leimaohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

db_5.3.28: modify SPDX_S variable

Because $S is set to sub-directory of db-5.3.28.
So modify SPDX_S to the source tree of db-5.3.28 instead of ${S}.

(From OE-Core rev: c86137e2fc9faee1146e41fa4b7c1d284dd6673f)

Signed-off-by: leimaohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

spdx.bbclass: Add SPDX-specific source tree variable.

Add SPDX-specific source tree variable for recipes where $S is a subdirectory of
the source tree.

[ RB - add a comment for SPDX_S ]

(From OE-Core rev: 41784ad0588b4aba6897d6e9e0efd0314ab19747)

Signed-off-by: leimaohui <leimaohui@cn.fujitsu.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

oprofile: eliminate git recipe

oprofile_git.bb does not unpack because it stills uses
INC_PR, which is no longer expanded.  If one fixes that,
patching fails.  Since there is another, later, version oprofile
recipe, we might just as well get rid of this one.

(From OE-Core rev: 0ef8390425ef5722c00074e962e64e70b7ff8598)

Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

rootfs.py: catch inner warn message

Package managements (smart/apt-get/opkg-cl) generate some warn messages
to stdout, and we need to catch them and output by bb.warn.

Here is an example, while invoking smart to attempt install doc packages,
if install failed, it generates warn message to stdout.
...
|warning: Can't install util-linux-doc-2.24.2-r1@i586: Can't
install util-linux-doc-2.24.2-r1@i586: no package provides info
...

The fix catches it and outputs:
...
|WARNING: log_check: There is a warn message in the logfile
|WARNING: log_check: Matched keyword: [warn]
|WARNING: log_check: warning: Can't install util-linux-doc-2.24.2-r1@
i586: Can't install util-linux-doc-2.24.2-r1@i586: no package provides
info
...

(From OE-Core rev: f8d725f49f2be4b854f523a5ee3a5c4357e67e30)

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

alsa-utils: interrupt streaming via signal

aplay/arecord (alsa-utils v1.0.28) cannot interrupt streaming
via CTRL-C. Fixed the issue by reverting buggy patches and
properly handling 'in_aborting' flag in appropriate functions.

(From OE-Core rev: 8e4ab29924c8c5fe2a79e8b0ca41fa45cc8e94a1)

Signed-off-by: Anant Agrawal <Anant_Agrawal@mentor.com>
Signed-off-by: Mikhail Durnev <mikhail_durnev@mentor.com>
Signed-off-by: Muzaffar Mahmood <muzaffar_mahmood@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

kernel-yocto.bbclass: Fixup shell condition test syntax error

A warning is issued when run about an unexpected operator due to a
syntax error with an extra if empedded in the shell conditional. Remove
the extra if.

(From OE-Core rev: f0566e127abc7bb90588b2a8bee12ad3e7d35b3e)

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

lttng-modules: fix build issues with the v3.17 kernel

The lttng-modules recipe was failing for meta-intel BSPs with the v3.17 kernel.
These BSP kernels were enabling some of the audio codec drivers, whose
structures are changed recently, causing mismatch with lttng-modules code
expectations. The qemu machines did not see this issue as they were not
enabling these sound codec kernel configuration.
  Fix the build issue, by changing the lttng-modules code to match with
the structures used by the v3.17 kernel. The code is conditional on the
kernel version, that way it keeps working with the older kernel versions.

(From OE-Core rev: 1854d6c2e6dda4fd6900399d827413fcc1e1aef6)

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

apt: fix for CVE-2014-0478

APT before 1.0.4 does not properly validate source packages, which allows
man-in-the-middle attackers to download and install Trojan horse packages
by removing the Release signature.

http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0478

(From OE-Core rev: 3dd692fcf2b0c11731b3f30abdf2b1878458a898)

Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com>
Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

base.bbclass: add SRCREV to do_fetch() hash

Without this changing just the SRCREV won't re-fetch unless you embed the SRCREV
into PV.

The downside here is that every hash changes, so this causes a full rebuild.

(From OE-Core rev: a414b17e1d783ad68a2d0f7d5922967449c05797)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

staging: Exclude MULTI_PROVIDER_WHISTLIST from do_populate_sysroot

If you switch between multilib and non-multilib builds, pretty much
everything rebuilds due to the use of MULTI_PROVIDER_WHITELIST
in do_populate_sysroot. It doesn't need to do this so exclude
that variable for checksum purposes.

(From OE-Core rev: 7f3a44ff30d07083ee8c4e2b7ac91dc6a9c8857b)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

meta-environment: Two critical fixes to unbreak toolchains

Firstly, when multilib builds were being used, the same output files
were used in each case, being overwritten each time due to the fact that
REAL_MULTIMACH_TARGET_SYS has been expanded. Instead of immediate
expansion, just use assignment. This overrides the problematic define
in toolchain-scripts.bbclass but allows the multilib code to work.

Secondly, the target sysroot was being defined incorrectly which
this patch fixes. This was breaking the toolchains.

(From OE-Core rev: 17229152453a8633b2cd63b429f98cc7c192f300)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

babeltrace: Add missing bison/flex depensencies.

* babeltrace do_configure failed due to missing flex/bison
  dependencies.

(From OE-Core rev: f7ffeb39d42c4b99dfd1522af00a674d38ca0579)

Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

tcmode-default: Define PREFERRED_VERSION for binutils-native

When using other toolchain layers, it does not pick
the OE-Core version eventhough not specified, its because
we did not pin it.

Change-Id: Ic47fd607a2a6535dd157d8afdd004197d2a6f60b
(From OE-Core rev: be1e7909abb1fc27087b2b99b183da260f9653af)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

boost: fix atomics for armv6

meta-raspberrypi and some other systems are ARMv6k but tell OE that
they're ARMv6 which doesn't fully support non-word atomics.  armv6k
does, but Boost didn't handle the recognition correctly in the 1.56
release.  Backport the patch that fixes the build.

See: https://svn.boost.org/trac/boost/ticket/10446
(From OE-Core rev: abf8baba208927a0156bb4b743614c6252f2af21)

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: toastergui fix size rendering in dirinfo page

We fix the rendering of the size field in dirinfo-related pages
by directly calling filtered_filesizeformat and not rendering
it through the template engine.

Additionally, we enable error dumping into logs if an
Exception happens.

[YOCTO #6669]

(Bitbake rev: afa2431c21b8271b05dc4cca4265f98d9f338007)

Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bash: Fix CVE-2014-7169

This is a followup patch to incomplete CVE-2014-6271 fix
code execution via specially-crafted environment

Change-Id: Ibb0a587ee6e09b8174e92d005356e822ad40d4ed
(From OE-Core rev: 76a2d6b83472995edbe967aed80f0fcbb784b3fc)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

nss.inc: Fix LICENSE

From reading the COPYING and various license headers, the nss
LICENSE was incorrect. It's actually MPL-2.0 (not 1.1) with a
few different Or instances.

(From OE-Core rev: ed3e7d4a584d836887d798e0f30339808d09804f)

Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bash: fix CVE-2014-6271

CVE-2014-6271 aka ShellShock.

"GNU Bash through 4.3 processes trailing strings after function definitions in
the values of environment variables, which allows remote attackers to execute
arbitrary code via a crafted environment."

(From OE-Core rev: 798d833c9d4bd9ab287fa86b85b4d5f128170ed3)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

curl: add a PACKAGECONFIG for librtmp

Otherwise this is a non-deterministic build dependency.

(From OE-Core rev: 8521d4d6b73c93ae60cca3d04673cdd02c27446c)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

licenses.conf: remove link to deleted License_Audit wiki page

(From OE-Core rev: de57a1ab92f975b020b9119e48c6cc8fc8393992)

Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

meta-toolchain-qt: fix up old reference to Nokia and typo

The SDK is now called Qt SDK.

(From OE-Core rev: 7c5d520d24f40d844e60540663b34b47d9d8f21b)

Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

qt4: fix bug tracker URLs for patches

(From OE-Core rev: 6523113a547042fc34110835fb658ee064d84a5f)

Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

qt-mobility: fix source URL

The source is no longer available from the original URL.

(From OE-Core rev: 502b0d1f68ad7668df153d3cfb8ca35f02313c1e)

Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

man/texinfo: conditionally add gzip/bzip2/xz to RDEPENDS

Conditionally add 'xz/bz2/gzip' to info/man's RDEPENDS
according to DOC_COMPRESS.

[YOCTO #6750]
[YOCTO #6751]

(From OE-Core rev: 610220a95f9ef78590acb1b8f18abc984464da96)

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

texinfo: fix QA Error while doc compress enabled

While doc compress enabled, ther is a QA issue:
...
ERROR: QA Issue: texinfo: Files/directories were installed but not shipped
  /usr/share/info/info.info.bz2
  /usr/share/info/info-stnd.info.bz2 [installed-vs-shipped]
...

(From OE-Core rev: c550cafa29b8621ef20481c873c5658f9ff6a602)

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

git: add Git perl module to perltools package

Git perl tools such as add--interactive load the Git module at runtime.
A previous patch to eliminate a QA error by deleting it instead of
packaging it was incorrect.

    beaglebone[62]$ git add -i
    Can't locate Git.pm in @INC (you may need to install the Git module) (@INC contains: /usr/lib/perl/5.20.0 /prj/pab/Utils/lib/perl5/linux-arm/5.020000 /prj/pab/Utils/lib/perl5/ /prj/pab/Utils/lib/perl5/site_perl/linux-arm /prj/pab/Utils/lib/perl5/site_perl /etc/perl /usr/lib/perl/site_perl/5.20.0/ /usr/lib/perl/site_perl/5.20.0 /usr/lib/perl/vendor_perl/5.20.0/ /usr/lib/perl/vendor_perl/5.20.0 /usr/lib/perl/5.20.0/ /usr/local/lib/site_perl .) at /usr/lib/git/git-core/git-add--interactive line 7.
    BEGIN failed--compilation aborted at /usr/lib/git/git-core/git-add--interactive line 7.

[YOCTO#3780]

(From OE-Core rev: 804f8e650f433d00907ec04282c22aaff2e5c044)

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

oeqa/utils: Added filter to LogResults decorator to enforce custom log level.

(From OE-Core rev: 65c97d4abd26f38917cd89b5f50f7299221b2123)

Signed-off-by: Lucian Musat <georgex.l.musat@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

sstate.bbclass: update the timestamps after install

Update the sstate file's timestamps after it is installed, it will be
very useful for removing the old sstate file, especially, it's not easy
to remove when use the shared SSTATE_DIR, we can easily remove them with
this change, for example:

$ find state-cache -type f -ctime +10 -exec rm -f {} \;

Will remove the sstate file which isn't used by recent 10 days.

We can use the -atime, but it is not always available, for example,
when mounted with "-o noatime".

The touch is a very light weight action, and the
scripts/sstate-cache-management.sh also requires this.

(From OE-Core rev: bbee747466a6947319cff2ffd676abf9432c16ae)

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gnupg: add pinentry into RRECOMMENDS

Pinentry is needed for most function of GnuPG, so add it into RRECOMMENDS

(From OE-Core rev: dc274b6325cfc6b78d51c97445b1af445ccfed93)

Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

pinentry: add recipes

gnupg 2.x.x needs pinentry to work

(From OE-Core rev: af893d747f3ee7894b2b444cf75024757f389742)

Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

dhcp: use ${PN} for SYSTEMD_SERVICES

We should use ${PN} instead of hardcoding 'dhcp' for SYSTEMD_SERVICES,
otherwise we would have 'installed-not-shipped' QA error if we are building
lib32-dhcp.

(From OE-Core rev: c3a152f946f7cb1666384fd7a214f883cbaecb56)

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

volatile-binds: use ${PN} for SYSTEMD_SERVICE

As this recipe inherits allarch, it makes no real difference whether
we are using ${PN} or 'volatile-binds'. But using ${PN} would keep
the same style with the other recipes in OE.

(From OE-Core rev: 708cc039b6cc891e466e89d2b10fcdea6c19287c)

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

acpid: use ${PN} for SYSTEMD_SERVICE

We should use ${PN} instead of 'acpid' for SYSTEMD_SERVICE, otherwise
we would have the 'installed-not-shipped' QA error if multilib is enabled
and we run `bitbake lib32-acpid'.

(From OE-Core rev: f8217853c69cf06c92b2f3885f7d49851213188f)

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

packagegroup-core-standalone-sdk-target: Add libgcov-dev to on device SDK

When a user takes coverage in gcc of SDK, it becomes the link error in SDK
because there is not libgcov.

----
ld: cannot find -lgcov
collect2: error: ld returned 1 exit status
----

(From OE-Core rev: 99b26dba6e4f5a64579f183883265498000e3104)

Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gnomebase: fix indentation

(From OE-Core rev: 103ded50380916d210e293913eebb173f014063e)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

syslog: Change unused variable declaration LOCAL=0 to LOG_LOCAL=1

This fix allows the correct appending of -L to syslogd arguments when both file and remote logging are selected.

(From OE-Core rev: ca68019760de6c5d5401be8eae7e65e7e6ca9021)

Signed-off-by: Michael Gloff <mgloff@emacinc.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

qtdemo-init: Make qtdemo startup correctly

The qtdemo can't launch via qtdemo-init initscript. Fix it.

(From OE-Core rev: bdd7a07db6b41c6c87c272d410af63c2d0251fc8)

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

perf: fix issue about package splitting

Currently, perf can't split to perf-archive, perf-tests, perf-python and
perf-perl. All files are included in perf package. Change the perfexecdir
variable to make split successfull. Add python to RDEPENDS_perf-tests.

(From OE-Core rev: 32fcc621401e7761d9b96bc5b7bef143c1c29695)

Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

libpam / xtests: remove bash dependency

There's not bash specific syntax in the xtests scripts:

  $ cd Linux-PAM-1.1.6/xtests
  # replace /bin/bash to /bin/sh and check the bashisms:
  $ checkbashisms *.sh
  No output

So the runtime dependency to bash could be removed.

(From OE-Core rev: 1917bf7aa74aa1b86756c73c56537db2591115e5)

Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gst-plugins-base: fix build failure for x86

On x86, EMMINTRIN is defined but not usable without SSE so check for
__SSE__ and __SSE2__ as well.

(From OE-Core rev: 556a19423d15c7c13f60d57528a3b880f95750b9)

Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

coreutils: selinux/flask.h should respect to with_selinux

Fixed when build with meta-selinux even with --without-selinux:
runcon.c:49:28: fatal error: selinux/flask.h: No such file or directory
 # include <selinux/flask.h>
                            ^
compilation terminated.

(From OE-Core rev: d52a606c8a75496f3b7239adc19fdb66e3ae576a)

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

systemd: disable resolv.conf symlink unless resolved is enabled

The tmpfiles configuration in systemd unconditionally creates a symlink
from /etc/resolv.conf to the location where systemd's resolved service
will place the real file.  This link is only appropriate when resolved
is enabled and running: its presence prevents connman or other systems
from providing a working resolv.conf when systemd is not assigned that
responsibility.  OE has not yet enabled systemd's networkd or resolved
by default.

There is a TODO in the systemd source to fix this, but it has not been
addressed upstream.  This patch comments out the corresponding line when
resolved is not enabled in the package configuration.

(From OE-Core rev: 7e2b05a6f59209687829225878a19a1dad8143b9)

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

sstate: Change overlapping files warning to a fatal error

When files overlap in the sysroot, something bad usually happened. We've had
two independent cases recently where a couple of months after one of these
warnings was shown, builds failed due to corruption.

This change moves the warning to become a fatal error. The complaint I've had
about this is that we need to tell the user what happened and more importantly
how to recover from it. If we could recover from it, great but the trouble is
we simply don't know what happened.

As a compromise, we can document several of the possible scenarios in the error
message. We don't normally go to this level of detail however in this case, I'm
lacking other viable alternatives.

I do believe it is important to stop as corruption occurs rather than letting the
build contunue into territory that is not deterministic amongst other things.

The complex message is followed by a simpler one in case the long message is too
much for the user.

(From OE-Core rev: 179ac7de03977b6e440409eddb2166819e07286a)

(From OE-Core rev: 4b503f25f1ef8f554d3c76d88399db379dc818cc)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: prserv/serv: Improve error message when prserver cannot bind to supplied host address

If localhost resolves to a remote address (due to a misconfigured network),
starting the pr server will fail without useful information.

To reproduce, add '<bogus ip> localhost' to /etc/hosts and run
'bitbake -p'. The error message will be:

ERROR: Timeout while attempting to communicate with bitbake server
ERROR: Could not connect to server False:

Running 'bitbake-prserv --host=localhost --port=0 --start' will fail with:

error: [Errno 99] Cannot assign requested address

Since these errors does not show the IP address of the attempted socket
binding, this results in a lot of wasted time looking at firewall rules, etc.

This patch results in the following error message if the socket binding fails:

PR Server unable to bind to <bogus ip>:0

(Bitbake rev: fae5914030bcf4c061c22fc61034c40c87b7121a)

Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: hob: Fix sstate mirrors mangling

hob was adding the redundant characters "\1" in SSTATE_MIRRORS variable. If
needed it is expected the user will add this instead so remove the code
that was doing this.

[YOCTO #6600]

(Bitbake rev: 73bf120062fc00c7e26dc4e77a7d140658d89daf)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: fetch: Extend testing of subdir unpack parameter and fix

This fixes urls of the form file://some/path/file;subdir=b. It also
adds in a couple of tests so we now tests these corner cases.

(Bitbake rev: 46306912a96444790efa9418d934dfdd36773ba1)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: fetch: SRC_URI parameter "subdir" does not work for local files

Check if the 'subdir' parameter exists and assign it to 'destdir' so that
files are copied in ${WORKDIR}/destdir. This fixes urls that are of the form
file://a;subdir=b.

(Bitbake rev: 836a986b365eb9798563ec08d90b346596de7791)

Signed-off-by: Roxana Ciobanu <roxana.ciobanu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: monitordisk: don't log when not monitoring a filesystem for inodes

Writing a log that the filesystem isn't being monitored for inode usage just
confuses users who are not aware about the nature of inodes in their filesystem,
so don't say anything, just silently disable the monitor.  In general this only
happens on filesystems which don't have a limit on inodes.

(Bitbake rev: ca93bc84ee5fb94a50c11c47e4d212d7da649e24)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

build-appliance-image: Update to dizzy head revision

(From OE-Core rev: e6c6d3fcfd2faf867e8145d25c1ba197fb9ee6b5)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: bin/bitbake: Update to version 1.24.0

(Bitbake rev: 637ce8df2658e4905fab8a0600a45505596bf472)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

sanity.conf: Update minimum bitbake version to 1.23.2 due to event changes

(From OE-Core rev: b4e2a769e8def2e78ffca3f006a0cc88407aaeda)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>