iproute2: pass CFLAGS to Makefile\

Makefile computes CFLAGS, but we can see that our
defaults get included by using CCOPTS to pass them
to make.

Upstream-Status: Pending

(From OE-Core rev: 8d71f7d33c18bb0a975eb86d602bda42db4baa2c)

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

bind: make "/etc/init.d/bind stop" work

Add some configurations, make rndc command be able to controls
the named daemon.

(From OE-Core rev: 9ad8f7c2bae021269e9a8e35f9fc44a16d23bb6f)

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

procps: pass CFLAGS to make

EXTRA_OEMAKE in the recipe currently discards the
environment CFLAGS when setting CFLAGS passed to make.
We change that to include these options.

(From OE-Core rev: 67924616963fee9cb9f2405d93c74a8cc10b6eab)

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

meta-toolchain-qte: add --sysroot option to OE_QMAKE_(CC|CXX|LD)

When building a QT application using OE_QMAKE_CC/OE_QMAKE_CXX, the
--sysroot was not included and the compilation would fail. The user had
to add the option manually which was not very user friendly. This
happened only when installing the SDK in another location than the
default one. Since CC/CXX/LD had this option already included, reuse them.

[YOCTO #3409]

(From OE-Core rev: 758f56523daa7d8c8b459757c70b50421d28b8dd)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gtk+: update to upstream version 2.24.13

(From OE-Core rev: 77cd1218bbd0760f674811eb748037deb4478db5)

Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xf86-video-omap: drop RPROVIDES/RREPLACES/RCONFLICTS

* without _${PN} suffix they are invalid:
  opkg install bash-4.2# opkg install xf86-video-omapfb
  Package xf86-video-omap-doc is already installed on root.

* it's not upgrade to omapfb driver but different driver,
  so let BSP maintainers decide which one works for their MACHINE

* without this xf86-video-omap (or -doc, -dbg, ...) can be pulled
  to image even when XSERVER clearly says xf86-video-omapfb

(From OE-Core rev: ef0f8611001c435abab60c464d31134ef027d7c2)

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xf86-video-omapfb: revive driver which actually works and is tested on real devices

* 0006-omapfb-port-to-new-xserver-video-API.patch added to port it to
  new xserver video API
* other patches just updated headers to be able to git am them

(From OE-Core rev: 58e600ae3cc955ebe30b2756540404a267c7cb26)

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xserver-xorg: disable dri2 too when building without glx PACKAGECONFIG

* it was enabled when dri2proto was built before xserver-xorg

(From OE-Core rev: 1668b4d4f373292ea4d611712ef56148ededfce5)

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xf86-video-omap: add xf86driproto dependency, drop --enable-neon and improve DESCRIPTION

* xf86driproto was missing
* --enable-neon isn't supported by omap driver
* DESCRIPTION merged from meta-ti
  http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-graphics/xorg-driver/xf86-video-omap_git.bb?id=410dc026f2ee24a2346e7563a83f0181c79809cf
* this driver also depends PACKAGECONFIG[glx] used in xserver-xorg,
  without it dri2.h sometimes isn't built (it is autodetected only
  when dri2proto is built before xserver-xorg) and without dri2.h it now
  passes do_configure but fails later in do_compile

(From OE-Core rev: 19951d2583b4ed08bbc871128d90aefd062e7da9)

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

perl: use the exported LDDLFLAGS in generate_config_sh script

The perl shared libraries did not have RPATHs set and that made
autoreconf fail when using the SDK. The LDDLFLAGS environment variable
was already exported in the recipe but was not used when generating the
config.sh.

[YOCTO #3338]

(From OE-Core rev: f6f5bdace473d0dd1dd5b8bdc7ebbb24fc6ee90d)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

kern-tools: report missing config fragments by name

If a configuration fragment was missing, the previous error output
was not clear about the error:

  | [INFO] doing kernel configme
  | [INFO] Configuring target/machine combo: "standard/atom-pc"
  | [INFO] collecting configs in ./meta/meta-series
  | ERROR: could not sanitize configuration fragments
  |    errors are logged in ... linux/meta/cfg/standard/atom-pc/config.log

but we know the name of the missing fragment and can improve the error
message to be this:

  | [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found
  | ERROR. A meta series could not be created for branch yocto/standard/common-pc/atom-pc
  | ERROR. Could not locate meta series for atom-pc
  | ERROR. Could not apply patches for atom-pc.
  |        Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto)

[YOCTO #3473]

(From OE-Core rev: 8e5dc511ffce4f4b512457dbc5d3dd510f6e4a95)

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

linux-yocto-3.4: gcc optimization config feature

Updating the meta SRCREV to include a x86 gcc optimization feature, and
its use by several BSPs:

  1c59807 meta: rangeley: Remove the shortcut path
  b5477d0 meta: crystalforest: Enable GCC inline compiler option
  ab2b874 meta: rangeley: Enable GCC inline compiler option
  8287750 meta: Add New feature for GCC optimizing

(From OE-Core rev: b042d1cce535fe88dd6f5b5c0cd1a608a27afbd6)

Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

opkg: bump SRCREV and drop applied patches

* only change upstream which wasn't in oe-core is
  http://code.google.com/p/opkg/source/detail?r=635
  and added testcase for that

(From OE-Core rev: 5fd1d515db5966f45a3b2f936f3c4225f59186e2)

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

lsbsetup: drop it

lsbsetup provides script LSB_Setup.sh to setup LSB test on image. But
script LSB_Test.sh provided by lsbtest replaces its function now. So
drop lsbsetup.

lsbsetup links /etc/localtime to HongKong zoneinfo file to make LSB
wcsftime test case pass(Yocto 1079). But the test case PASS without
this link, so remove the link.

Other 2 links are moved to packages lsb.

[Yocto 3278]

(From OE-Core rev: d991393207af90fe73de76f89ac6949ef291904e)

Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

packagegroup-core-lsb: remove lsbsetup

package lsbsetup has been dropped, so remove it from packagegroup
core-lsb.

(From OE-Core rev: 9b6ca9bd8dcf7e7d3eed9f0120a4ffcac80e441f)

Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

lsb: move links from lsbsetup to here

Because package lsbsetup is dropped, move the links created for LSB test
to package lsb.

(From OE-Core rev: 7659ad17799672d48c4d8614e830b7e60a1e971a)

Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gcc: Add --enable-linker-build-id

See https://fedoraproject.org/wiki/Releases/FeatureBuildId for the
benefits this brings.  As far as I can tell from searching the
discussion archives, there doesn't appear to be a reason not to enable
this, and the benefits are real.

Both the Red Hat Enterprise Linux 6, all Fedora, and Ubuntu Quantal
GCC builds are configured with this on.  I plan to use it in
gnome-ostree.

(From OE-Core rev: f3be2b1e5e100a953d6d7fbbb19a77a5c4d547e1)

Signed-off-by: Colin Walters <walters@verbum.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

insane.bbclass : Disable tests for unsafe references in binaries and scripts.

These test look for programs in / that depend on programs in /usr. After
a brief discussion in #oe, we decided these tests should be disabled so
we can focus on more serious QA issues.

If you are working on a system where / and /usr are on different partitions,
you should turn these tests back on and resolving the QA warnings.

(From OE-Core rev: 2fb58da56e8e7044de21fd10fe9164d204587236)

Signed-off-by: Philip Balister <philip@balister.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

binutils-crosssdk: do not set .interp size to 0x1000 for partial linked objects

When building the SDK, the final .interp section size should be set to a
bigger value (0x1000) in order to be able to change the dynamic loader's
path later. However, we shouldn't do that for partial linked objects
(when -r or -rU is used). That's because those objects will then have an
.interp section of 0x1000 even if it contains no data and when the final
linking is done we will end up with a "cannot move location counter
backwards" error. That's because the linker will try to squeeze all the data in
the .interp sections found in various partial linked objects into one 0x1000
bytes final .interp section.

[YOCTO #3264]

(From OE-Core rev: b25d0c5fe286e44ded46aefdcbe35ed259087759)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

image classes: use PN for depends, not IMAGE_BASE_NAME

Some images override IMAGE_BASE_NAME in the recipe causing targets using image-{live,vmdk} to fail.

(From OE-Core rev: 7e000fef0bf917f27dcad66dd90fae6c155c4d1d)

Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

gcc-cross: Explicitly depend on linux-libc-headers

gcc-cross cannot build without linux-libc-headers but doesn't explicitly depend on
it relying on the implied dependency through libc. With cases where pieces
can be installed through sstate, we now need this explicit dependency to
ensure builds with partial sstate work.

(From OE-Core rev: 65e5670ef429bb6c348decb1804e425f1c4d7c61)

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

sstate: Explicitly define populate_sysroot task relationships

Clean up and clarify the populate_sysroot task dependencies. Target sysroot
packages do need their dependencies installed, as do some target/cross
relationships. We can whitelist the *-initial dependencies as these are
never needed indirectly.

(From OE-Core rev: eeec307917234d97be2674beeadef71599fb1487)

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

sstate: Add a rule for target sysroot requirements from cross dependencies

For example gcc-cross depends on linux-libc-headers and needs it to be present
to build/work correctly.

(From OE-Core rev: 43ce7a1d86bf82d976ad241057a4207b1a340b3b)

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

build-appliance-image: Add explict dependency on do_unpack

The code called by do_rootfs explicitly needs the code obtained during
do_unpack. If built from sstate, it might not be present so we ensure
it is by adding an explicit dependency. This fixes build failures when
building from sstate.

(From OE-Core rev: 53d3c3caf1894e088ebf10fdf233cdf109b04da6)

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

scripts/sstate-cache-management.sh: Fix stamp handling after recent layout change

(From OE-Core rev: 8df3350d107322380582c807ccc92ea353b543ab)

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

scripts/cleanup-workdir: Adpat to new workdir layout

(From OE-Core rev: d967a498cb464c3858dc280db5e67b7e7b281b02)

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

Revert "kern-tools: report missing config fragments by name"

This reverts commit 46cc0d0a2f1486bf541c1a1b11075de3da396cc2 since
the revision in question isn't in the repository.

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

kern-tools: report missing config fragments by name

If a configuration fragment was missing, the previous error output
was not clear about the error:

  | [INFO] doing kernel configme
  | [INFO] Configuring target/machine combo: "standard/atom-pc"
  | [INFO] collecting configs in ./meta/meta-series
  | ERROR: could not sanitize configuration fragments
  |    errors are logged in ... linux/meta/cfg/standard/atom-pc/config.log

but we know the name of the missing fragment and can improve the error
message to be this:

  | [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found
  | ERROR. A meta series could not be created for branch yocto/standard/common-pc/atom-pc
  | ERROR. Could not locate meta series for atom-pc
  | ERROR. Could not apply patches for atom-pc.
  |        Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto)

[YOCTO #3473]

(From OE-Core rev: 46cc0d0a2f1486bf541c1a1b11075de3da396cc2)

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

kernel-yocto: clarify KMETA branch comments

Having a meta branch is not strictly required by the tools (and
recipes like linux-yocto-custom do not have meta branches), but the
comments in the kernel-yocto.bbclass could lead someone to think that
it was required.

This commit clearifies the comment to the following:

  # We can fix up the kernel repository even if it wasn't a bare clone.
  # If KMETA is defined, the branch must exist, but a machine branch
  # can be missing since it may be created later by the tools.

[YOCTO #3422]

(From OE-Core rev: 421a2e2523a8f2c461479a1c0d44908cc1eaca6b)

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

linux-yocto/3.4: uprobes: reinstate config options for 'uprobe' feature

bumping the meta SRCREV to import the following fix:

[
    uprobes: reinstate config options for 'uprobe' feature

    commit 17ec51adfff (meta: cleanup invalid/obselete 3.4 CONFIG options)
    removed the uprobes config options, this restores them.
]

(From OE-Core rev: 8c637986e063fcb087babecfc0192f96d3981515)

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

linux-yocto/3.0: fix virtio configuration typo

The recent tools updates in master exposed a typo that has existed
in the 3.0 kernel meta data and that breaks the build for boards still
using the 3.0 kernel.

Bumping the meta SRCREV to pickup the following fix:

[
  commit fa9b8c24e84bb9d75d08d197c84c50ce4f99c424
  Author: Bruce Ashfield <bruce.ashfield@windriver.com>
  Date:   Wed Nov 21 09:24:46 2012 -0500

    meta: fix typo in virtio.scc

    virtio.scc was referring to an invalid/incorrect virto.cfg. Fixing
    this typo fixes the build for boards still using the 3.0 kernel.
]

(From OE-Core rev: b16d72a749ac73a2bd0434f36102c00f6c476bc1)

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

python-smart-backend: Remove bogus runtime virtual/

At runtime virtual/ providers make *no* sense at all. They also break debian
packaging since the "/" character is not allowed in debian package names.

This patch removes this runtime provider selection code since it is not
workable and breaks builds.

(From OE-Core rev: 887059e9c0082cb4e7fa8b5d7c9646207acd62a6)

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

xf86-video-omapfb: drop

This driver has been superceeded by a dri omap driver. This driver
no longer builds against current versions of the xserver. If someone
wants to do the work to resurect it, that is fine but until that happens
there is no point in keeping broken code in the tree which won't even
compile. It can be easily brought back from git history.

(From OE-Core rev: 75858ad8cb19ee24f2c418515cb9d2b649a4de46)

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

xf86-video-omap: don't use AC_CHECK_FILE

Upstream uses AC_CHECK_FILE to find dri.h, but that errors out when
cross-compiling.  Until oe-core 1b0d9cb1801a8eb68c82dfcda5a1da420ac8dd83 this
wasn't a problem because we patched AC_CHECK_FILE to always pass, which was a
nasty hack.

Patch configure.ac to use pkg-config like it should, and not AC_CHECK_FILE.

(From OE-Core rev: a7fe0d17c50d9b38ce33fe39e677da349d1d358c)

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

build-appliance-image: Update to dee77eca39f406f90e60d9c5ef7a66fcc8f57dbf commit

There are a lot of improvements in Hob
and a critical fix to bitbake affecting
Build Appliance, so the poky revision
is upped to include these changes.

(From OE-Core rev: 654d5816f8ff696d42d72cfb881d5e51330a79b6)

Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

builder: fix adduser breakage with password

Build Appliance needs to have for the builder
user a password set. However, the useradd.bbclass
requires the last parameter to be the user's group
name. Previously, the password was the last
parameter to useradd command.
Fixed using the right order for parameters.

(From OE-Core rev: 29f2ae0305b9a3db9632a8fe078fedc88f89a9ad)

Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Revert "bitbake.conf: Drop obsolete FILESDIR setting"

This reverts commit d6e5ceafcaef06b8a3f9acc2aa826a40a016f913 since
the value is clearly still being used in local file urls that are
only hit at do_unpack time.

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

ldconfig/cdrtools/icecc-create-env/linuxdoc-tools/python: Set FILESPATH to find -native files

In a small number of cases we need to have ${PN} in FILESPATH rather
than ${BPN}. Rather than hurt readability for all other recipes,
set FILESPATH in these recipes so we can prune the default.

(From OE-Core rev: d61ef6ce86abe5b484a2a2602982f4ded54b3f9a)

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

classes: Drop do_package stamp-extra-info

This was needed when do_package for target recipes was target specific
however since it now isn't we can remove these stale references.

(From OE-Core rev: 1c54d8c3639659bc8cf8fa2786a1aa9ed785b723)

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

utils: Optimise looping in base_set_filespath

Calling split on the same expression, once per loop iteration is
inefficent and pointless, particularly in a function called by
every recipe during parsing.

(From OE-Core rev: 566c0e874fc1610f3f97737b5601ef22026c918a)

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

libffi: Use a more standard layout for patch files

(From OE-Core rev: cc2d2abad25a82ce722ac255a631430058f8de30)

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

trace-cmd: Simplify SRC_URI patch entry

(From OE-Core rev: dd4cf48b5a5d181d507356a845fecdbb26f37390)

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

matchbox-panel-2: Use a more standard layout for patch files

(From OE-Core rev: 7e78c5901be4d684669146b2f9ab845507156034)

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

bitbake.conf: Drop obsolete FILESDIR setting

FILESPATH is the preferred way of finding files now. Having a value
for FILESDIR which defaults to paths which will have already been
searched is pointless at best. This is the final step in letting
us drop FILESDIR support entirely from bitbake at some future date.

(From OE-Core rev: d6e5ceafcaef06b8a3f9acc2aa826a40a016f913)

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

x-load: Replace FILESDIR with FILESPATH

(From OE-Core rev: 0f7ca16c01f6206cd03d103861b77ce2b540c834)

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

opkg: Drop unnecessary FILESDIR setting

(From OE-Core rev: e869731f80d8c0059b44a7029543b8943fd07653)

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

qemu_git: Drop unnecessary FILESDIR setting

(From OE-Core rev: 8afa069778aea414856a9f538171d9ab1a2e1dd8)

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

gcc: Use FILESPATH instead of FILESDIR and cleanup/simplify

(From OE-Core rev: 4cb359182da00e661fda11a8b31e3611b0df03cb)

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

build-appliance-image: Simplify fetch/unpack execution

This provides a slightly neater way of ensuring fetch/unpack get
executed (image.bbclass marks them as noexec) since I found the
current approach harder to understand at first glance.

(From OE-Core rev: 84021fd694d0a7bb1e4f49c0f7c46a0fbd178924)

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

opkg: drop PACKAGE_ARCH setting for update-alternatives-cworth

* there is warning about update-alternatives-cworth ipk being
  overwritten in "all" feed when opkg is built for more architectures
* see https://bugzilla.yoctoproject.org/show_bug.cgi?id=3390 for details

(From OE-Core rev: 969d10d0aa5537a119ed9be9e8321dbd73d160fe)

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

distutils-common-base: Create staticdev pacakge for static libraries

(From OE-Core rev: 0c4c3ebfedd06b2b8f36747bc0c0d986f05420cf)

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

gnutls: Update to 2.12.21

(From OE-Core rev: d55c435575410e1865748ba1914443c94ef9de27)

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

libksba: Update to 1.3.0

Licensing files changes from 1 COPYING to be split.
The Code is marked LGPLv3 or GPLv2 or both in parallel

(From OE-Core rev: 96a29f346f89641eaccdb740e4d21cc4f732768d)

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

dhcp: Update to 4.2.4-P2

(From OE-Core rev: f3ca792a470437cb7fc91ca10f220a48da23d6f5)

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

libxml2: Update to 2.9.0

(From OE-Core rev: a65ea43e26866ddc60051c52b2eb226507fae346)

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

resolvconf: Update to 1.68

(From OE-Core rev: 5255d0ba318f1a24b3ea3947304f4b798a1562be)

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

mc: Update to 4.8.6

(From OE-Core rev: 27bb231a0a80ee39265ad54047d8dfb0feeeb2bc)

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

man-pages: Update to 3.44

(From OE-Core rev: cdf782fab956f5a3b43b3eb256fa57748175b802)

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

tiff: Update to 4.0.3

(From OE-Core rev: 90ad57fbd72edf44336d0ad2c2e3ec861a641fb3)

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

rt-tests/hwlatdetect: Update to 0.85

(From OE-Core rev: 42fc047daa524ce4f1b9b1b2937d75375d796e6f)

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

libdumpvalue-perl: Update to 1.17

LICENSE file updated Copyright year to 2012, no other change

(From OE-Core rev: 41f3104d1993f374e9e289ac74f821261808f833)

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

libproxy: set LIBEXEC_INSTALL_DIR

This change fixes the following QA Warning

WARNING: QA Issue: libproxy: Files/directories were installed but not shipped
  /usr/libexec
  /usr/libexec/pxgsettings
  /usr/libexec/.debug
  /usr/libexec/.debug/pxgsettings

(From OE-Core rev: b11874ef0b80f8d5150681fc2d6a0ca7a2c8fa06)

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

libtasn1: Update to 2.14

(From OE-Core rev: 74200da342a8888230a09e063bea396a8f611400)

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

multilib.bbclass: Drop populate_sdk_base exclusion

With this recently introduced exclusion, <multilib>-meta-toolchain-sdk
throws errors about missing DEPENDS that don't exist since it needs the
PROVIDES/DEPENDS remapping. This patch tweaks the class tests to fix
the errors.

(From OE-Core rev: 9cc18fe12bd8d1c73df291b4057aab6167ef6b16)

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

libcheck: Add missing rdepends on gawk and set path correctly

The new version of libcheck needs gawk and we need to ensure the paths are
not taken from the build system.

(From OE-Core rev: 120bea8043d3a05174ed034e20d9094784402824)

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

bitbake: server/process.py: Change timeout error handling

In normal usage, we never hit the timeout issue. If we do, it becomes obvious
that the current error handling is not good enough. The request may have made it
to the server and the answer will get queued. This means the next command may get
the return value from the previous command with suitably puzzling results.

Without rewriting large sections of code, its not possible to avoid this problem.
It is better to increase the timeout to several seconds giving the server a chance
to respond and if it does timeout, hard exit since recovery is not possible with the
code base today.

I'd be happy to see the structure of this code improved but this quick fix at least
stops corrupted builds from happening which has to be a good thing.

(Bitbake rev: 410c11dd10736873f2dc587fbe9119c38831e693)

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

package.bbclass: Adapt debugsrc code to workdir layout changes

With the change to WORKDIR layout, splutting PN and PV into two directories,
the debugsrc splutting code layout became suboptimal. This changes things to
include the information as it was before. Ideally this code would be written
to more generically support other layouts buts it not clear that the tools
would even support that right now so this is the best immediate fix.

(From OE-Core rev: 432cfbb403f0e864d1fad383c2bbb6f9bdb80770)

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

mesa-dri: add correct RPROVIDES for the -dev packages

The -dev packages were RPROVIDEing the non-dev names, which is clearly wrong.

(From OE-Core rev: 8d224244a016adc889be132d9994d7c517f7eae3)

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

Revert "gcc: Use FILESPATH instead of FILESDIR and cleanup/simplify"

This reverts commit 90616875b432a932415063b08497266e70c49d75. It was
never meant to be applied as its an incorrect previous development
verison of a patch in progress.

ia32-base: fix typo in XSERVER_IA32_EXT definition

(From OE-Core rev: 2948fcb2e85d71e3e686760f12e1082dc912f418)

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

yocto-bsp: upgdate configs after xf86-video-omapfb changed name

(From meta-yocto rev: 992c2c469861bfcab45a118ac9ab8887e81f1a11)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

yocto-bsp: update configs after xorg upgrade

There were some changes in the xserver-xorg upstream project that need
to be reflected here too:
 * extmod module was removed completely as it became empty;
 * DRI1, DRI2, DBE (among others) were made built-in;

(From meta-yocto rev: ed681441a2cf06dc55e71035ecbfc637ff83640d)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: knotty: Colorize knotty interactive console output

Add bold color output to log level name and standard color output to log msg
when bitbake is run from an iteractive console.  Color output is only
enabled
if the terminal supports color.

Used Jason Wessel's recommendation for transparency on verbose, note and
plain.

(Bitbake rev: 2734240da2cc150f811129a6adf6eb4b2161b204)

Signed-off-by: Seth Bollinger <seth.boll@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: hob: warnings during the build should be displayed in the Issues tab

Any issues encountered during the build (fatal or not) is displayed
in the Issues tab, and the total number of issues is changed.

[YOCTO #3376]
(Bitbake rev: 64c662ab7f09c2e867445e8ba21ea63ae014d45b)

Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

bitbake: runqueue: Allow partial setscene task coverage

When the setscene code was originally written it was thought that we'd
allow "partial" coverage. For example, if we just want to build the target
"bash:do_populate_sysroot" and its available from sstate, it makes no sense
to install gcc-cross's sstate package as its simply not needed.

Due to various other issues in the codebase, this functionality was
disabled/removed to allow the setscene code and sstate to stabilise and allow
us to concentrate on other problems.

The time has now come to enable "partial" coverage. There are two major changes
in this patch:

a) Creation of an unskippable list. This lists direct dependencies of
   build targets and hence things that cannot be skipped.

b) Addition of a handler which looks at a given setscene target and what depends
   on it and then decides whether its necessary.

(Bitbake rev: 2a937cd6a6c3110030b40bc4d85e349b85cb4db7)

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

bitbake: parse/cache/cooker: Preserve order in the file inclusion list

The data returned by get_file_depends() may me used in contexts like
checksums where order is important. The current usage of sets means
that some of the checksums can change in circumstances they should not.

This patch changes to use lists, thereby removing the problem.

(Bitbake rev: a44285fc4109236ab89f7aad0a1fc9220eec19b6)

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

libcheck: Update to 0.9.9

(From OE-Core rev: 0d856639e8c4fd31c7af222cdb2f37d6a9bec1db)

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

sqlite3: Update to 3.7.14.1

[YOCTO #3283]

(From OE-Core rev: 141ec5567de19d740e147786e25e17dd10e68001)

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

builder: Add password for user

This is needed to allow openssh to work correctly for the Eclipse
plugin to have access to the build appliance to view/modify recipes
and lauch builds

Default password is "builder"

(From OE-Core rev: ccf86771bf65e9620385abf20049f355dca391df)

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

sysstat: Update to 10.1.2

(From OE-Core rev: 6e1a032c6a2642399c5d32028c597a5affbedce1)

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

mesa: default to enabling EGL and GLES

Even on systems where Mesa has no hardware support, building the software
renderers is useful for build testing and limited functionality.

(From OE-Core rev: e79987bc4bac1d739f92790f8e9840cd02f073d3)

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

mesa: add -mesa suffix to GL packages, RPROVIDE their generic names

When Debian-renaming, all packages that provide GL libraries get renamed to the
same name, and it's entirley possible for a feed to have multiple GL libraries
in.  This obviously creates conflicts.

Resolve this for Mesa by forcing the package names to be of the form libgl-mesa,
and RPROVIDE libgl.

(From OE-Core rev: 64c77bf395310e55b4d8e0ec754fa19e9034ab35)

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

xf86-video-omap: add new recipe to follow the maintained repo

This new recipe is needed because the old driver is unmaintained. This
new recipe will follow the new repo.

(From OE-Core rev: a1d93e6383396dc3ff7cd3a4fccf27895e80af8a)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xf86-input-synaptics: add mtdev dependency

After upgrading xserver to 1.13, multitouch support is automatically
enabled in xf86-input-synaptics. Hence, the need for mtdev dependency.

(From OE-Core rev: 6b2ffa1637d9ae067753102efeb78d1eb42a0b8a)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xf86-video-vmware: Add compat API

Needed after upgrading xserver to 1.13.

(From OE-Core rev: 6eebd1699f9efba834e51a0772eab253184af914)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xserver-xorg: upgrade to 1.13.0

The patch contains several aditional changes:
 * removed one backported patch (included in the new release);
 * changed mips64-compiler.patch to apply properly;
 * licence checksum for COPYING file changed: some copyright years have
   been changed;
 * bump PR in xorg-driver-common.inc so that all input/video drivers
   get rebuilt. That's becaue the ABI changed;

The following external modules are now built-in:
 * DBE
 * DRI2
 * DRI
 * RECORD

The extmod module was completely removed.

(From OE-Core rev: 506da0d139dd470475a1d6b2dd3ae62406c36816)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

libdrm: upgrade to 2.4.40

Other changes:
 * removed a backported patch;
 * activated libdrm-omap helper layer which is needed by the latest
   xf86-video-omap xorg driver;
 * split libdrm-drivers package into libdrm-radeon, libdrm-nouveau and
   libdrm-omap, libdrm-intel and libdrm-exynos;

(From OE-Core rev: 8b100befe8dcf7523148b6fc14fa2237d07fe556)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

xkeyboard-config: upgrade to 2.7

A few extra changes:
 * changed the SRC_URI to the new, valid, one
 * added dependency of gettext (do_qa_configure detected is needed)
 * disable runtime dependency checks at configure time

(From OE-Core rev: c67b5e212244f1bac57e8491c6500656786df3a2)

Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

guilt: change upstream tgz location

The kernel.org mirror of the guilt tarball has been missing for a while
and the yocto mirrors have been keeping builds working. Switching to a
debian upstream is better than solely relying on the yocto mirrors for
serving the tgz.

(From OE-Core rev: 71f281f40e25bdd3ea052cb673d06c1a250e618f)

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

kern-tools: flexibility and usability enhancements

Updating the SRCREV to import the following changes.

 [updateme: find the board description with the highest score]

   This removes the requirement that a custom linux-yocto .scc file have
   define KTYPE <foo>, where <foo> is typically "standard". The tools can
   now match on a .scc file that only matches the board, but will still
   chose one that matches the board and kernel type, if available.

 [updateme: allow for tabs or spaces in defines]

   define KMACHINE<tab>$MACHINE was missed by the regex.

 [scc/kgit-meta: detect and avoid duplicating patching]

   To allow feature description to be included multiple times, they were
   previously split into -enable and 'patch' descriptions. With this change
   the patches will be detected as already included, and skipped
   automatically. Removing the need to do this split. It also cleans up
   the ability to warn about multiple includes.

 [kconf_check: add "verify" configuration fragment type]

   This adds the ability for a BSP to have a kernel configuration
   fragment that lists options that must be present. If they are not
   present it is a hard error. "required" is a similar fragment, but
   it adds them to the build, and audits them at the end, but does
   not abort the build if they are present. This is a minor distinction,
   but one that is useful when creating flexible, shared kernel config
   structures.

 [kconf_check: improve kernel audit report formatting]
 [kconf_check: perform validity checks on non-hardware options]
 [kconf_check: cleanups and verbose flag]

   The existing output was verbose and not always useful to the reader.
   This change makes the output more compact, audits non-hardware options
   and gives information

     [invalid (54)]: meta/cfg/preempt-rt/common-pc/invalid.cfg
        This BSP sets config options that are not offered anywhere within this kernel

(From OE-Core rev: 2d328dc0f7dd763c45444394b681d2726b4f6c83)

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

kern-tools: kconf_check: fix find warning

Bumping the kern-tools SRCREV to pickup the following change:

[
    kconf_check: fix find warning

    When searching for all available Kconfig files, kconf_check was using
    $meta_dir instead of $META_DIR. This resulted in a truncated path and
    the following warning:

      find: warning: -path $oe-path/linux/ will not match anything because it ends with /.

    Using the proper variable removes the warning and make sure that we
    do actually search all relevant directories.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]

[YOCTO #3226]

(From OE-Core rev: 5999ccebc7b071737f82709467e2a2ec152240f6)

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

linux-yocto/3.2: update to v3.2.32 and 3.2.32-rt48

The 3.2 kernel was lagging behind on kernel.org -stable and -rt
updates. Even though no 1.3 BSPs directly use this kernel, it should be
updated for those that may use it.

Sanity test on qemu* for -rt and standard builds.

(From OE-Core rev: 7ad1c853e252bea024043dc79d89405178393c09)

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

linux-yocto/3.4: v3.4.17, v3.4.18, -rt and config changes

Bumping the linux-yocto/3.4 SRCREVs to incorporate the following updates:

  - v3.4.17
  - v3.4.18
  - 3.4.18-rt29

Also incorporating the following meta branch config changes:

  5bd6d0d rangeley: update include to use the new intel-dpdk feature
  4b277c2 dpdk: Add feature Intel DPDK
  3905e74 meta: rangeley: Enable Zlib Compression
  194c5f1 meta: Add a new feature for Zlib
  14cb04d meta: rangeley: Enable AES feature
  8e4dbf6 meta: Add new feature for Ciphers
  7e75c1f enable IPv6 Router Preference (RFC 4191) support
  dfd56d1 Create IPv4 and IPv6 IPSec fragments
  0a85061 rangeley: Add smp support
  1190856 rangeley: Add efi support
  b262e38 rangeley: Add PCI features
  80c9084 rangeley: Add uio and hugetlb support

(From OE-Core rev: 7cc39567cc91955eb3014da6fdbafffa5c3148c7)

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

linux-yocto/3.4: bump kver to v3.4.16

The -stable 3.4 kernel has updated versions, so we import 3.4.16 and
make that our new baseline.

(From OE-Core rev: c476046368ed87a400b3a2fd4344fc48aacc0dbc)

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

linux-yocto/3.4: efi/mmc fixes and fri2 updates

Updating the 3.4 SRCREVs to pick up the following two fixes:

 218bd8d efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)
 b6d08f7 mmc: sdhci: Use DBG() instead of pr_warning() on large timeout

And the following meta branch config updates:

 68a635b fri2: Disable GPIO_PCH for preempt-rt
 2ec32d5 fri2: Add fri2-tiny support
 a7b9607 fri2: Required boot config for fri2
 bed2080 fri2: Remove graphics options from the core fri2 description

(From OE-Core rev: dbd49c9157f933fec9147280a48ce3cda7a697eb)

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

linux-yocto/3.4: nfsd, pci, fishriver and rangely config changes

Updating the 3.4 meta branch with the following configuration changes
and additions:

0541ba5 meta: Rangeley Machine Created
9e3bdb7 meta: Add nfsd kernel features
da9b37d CrystalForest: Enable PCI extended config space for CrystalForest Machine.
628cbe9 meta: Add a new feature for PCI devices.
9c3a2b3 meta: fishriver: remove meta-data

(From OE-Core rev: c11bf4359697f654ff38a32bda5eae71b097d3b8)

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

license: We need to run this task before do_build, there is no dependency on do_package

This change means we have more flexibility about when to schedule the license
task and if it changes, we don't repackage everything (which is pointless).

(From OE-Core rev: ee1293446936c5444ece42b60e3ab94189b2fbc3)

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

bitbake.conf/sanity: Separate versions and PN stamp components into separate directories for WORKDIR and STAMP

This means some of the hacks we have to tell where the package name ends and
the version starts in the directory layout becomes obsolete, simplifying the
work of some of the cleanup scripts. It also makes the layout slightly more
intuitive to the user.

It does force a rebuild onto the user but it will reuse sstate successfully.

(From OE-Core rev: 05075cf3138d1c61f5cf4fe0e1a4587acc00c692)

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

image.bbclass: Add missing dependency on do_package data

Since the packaging functions now reference the pkgdata files written out during
do_package, we need to reference this dependency explicitly.

(From OE-Core rev: 1e9c9d164f8d12c8de205e04bf7c1dae3660f12a)

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

sstate: Implement a setscene dependency validation routine to allow skipping of some sstate installation

This is a first attempt at logic to determine when a sstate dependency needs
to be installed and when it does not. Its a start at the logic and errs on the
side of caution, as it gets wider testing, we can refine the logic as needed.

This code should allow a significant performance speedup to certain workflows, for
example "bitbake xxx-image -c rootfs" will not populate the target sysroot.

(From OE-Core rev: b43faba37816817edc5240a139361d16e07c6131)

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