Tiny release to fix build with new xmlto.
(From OE-Core rev: ef523527b68eef0ce1fdacac87b4eee27677589b)
(From OE-Core rev: 8a52a4a64727f573fa11951ee0d387cc977a8b25)
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New release requires libpcre 2.
Enable gnutls by default to remove an annoying warning on every
vte widget. core-image-sato already has gnutls so this shouldn't
be a big deal.
(From OE-Core rev: c9b65168a6e5ca329c013d5932567eb6cca770f3)
(From OE-Core rev: 03f707ba1134b9706aed85665dc5f61aebbd5fb7)
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
here is shortlog
* d6601f0a avoid unbounded strlen in gettext functions
* dbbb3734 fix use of uninitialized pointer in gettext core
* 01e6bbec fix bindtextdomain logic error deactivating other domains
* 6894f847 fix spurious EINTR errors from multithreaded set*id, etc.
* 1f53e7d0 fix crashes in x32 __tls_get_addr
* 27b3fd68 fix crash from corrupted tls module list after failed dlopen
* 809ff8cf treat base 1 as an error in strtol-family functions
* 786fda87 fix getopt[_long] clobbering of optopt on success
* 150747b4 reduce impact of REG_* namespace pollution in x86[_64] signal.h
(From OE-Core rev: 6f42e7be18e0896aac357ce2aedaa3b32b2ad98e)
(From OE-Core rev: 72146e579e2df3b1132776a81b47e842dc262229)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are two major versions of the PCRE library. The newest version, PCRE2,
was released in 2015 and is at version 10.22.
The original, very widely deployed PCRE library, originally released in 1997,
is at version 8.40, and the API and feature set are stable, future releases
will be for bugfixes only. All new future features will be to PCRE2, not the
original PCRE 8.x series.
The newer vte depends on libpcre2, so add it.
(From OE-Core rev: f7165d379cb67c4d4918a8a3e9509d3d823d61da)
(From OE-Core rev: 69c4d94dd6b825c710c6e76fe77e5255ddd1183d)
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>
Now that Tremor isn't enabled by default in oe-core's GStreamer plugins and has
been added to meta-multimedia, it can be removed from oe-core.
(From OE-Core rev: 30f5c80943f69884b3d7323b540c8bb0f1efd8fd)
(From OE-Core rev: a8b476e7d6a5bf43cceb8c7b2610c9b66fe2f33e)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I discovered that we were not running autoreconf (and cannot due to the
unconvential file structure upstream), so manually run autoconf and move the
generated configure to the right place as we do already for gnu-configize.
Update no-x.patch (now that it is actually being used) so that it doesn't break
the build.
Patch out the use of INST_LIB_DIR in slsh/Makefile.in as this is the *target*
path, so is inappropriate to link to. This means we can remove the custom
do_install() which was working around the problem.
Remove all rpath patches (now overwritten by autoconf) and replace
with just passing RPATH='' via oe_runmake.
Remove the library search path patches (now overwritten by autoconf) and replace
with passing explicit pointers to the sysroot in the options.
[ YOCTO #10969 ]
(From OE-Core rev: 48fe39b09fbac973ba188938ab2a080f71ee8d68)
(From OE-Core rev: 3506898dbd62bb028349b83e1538a7ea665c3d1c)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default these pull in binutils-cross since they're a cross tool
and pull in any native tool requirements. In reality they don't
need such tools at build time or runtime since they're scripts.
Therefore clear the dependency and save on some processing time.
(From OE-Core rev: 63796765122e2eee2b78930797d571acb5c244d1)
(From OE-Core rev: 50feffd0917b0ab408b34ded9c2f741a9c4e5b74)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Its sad we need to do this but do_install and do_populate_sysroot appear
to change the files in ${B} and this breaks if something works in parallel
like gcc_stash_builddir. We've seen a few too many race errors on the
autobuilder which appear to be from this so make things run in sequence
deterministically for now.
An example failure was this from do_populate_sysroot whilst stash_builddir was running
in parallel:
ERROR: gcc-cross-initial-arm-6.3.0-r0 do_populate_sysroot: split_and_strip_files: 'file
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/work/x86_64-linux/
gcc-cross-initial-arm/6.3.0-r0/sysroot-destdir/home/pokybuild/yocto-autobuilder/yocto-worker/
nightly-arm-lsb/build/build/tmp/work/x86_64-linux/gcc-cross-initial-arm/6.3.0-r0/recipe-sysroot-native/
usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/arm-poky-linux-gnueabi-gcov' failed
Exception: subprocess.CalledProcessError: Command '('patchelf-uninative', '--set-interpreter',
'/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/sysroots-uninative/
x86_64-linux/lib/ld-linux-x86-64.so.2', '/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/
build/build/tmp/work/x86_64-linux/gcc-cross-initial-arm/6.3.0-r0/sstate-build-populate_sysroot/
recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/arm-poky-linux-gnueabi-gcov')' returned non-zero exit status 1
Subprocess output:
missing section headers
(From OE-Core rev: 75b76eb08c7e344142f0326605aeb6b24e61e38e)
(From OE-Core rev: 7265e99d0b4b662ca7f23d480f2845a309ac57fc)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The command was:
s += " -e 's:-L${libdir}:-LOELIBDIR:;'"
s += " -e 's:-I${includedir}:-IOEINCDIR:;'"
s += " -e 's:OELIBDIR:${STAGING_LIBDIR}:;'"
s += " -e 's:OEINCDIR:${STAGING_INCDIR}:;'"
s += " -e 's:-I${WORKDIR}:-I${STAGING_INCDIR}:'"
s += " -e 's:-L${WORKDIR}:-L${STAGING_LIBDIR}:'"
The STAGING_LIBDIR and STAGING_INCDIR now contains WORKDIR, so the
result would be incorrect like:
TCL_INCLUDE_SPEC='-IFIXMESTAGINGDIRTARGET/usr/include/recipe-sysroot/usr/include/tcl8.6'
Note, the "/usr/include/recipe-sysroot" is not needed. Move the last two
sed commands ahead will fix the problem.
(From OE-Core rev: 42e4e36de37b8e06a2ff56172d04d3ffeccfbfae)
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>
This allows a native package's recipe-sysroot-native to be populated with
that packages native image files. This in turns allows it to be used by
scripts or other tools without creating un-necessary DEPENDS.
An example of this is systemtap-native and the crosstap script.
(From OE-Core rev: 7f6b4359e1f2d9d748d23305a2af73c0efba5928)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed:
run.do_deploy.27809: line 155: depmodwrapper: command not found
(From OE-Core rev: 96b7eceefb3e99848d1c16d7c5da123056dcdc24)
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>
upgrade.py imports oe.recipeutils in meta/lib/ but path to oe.recipeutils
is not provided. This fails populate_sdk_ext.
(From OE-Core rev: 5f140359f859fea9cfe8c8d9c9584bceec875adb)
Signed-off-by: Luck Hoang <huyht1205@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
So that we can easily reproduce configure by:
$ $CACHED_CONFIGUREVARS ./configure $CONFIGUREOPTS $EXTRA_OECONF
[YOCTO #9423]
(From OE-Core rev: a851f57de63fe527e04f2296245e9720c40f9c2e)
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>
There is a typo in the useradd-staticids.bbclass that
causes error during do_install.
If build was configured to use usedadd-staticids and
the recipe included (for example):
USERADD_PARAM_${PN} = "--expiredate '' testUser"
Due to the typo this added the wrong option '--expiredata '
that caused an error.
(From OE-Core rev: 9d26a2f9f52ae9df6aa5e0ee20683ada35c32af1)
Signed-off-by: Peter Bergin <peter@berginkonsult.se>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
TUNE_FEATURES is include in BUILDCFG_VARS, so any whitespace is
visible to the user during the build process. Remove the extra
whitespace added during the 2.1 development cycle:
http://git.openembedded.org/openembedded-core/commit/?id=f774b44fa007a2a756ada892ede832b1251d940c
For consistency, squash whitespace within PACKAGE_EXTRA_ARCHS strings
too.
Whitespace within TUNE_FEATURES strings in the tune-cortexa*.inc
files has been fixed in a separate commit:
http://git.openembedded.org/openembedded-core/commit/?id=5610c6397ee098dd998b7417b343494de77179f9
(From OE-Core rev: 3cd0c5ef748ad072f1bd9a8d42157e9643bf97eb)
(From OE-Core rev: 971e43270173afb08f21ffac16a4157f7e611b81)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Incorrect data was printed (recipe name instead of epoch number) when
displaying changes in epoch.
(From OE-Core rev: 5e2b1bfb684dc76963f692172f7457c2249c3266)
(From OE-Core rev: d3f4ec2ad5e83f52f7d3824cfe1f5a64f2d81bcf)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add .xz to the list of extensions recognized by patch_path(), so that
compressed patches ending in .patch.xz or .diff.xz are automatically
applied.
(From OE-Core rev: f1a2c45765d14d3ca09657ad1f6b526554af2bb6)
(From OE-Core rev: f50fd7f247d5bb05bc7d1109c574a682067688da)
Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use cdn.kernel.org to distribute the server load and improve download speeds.
Leave www.kernel.org in MIRRORS as a fallback.
See https://www.kernel.org/introducing-fastly-cdn.html
(From OE-Core rev: 7c81b680a3cc4602c9c153398103d5477d7fd894)
(From OE-Core rev: 4f09ec0e7b51cc599d6a46d41f77d6fb07a6d445)
Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The idea on getTarget is to use kwargs to send custom variables
to different targets, instead of this, a new variable was added
(just used for custom targets) and this broke testexport. So
in order to fix it, just add the custom variable to kwargs.
This fixes the use of getTarget() in testexport class that was
introduced in 1dc8010afd71fe46fb28bb86fb7c07a5fbd3d7cf.
(From OE-Core rev: cf138029a1f18f991fc7a28c81d85884942e9d56)
Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The word 'uninstall' was spelled incorrectly in various parts of
oeqa files.
(From OE-Core rev: af365e025030436f83b233fa51ecc9c58c58ce3c)
(From OE-Core rev: 9d25188e873645b849584b51a77b86588a51d4ba)
Signed-off-by: Humberto Ibarra <humberto.ibarra.lopez@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Variable WKS_SEARCH_PATH was not fully expanded when used directly
in this expression:
WKS_FULL_PATH = "${@wks_search('${WKS_FILES}'.split(), '${WKS_SEARCH_PATH}') or ''}"
This caused expansion error: bb.data_smart.ExpansionError:
Failure expanding variable WKS_FULL_PATH, .... which triggered exception
SyntaxError: invalid syntax (WKS_FULL_PATH, line 1)
Calling d.getVar instead of directly referencing variables
should fix the issue.
(From OE-Core rev: 20f8fddd28fe46d7e694804de3d894cdf9f7c636)
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since 59a99cd8 "oeqa/sdk: Updates sanity tests for minimal eSDK"
we can now run oe-selftests against a minimal eSDK.
We need to increase the layer version so that we can detect this
change in behaviour in our automated testing.
(From OE-Core rev: def3800c7e58d9d1b54ea1df27b190a0f6d1d544)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9376]
Expanded many of the brief descriptions for the kernel-related
tasks.
(From yocto-docs rev: ee9e54aa9f148e5438cd9bdf7e55d7fa43cc3ec5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section "Maintaining Open Source License Compliance During
Your Product's Lifecycle" had a vew minor typo things (e.g. duplicated
word and some formatting issues). I fixed these.
(From yocto-docs rev: 67beb658445e79129d8aae1739bb33c000367107)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #11010]
The second example was incorrect in the glossary entry. Instead
of "1" an image name place holder was in the example. I put "1"
in there.
(From yocto-docs rev: 00ab787d0d90da5c6d384c3669e804c9b2baca53)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #10076]
The note on the title page for each manual was brief regarding
where to find the latest version of the manual. I updated the
note to have more detailed information on finding current,
alternate, and latest versions of the manual based on YP
releases.
(From yocto-docs rev: 0ec81465296a7a78309d3039af4d00caa52d2285)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This test checks to make sure only the files expected exist in a
container image. Currently only ROOTFS_BOOTSTRAP_INSTALL, gets added to
all images without the user specifying it.
But this test should help if a developer in the future ever silently
adds more than just ROOTFS_BOOTSTRAP_INSTALL, and that the developer can
make sure it also gets removed from a container image.
[YOCTO #9502]
(From OE-Core rev: 4f5e5321fafe491f91d78a35d11afc0dc0527d4b)
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the typical case of a container, the user doesn't particularly care
about the kernel version used. Since using linux-dummy prevents building
a kernel in the most common case, alert the user if they choose a
container image, but don't also specify linux-dummy.
In the cases the user actually does want to build against particular
kernel headers, etc, they can override by setting
IMAGE_CONTAINER_NO_DUMMY = "1".
[YOCTO #9502]
(From OE-Core rev: f0645e172bb839803d616f19307e1e81e0d204c0)
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "container" fstype does very little other than pick tar.bz2 as the
actual image type and disable installation of ROOTFS_BOOTSTRAP_INSTALL.
[YOCTO #9502]
(From OE-Core rev: e45f074b792a43aa2fd84a5a3f0e20bf1d88ad7e)
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When we removed the postinst sstate dependency handling code from
setscene_depvalid, we noticed things being installed into the old
style sysroot for rootfs tasks which should not have been there,
causing a performance regression.
Analysis revealed that setscene dependencies were "bubbling" over
sstate tasks when they should have been stopping there. The
'continue' added by this patch avoids this issue and eusures
sstate tasks remain contained to their specific chains.
There was another bug in the code this exposed where the acconting
for tasks as they were removed from sq_revdeps was not correct. In
fixing this, what looks like a workaround in another test can then
be simplified.
After this change, populate_sysroot tasks are no longer depending
on package_write_rpm tasks for example, which would make no sense.
A before/after analysis of image dependencies only revealed improved
dependencies after this change.
Recipe specific sysroots did highlight the issue here since the
behaviour of the sysroot dependencies (and processing with depvalid)
was not matching what bitbake itself was doing, with bitbake being
incorrect. Failures were 'safe' in that too many dependencies would
get installed.
(Bitbake rev: 5ef2cb50041fa7106c8de170af73d2a54cb0b1f0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The tinfoil.prepare method can raise Exceptions when is parsing initial
data so add this call inside try, finally to avoid get blocked for
don't call tinfoil.shutdown().
The tinfoil_init function was remove because isn't make sense now since
tinfoil.prepare() needs to be inside try, finally closures.
Example of raised exception and gets blocked:
$ bitbake-layers add-layer ~/repos/meta-openembedded/meta-python/
Traceback (most recent call last):
File "/home/alimon/repos/poky/bitbake/bin/bitbake-layers", line 83, in
main
tinfoil.prepare(True)
...
File "/home/alimon/repos/poky/bitbake/lib/bb/tinfoil.py", line 268, in
run_command
raise TinfoilCommandFailed(result[1])
bb.tinfoil.TinfoilCommandFailed: Traceback (most recent call last):
File "/home/alimon/repos/poky/bitbake/lib/bb/command.py", line 81, in
runCommand
result = command_method(self, commandline)
...
File "/home/alimon/repos/poky/bitbake/lib/bb/cooker.py", line 1314, in
handleCollections
raise CollectionError("Errors during parsing layer configuration")
bb.cooker.CollectionError: Errors during parsing layer configuration
(Bitbake rev: 61ebe9a026652e32f9482f66fc3fe7a8672fc093)
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The runqueue expects to be able to run 'bitbake-worker' from PATH, but
for example in the OE extensible SDK, tinfoil is used within devtool
where this isn't the case (we're not exposing bitbake to the user, thus
bitbake's bin directory isn't in PATH).
This fixes devtool modify usage within the extensible SDK which has
apparently been broken since the tinfoil2 changes went in.
Fixes [YOCTO #11034].
(Bitbake rev: 52d87e4a58a52174e8e0b6297abaac8fd93ffcc3)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- In some cases the file descriptor
is held by nfs client and none of os.path.* is catching
that, it could mean that error is not doled out because
client has cached the stat info. In this case we are
out of luck. Needed to catch IOError, which would be
causing the Stale error.
- In download method, update_stamp is invoked
md5sum validation which is found to be throwing
Stale errors.
- Added error handling to fix the stale errors.
(Bitbake rev: 5a53e7d7b017769a6eb0f0a6335735a1fe51a5ec)
Signed-off-by: Balaji Punnuru <balaji_punnuru@cable.comcast.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For spelling's sake, rename Python routine "setup_revisons" to
"setup_revisions."
(Bitbake rev: 4df59b027c02ef39d72476251ccd3fd62fc20bf6)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(Bitbake rev: 05f5421b2e44cd58c5912848de43d5884d070150)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When constructing an older style single regex, it's possible for BBMASK
to end up beginning with '|', which matches and masks _everything_.
(Bitbake rev: 56ad67017e601c7e0f6085ca84e29c28d8d4519f)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The package-depends.dot and pn-depends.dot files are inaccurate, missing
out key dependencies such those made via the [depends] flags. As such
they can be misleading to the user.
They mainly exist for historical reasons, coming from a time before
we had task based execution.
This commit removes the two dated file formats and replaces them with
a recipe-depends.dot which is a flattened version of task-depends.dot.
The old format files are removed if present so that the user can't get
confused about why data might not match between files.
The code is also rewritten to use 'with f: f.write()' syntax as is more
commonly used now.
Also update the docs to match the change.
(Bitbake rev: d3e182bc18ff2894f1efc8aad3d508dd432c996e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The depexp UI has been replaced with taskexp, also remove old
references to goggle and hob.
(Bitbake rev: 814c2b232ea5f88b5ad5031fb9d389c9c594aa01)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The data displayed by the depexp UI is buggy, bitbake can't convey
accurate runtime dependency information.
Convert the UI to become taskexp ("Task Explorer") which provides
a graphical way of exploring the task-depends.dot file. This data
is accurate and being able to visualise the data is an often requested
feature as standard dot file viewers can't usualy cope.
(Bitbake rev: 416a496edc692982af2feec768ac4df8fb799853)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backup are files sometimes are inconsistent and then cannot be
sorted (YOCTO #11043), and more importantly, are not needed in
the initial rootfs, so they get deleted.
Fixes: [YOCTO #11007]
(From OE-Core rev: e5628c80a52f3caeea9d9dc7f67d1b8a61222aef)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs to make Paul Gortmaker's port of 4.9-rt6 active.
(From OE-Core rev: b3e3ef85f5fd64473cae4aa72243665ac1e618e9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A typo introduced an extra } in the logging of the bsp_definition.
While this won't cause problems .. it needs to be fixed!
(From OE-Core rev: 9b95f3fca2a94ca922e05321096e07a11e98f9bb)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commit already in 4.9 and 4.8:
intel-quark: Add intel-quark-preempt-rt bsp configuration
While there are intel-quark configurations for the KTYPEs standard
and tiny in bsp/intel-common, there's none for the preempt-rt KTYPE.
Trying to build preempt-rt enabled kernels such as linux-yocto-rt for
intel-quark yields a .config having a potentially misconfigured
architecture. More importantly, however, preempt-rt related CONFIG
options are not enabled. Hence, a build of, e.g., linux-yocto-rt, does
not result in a preempt-rt enabled kernel.
This patch qualifies to be (back)ported to other branches than
master.
Signed-off-by: Christian Storm <christian.storm@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
(From OE-Core rev: e853327447908d1be085a96f8dda1c53305f9552)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to the korg -stable release. Changelog is as follows:
d2e4b66b4ef2 Linux 4.9.9
f2a0409a0850 drm/i915/execlists: Reset RING registers upon resume
72cd604cfd86 fs: break out of iomap_file_buffered_write on fatal signals
bf9ab22c350d iw_cxgb4: set correct FetchBurstMax for QPs
13363b6988f6 x86/irq: Make irq activate operations symmetric
e02136282296 irqdomain: Avoid activating interrupts more than once
c6b0333baea0 iio: health: max30100: fixed parenthesis around FIFO count check
12c2fcf6bcf7 iio: dht11: Use usleep_range instead of msleep for start signal
7baa8491d47d iio: health: afe4403: retrieve a valid iio_dev in suspend/resume
5f0ee562605b iio: health: afe4404: retrieve a valid iio_dev in suspend/resume
54d2ccc4003b iio: adc: palmas_gpadc: retrieve a valid iio_dev in suspend/resume
db0e02ef6b82 staging: greybus: timesync: validate platform state callback
89cc65c1117f USB: serial: option: add device ID for HP lt2523 (Novatel E371)
12a9c11c2e19 usb: gadget: f_fs: Assorted buffer overflow checks.
e40d15fce929 usb: musb: Fix host mode error -71 regression
cbd819e7db3a USB: Add quirk for WORLDE easykey.25 MIDI keyboard
4807725aab0b USB: serial: pl2303: add ATEN device ID
8bc382a9652b USB: serial: qcserial: add Dell DW5570 QDL
0dcbd0aa44e6 KVM: x86: do not save guest-unsupported XSAVE state
bc05a2e940fe dmaengine: cppi41: Fix oops in cppi41_runtime_resume
2c2e7fe7c9c5 dmaengine: cppi41: Fix runtime PM timeouts with USB mass storage
bebb9d75e84d perf/x86/intel/uncore: Clean up hotplug conversion fallout
e6bd712154aa HID: wacom: Fix poor prox handling in 'wacom_pl_irq'
f24bc920612c HID: hid-lg: Fix immediate disconnection of Logitech Rumblepad 2
80246551c7d7 HID: usbhid: Quirk a AMI virtual mouse and keyboard with ALWAYS_POLL
40add19d3897 iwlwifi: mvm: avoid crash on restart w/o reserved queues
97663735a96f iwlwifi: fix double hyphen in MODULE_FIRMWARE for 8000
3d8ec7d2d5f9 pinctrl: intel: merrifield: Add missed check in mrfld_config_set()
2cf6c49264e4 pinctrl: baytrail: Debounce register is one per community
449d3ecfbd76 Revert "vring: Force use of DMA API for ARM-based systems with legacy devices"
16f61dee7e7c Revert "bcma: init serial console directly from ChipCommon code"
12f822d23dee percpu-refcount: fix reference leak during percpu-atomic transition
8ee8ff9e2652 regulator: axp20x: AXP806: Fix dcdcb being set instead of dcdce
1594edd9ea0d vhost: fix initialization for vq->is_le
04eb7db25bb1 mmc: sdhci: Ignore unexpected CARD_INT interrupts
1d88791d5ed5 cgroup: don't online subsystems before cgroup_name/path() are operational
a150e08704b2 can: bcm: fix hrtimer/tasklet termination in bcm op removal
a93ae8dccc3c tracing: Fix hwlat kthread migration
b67c7d39bc28 mm, fs: check for fatal signals in do_generic_file_read()
6cb0497aec81 base/memory, hotplug: fix a kernel oops in show_valid_zones()
72f7419610c8 mm/memory_hotplug.c: check start_pfn in test_pages_in_a_zone()
9e255997c2e1 cifs: initialize file_info_lock
f0c3a0ac3349 zswap: disable changing params if init fails
a3d729526f2f svcrpc: fix oops in absence of krb5 module
743146d347f3 NFSD: Fix a null reference case in find_or_create_lock_stateid()
4c953848c95b powerpc/mm: Use the correct pointer when setting a 2MB pte
8f415333be3a powerpc: Fix build failure with clang due to BUILD_BUG_ON()
bbf69e5197da powerpc: Add missing error check to prom_find_boot_cpu()
73d45909780e powerpc/eeh: Fix wrong flag passed to eeh_unfreeze_pe()
4b70d598c2ee libata: Fix ATA request sense
6d08607ef35b libata: apply MAX_SEC_1024 to all CX1-JB*-HP devices
fc794153c407 ata: sata_mv:- Handle return value of devm_ioremap.
b41615aa7056 perf/core: Fix PERF_RECORD_MMAP2 prot/flags for anonymous memory
3996a91e3bdc perf/core: Fix use-after-free bug
53bed1f64025 crypto: arm64/aes-blk - honour iv_out requirement in CBC and CTR modes
b04a39f88ced crypto: api - Clear CRYPTO_ALG_DEAD bit before registering an alg
2eb8f7c4225a drm/nouveau/nv1a,nv1f/disp: fix memory clock rate retrieval
bd5cefed1ccc drm/nouveau/disp/gt215: Fix HDA ELD handling (thus, HDMI audio) on gt215
c9fb422fd938 drm/amdgpu/si: fix crash on headless asics
20658b3df8b9 pinctrl: baytrail: Add missing spinlock usage in byt_gpio_irq_handler
7396685a1bca HID: cp2112: fix gpio-callback error handling
a18c4584a489 HID: cp2112: fix sleep-while-atomic
dfd713307adb xtensa: fix noMMU build on cores with MMU
f2e24dd91818 efi/fdt: Avoid FDT manipulation after ExitBootServices()
f0c7412edfc1 x86/efi: Always map the first physical page into the EFI pagetables
13e6ef99d23b ext4: validate s_first_meta_bg at mount time
610c2b7ff8f6 PCI/ASPM: Handle PCI-to-PCIe bridges as roots of PCIe hierarchies
(From OE-Core rev: e1866b78d8365855583250877db7f11f98de65df)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commits to fix a configuration warning
and to add a tpm configuration feature:
8f3bc608ae61 features: add dm-verity
0ad64750fef1 tpm: avoid warning due to double CONFIG_TCG_TPM
(From OE-Core rev: 7fc93859ce805a604814b1b373d77ecc547e812f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Jussi Kukkonen
Khem Raj
Robert Yang
Ross Burton
Richard Purdie
Saul Wold
Luck Hoang
Peter Bergin
Andre McCurdy
Markus Lehtonen
Dominic Sacré
Mariano Lopez
Humberto Ibarra
Ed Bartosh
Joshua Lock
Scott Rifenbark
Randy Witt
Aníbal Limón
Paul Eggleton
Robert P. J. Day
Patrick Ohly
Bruce Ashfield