Added "October 2014" to table for all manuals that have the
table.
(From yocto-docs rev: 3f9ceb4dd2397fe907bf701c842277eb65d11a56)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reversed order of the list presentation and re-worded the static
library sentence.
(From yocto-docs rev: 5c32730550629527f6ceb2140df31a097f7a6081)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
3.17 is ready and stable to be used as the default for the qemu* BSPs,
so we update their preferred version to reflect this.
(From meta-yocto rev: 7d6a692ab48e793ec2af79303d160ddb4fca324d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The oe-core BSPs have been udpated to 3.14.19, so we follow suit with the
reference BSPs.
(From meta-yocto rev: 072b9dc5d0643c397d053bb00e541be5c285b9cd)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
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>
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>
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>
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>
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>
I updated the section to have two lists of features. One list
is for features that work only when you inherit the core-image
class. The other list is for features that are available for
all images regargless of inheriting this class.
(From yocto-docs rev: 9d1bcab2a9264e64db2dec66247aaf55493ae362)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list of features in the section was out of sync with the list
of features shown in the comments of the core-image class.
Additionally, four of the features are available to all images
regardless of whether or not the core-image class is inherited.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: e4821fd0a63e906da8b1ff015fb4970e5e62d667)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a space-separated list and not a comma-separated list.
(From yocto-docs rev: 23cf09ac128289e878bbc056e28060008ab5217c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a small sentence to note that this class is a good class
to use for extracting and installing propretary binaries.
(From yocto-docs rev: adde5e66f46df0b4e21bfe0fc0b47a9a8bed5e0c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bulleted item on supported BSPs was very centric on meta-intel.
I rewrote the section to not be so exclusive.
(From yocto-docs rev: d8118bb6124fbbb2340ae8720cd6187fd5546967)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
* 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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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_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>
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>
Scott Rifenbark
Richard Purdie
Bruce Ashfield
Alejandro Hernandez
Saul Wold
Andreas Müller
Ross Burton
Armin Kuster
Anibal Limon
Randy Witt
Roy Li
leimaohui
Joe Slater
Hongxu Jia
Muzaffar Mahmood