Saul Wold [Thu, 19 May 2016 22:24:13 +0000 (15:24 -0700)]
gdb: Backport patch to changes with AVX and MPX
The current MPX target descriptions assume that MPX is always combined
with AVX, however that's not correct. We can have machines with MPX
and without AVX; or machines with AVX and without MPX.
This patch adds new target descriptions for machines that support
both MPX and AVX, as duplicates of the existing MPX descriptions.
The following commit will remove AVX from the MPX-only descriptions.
This commit is backported from 7.12
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Anders Darander [Tue, 3 May 2016 11:57:16 +0000 (13:57 +0200)]
lib/oe/rootfs: Fix DEBUGFS generation for opkg & openssl-cnf
When enabling extra DEBUGFS image generation with opkg, the following error is
seen when openssl-cnf is included in the image.
Collected errors:
* file_md5sum_alloc: Failed to open file /mnt/cs-builds/anders/oe-build/build-ccu/tmp/work/ccu-oe-linux-gnueabi/ccu-image/1.0-r0/rootfs/usr/lib/ssl/openssl.cnf: No such file or directory.
Signed-off-by: Anders Darander <anders@chargestorm.se> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 9 May 2016 13:12:16 +0000 (14:12 +0100)]
update-alternatives: Fix determinism issue
getVarFlags returns a dict and there is therefore no sort order. This
means the order of the X_VARDEPS_X variables can change and hence the
task checksums can change. This can lead to rebuilds of any parts of
the system using update-alternatives and their dependees. This is a
particular issue under python v3.
Add in a sort to make the order of the variables deterministic.
Richard Purdie [Mon, 9 May 2016 13:09:37 +0000 (14:09 +0100)]
image: Fix IMAGE_FEATURES determinism issue
remain_features uses a dict which means the order is not deterministic. This
can lead to the task hash changing depending on the state of the memory at
parse time. This is particularly noticeable under python v3.
Since the dict is helpful in constructing the data, pass the data through
sort() so the order is always deterministic.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster@mvista.com>
Bruce Ashfield [Fri, 29 Apr 2016 17:05:14 +0000 (13:05 -0400)]
linux-yocto/4.4: skylake configuration
Integrating the following patches for skylake features and config:
82c2ea9f6bf intel-common: enable support for skylake in intel common bsp 269b6a7a98e2 intel-common-drivers: enable OSS Support 71a19d3e6dc6 intel-pinctrl: enable pinctrl driver for skylake 281f7db8c839 features: soc: enable configurations for skylake.
Bruce Ashfield [Fri, 22 Apr 2016 19:03:24 +0000 (15:03 -0400)]
linux-yocto/4.1: make ltsi content available
In the better late than never category, this commit integrates the
ltsi content into linux-yocto 4.1. We we already matching LTSI on
the kernel version front with a small gap in patches. With this
commit, we have a "ltsi" branch that is pure ltsi on the mailine
kernel, and then that commit is merged into standard/base (to
make it available to all BSPs).
Bruce Ashfield [Thu, 21 Apr 2016 15:23:45 +0000 (11:23 -0400)]
kernel-yocto: allow branch auditing to be suspended
When working on the yocto-bsp and kernel-lab update for yocto 1.2
we found it was impossible for a end-user BSP to isolate patches
on a branch, since with the following commit:
[kernel-yocto: enforce SRC_URI specified branch]
Any new branch would be switched to whatever was specified on the
SRC_URI and undoing the work that the yocto-bsp tool did to support
board specific patches.
To fix this, we'll keep the enforcing of branch consistency enabled
by default, but introduce a variable "KMETA_AUDIT" that when not
set will skip the check.
There's no impact for existing users, and it is only something that
other plumbing commands and tools will need to use (or care about).
There was a bug in the tools that did not handle the mix of subdirs
properly and ended up leaving a trailing / on the elements *not* in
the $BOARD subdir. As a result, the configuration fragments were not
properly found when searching the include paths, and a configuration
failure was triggered (due to missing files).
This change tweaks the tools to always check a path with and without
a trailing / when processing config fragments so they can be later
found when processing the configuration of the kernel.
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster@mvista.com>
Bruce Ashfield [Wed, 20 Apr 2016 23:30:07 +0000 (19:30 -0400)]
linux-yocto/uvesafb: print error message when task timeout occurs
Integrating the following commit to have a more informative error
message:
uvesafb: print error message when task timeout occurs
The driver waits for response from user space for a pending
task until a timeout (UVESAFB_TIMEOUT) occurs. But the
existing error message in later steps is a little obscure.
This patch throws out an error message when timeout happens.
Configure autodetects libtomcrypt, but then it adds libtommath to
$LIBS and fails to link subsequent tests if it's unavailable.
| checking for pcre.h... yes
| checking for pcre_compile in -lpcre... no
| checking whether to build with PCRE library... no
| ++ executing failure action
| configure: error: unable to find usable PCRE library
Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
gobject-introspection: fix floating dep on python-mako
This was resulting in non-deterministic builds where g-ir-doc-tool may or may
not exist depending on whether python-mako was built previously. Add
a PACKAGECONFIG so the dependency is explicit.
Signed-off-by: Sujith H <sujith.h@gmail.com> Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Sujith Haridasan <Sujith_Haridasan@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
sdk.py: preserve packaging data when SDKIMAGE_FEATURES has "package-management"
This is not enabled by default, as there are still limitations and possible
issues with opkg (and rpm?) packaging data containing broken symlinks for
local indexes:
There are other use cases for the packaging data to be available in SDK,
since it provides comprehensive info about SDK's contents and in the case of
opkg and dpkg is all text-based and can be easily parsed by simple scripts.
Introduce new "package-management" flag for SDKIMAGE_FEATURES list (similar
to the one already used for IMAGE_FEATURES) that controls presence of the
packaging data in resulting SDK, while unifying this behavior across the
board for supported pkg managers - rpm, opkg, dpkg.
Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Richard Purdie [Fri, 22 Apr 2016 13:51:22 +0000 (14:51 +0100)]
lib/oe/rootfs: Fix DEBUGFS generation when using opkg
When enabling extra DEBUGFS image generation with opkg, errors are seen like:
ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed packages list. Command '/media/build1/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg -f /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/opkg.conf -o /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version status' returned 0 and stderr:
Collected errors:
* file_md5sum_alloc: Failed to open file /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/etc/syslog-startup.conf.busybox: No such file or directory.
* file_md5sum_alloc: Failed to open file /media/build1/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/etc/fstab: No such file or directory.
basically for all CONFFILES in the image. This is due to the file rearranging
the rootfs generation code does. If we preserve the /etc directory,
the avoids the problem.
We need to tell copyfile to preserve symlinks since some are present in /etc.
[YOCTO #9490]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Tue, 19 Apr 2016 16:20:19 +0000 (17:20 +0100)]
boost: improve configure
Instead of adding a custom task (do_boostconfig) simply use the existing
do_configure.
Ensure that there are no relative paths in do_configure.
Instead of editing the user-config.jam sample file in the source tree (which is
entirely comments) and extending it on every build, create a new user-config.jam
in ${WORKDIR}.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Ross Burton [Tue, 19 Apr 2016 16:07:59 +0000 (17:07 +0100)]
boost: delete the build directory before rebuilding
If there is an existing build directory when do enter do_compile() then delete
it, as it contains the previous build. If the rebuild was caused because
dependencies have changed we want to ensure that a rebuild actually happens.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Markus Lehtonen [Thu, 21 Apr 2016 11:03:26 +0000 (14:03 +0300)]
license.bbclass: make sure that image manifest dir exists
Previously, write_deploy_manifest() was relying on
write_package_manifest() to create the subdirectory for the manifest
file. However, do_rootfs may be an empty function so that
write_package_manifest() will not be called and the manifest
subdirectory will not be created, causing a build failure. This patch
fixes that by creating the directory hierarchy inside
write_deploy_manifest().
[YOCTO #9446]
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Maxin B. John [Thu, 21 Apr 2016 09:24:07 +0000 (12:24 +0300)]
busybox: update flock behavior to match upstream
In "util-linux" implementation of flock, -c 'PROG ARGS' means run
"sh -c 'PROG ARGS'". At present, busybox implementation doesn't follow it.
That causes errors like the one listed below:
smart install /media/cronie-1.5.0-r0.core2_64.rpm
Updating cache...
<snip>
Output from cronie-1.5.0-r0@core2_64:
Running groupadd commands...
NOTE: cronie: Performing groupadd with [ --system crontab]
ERROR: cronie: groupadd command did not succeed.
error: %pre(cronie-1.5.0-r0.core2_64) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping
cronie-1.5.0-r0.core2_64
This is because we use flock command in preinstall scripts in packages
which create new groups/users.
[YOCTO #9496]
Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Attempting to install ptest for valgrind fails with this error:
error: Can't install valgrind-ptest-3.11.0-r0.1@ppce500mc: no package
provides /this/is/a/bogus/interpreter/name
This is because one of the tests contains a bogus interpreter path on purpose
It is not enough to skip the QA warning about the missing dependency
but the dependency have to be completely removed.
Since this package contains oly tests it is safe to disable per file
dependencies and rely on the ones per package.
Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30.
(Thanks to Alexander Krivenyshev for the heads-up.)
Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00.
(Thanks to Alexander Krivenyshev and Matt Johnson.)
New zone Asia/Tomsk, split off from Asia/Novosibirsk. It covers
Tomsk Oblast, Russia, which switches from +06 to +07 on 2016-05-29
at 02:00. (Thanks to Stepan Golosunov.)
Changes affecting past time stamps
New zone Europe/Kirov, split off from Europe/Volgograd. It covers
Kirov Oblast, Russia, which switched from +04/+05 to +03/+04 on
1989-03-26 at 02:00, roughly a year after Europe/Volgograd made
the same change. (Thanks to Stepan Golosunov.)
Russia and nearby locations had daylight-saving transitions on
1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on
1992-03-28 at 23:00 and 1992-09-26 at 23:00. (Thanks to Stepan
Golosunov.)
Many corrections to historical time in Kazakhstan from 1991
through 2005. (Thanks to Stepan Golosunov.) Replace Kazakhstan's
invented time zone abbreviations with numeric abbreviations.
Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
they keep the versions in-sync. changes are all in data.
Changes affecting future time stamps
America/Caracas switches from -0430 to -04 on 2016-05-01 at 02:30.
(Thanks to Alexander Krivenyshev for the heads-up.)
Asia/Magadan switches from +10 to +11 on 2016-04-24 at 02:00.
(Thanks to Alexander Krivenyshev and Matt Johnson.)
New zone Asia/Tomsk, split off from Asia/Novosibirsk. It covers
Tomsk Oblast, Russia, which switches from +06 to +07 on 2016-05-29
at 02:00. (Thanks to Stepan Golosunov.)
Changes affecting past time stamps
New zone Europe/Kirov, split off from Europe/Volgograd. It covers
Kirov Oblast, Russia, which switched from +04/+05 to +03/+04 on
1989-03-26 at 02:00, roughly a year after Europe/Volgograd made
the same change. (Thanks to Stepan Golosunov.)
Russia and nearby locations had daylight-saving transitions on
1992-03-29 at 02:00 and 1992-09-27 at 03:00, instead of on
1992-03-28 at 23:00 and 1992-09-26 at 23:00. (Thanks to Stepan
Golosunov.)
Many corrections to historical time in Kazakhstan from 1991
through 2005. (Thanks to Stepan Golosunov.) Replace Kazakhstan's
invented time zone abbreviations with numeric abbreviations.
Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Otavio Salvador [Tue, 19 Apr 2016 20:17:39 +0000 (17:17 -0300)]
syslinux.bbclass: Remove APPEND from variable dependency
The value of APPEND is already being tracked and does impact on the
generated configuration file. This reverts the OE-Core:3c2d7ae5 commit
as it is not need anymore.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Otavio Salvador [Tue, 19 Apr 2016 19:34:00 +0000 (16:34 -0300)]
syslinux.bbclass: The AUTO_SYSLINUXMENU value needs to be boolean
The python code expects AUTO_SYSLINUXMENU to be a boolean value,
otherwise the logic fails. This fixes the code comparing the value to
"1" which is the value expected by the shell script code, counterpart.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Tue, 19 Apr 2016 12:56:00 +0000 (13:56 +0100)]
perf: pass DESTDIR in EXTRA_OEMAKE
Instead of passing DESTDIR just in the make install invocation, pass it in
EXTRA_OEMAKE. This appears to stop perf from rebuilding at instal time for me,
which appears to be the trigger for the random build failure.
[ YOCTO #9182 ]
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Tue, 19 Apr 2016 02:09:35 +0000 (19:09 -0700)]
buildtools-tarball: set INHIBIT_DEFAULT_DEPS
The recipe doesn't need any default deps.
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>
Robert Yang [Mon, 18 Apr 2016 09:29:26 +0000 (02:29 -0700)]
xf86-video-omapfb: remove EXTRA_OECONF_armv7a
Fixe when build with armv7a:
gcc -c ../../git/src/sw-exa.c -fPIC -DPIC -o .libs/sw-exa.o
{standard input}: Assembler messages:
{standard input}:179: Error: selected processor does not support `vld1.u8 {d0},[r1]!' in ARM mode
{standard input}:182: Error: selected processor does not support `vld1.u8 {d1},[r4]!' in ARM mode
{standard input}:183: Error: selected processor does not support `vld1.u8 {q1},[r0]!' in ARM mode
{standard input}:184: Error: selected processor does not support `vzip.u8 d0,d1' in ARM mode
{standard input}:185: Error: selected processor does not support `vld1.u8 {q2},[ip]!' in ARM mode
{standard input}:186: Error: selected processor does not support `vst2.u8 {q0,q1},[fp]!' in ARM mode
{standard input}:187: Error: selected FPU does not support instruction -- `vmov.u8 q1,q2'
{standard input}:188: Error: selected processor does not support `vst2.u8 {q0,q1},[lr]!' in ARM mode
{standard input}:239: Error: selected processor does not support `vld1.u8 {d0},[r1]!' in ARM mode
{standard input}:242: Error: selected processor does not support `vld1.u8 {d1},[r4]!' in ARM mode
{standard input}:243: Error: selected processor does not support `vld1.u8 {q1},[r0]!' in ARM mode
{standard input}:244: Error: selected processor does not support `vzip.u8 d0,d1' in ARM mode
{standard input}:245: Error: selected processor does not support `vld1.u8 {q2},[ip]!' in ARM mode
{standard input}:246: Error: selected processor does not support `vst2.u8 {q0,q1},[fp]!' in ARM mode
{standard input}:247: Error: selected FPU does not support instruction -- `vmov.u8 q1,q2'
{standard input}:248: Error: selected processor does not support `vst2.u8 {q0,q1},[lr]!' in ARM mode
make[2]: *** [image-format-conversions.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
../../git/src/omapfb-crtc.c: In function 'OMAPFBCrtcResize':
../../git/src/omapfb-crtc.c:34:12: warning: unused variable 'ofb' [-Wunused-variable]
OMAPFBPtr ofb = OMAPFB(pScrn);
^
../../git/src/omapfb-xv.c:66:43: warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
{ XvSettable | XvGettable, 0, 0xffff, "XV_COLORKEY" },
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>
* add separate variable for configuration options generated from
PACKAGECONFIG setting, this helps other bbclasses and recipes
to take advantage of PACKAGECONFIG mechanism, without including
other options from EXTRA_OECONF
* e.g. meta-qt5 recipes are abusing EXTRA_OECONF to get options
from PACKAGECONFIG:
EXTRA_QMAKEVARS_PRE +=
but with
conf/distro/include/no-static-libs.inc
it means getting --disable-static as invalid option inside
EXTRA_QMAKEVARS_PRE as reported by Alexandre Belloni who tried
to use poky with meta-qt5.
* once we migrate all bbclasses and recipes to PACKAGECONFIG_CONFARGS
we should also restrict EXTRA_OECONF append only to autotools.bbclass
like I did for cmake.bbclass
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Markus Lehtonen [Tue, 19 Apr 2016 11:17:04 +0000 (14:17 +0300)]
license.bbclass: do write_deploy_manifest in image postprocessing
Call write_deploy_manifest() in image postprocessing phase, instead of
rootfs postprocessing. The reason being that not necessarily all
do_deploy tasks are dependencies of the do_rootfs and we might miss
something.
[YOCTO #9446]
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Tue, 19 Apr 2016 11:09:11 +0000 (23:09 +1200)]
devtool: sdk-update: fix handling of UNINATIVE_CHECKSUM changes
If UNINATIVE_CHECKSUM changes over an SDK update, bitbake within the
extensible SDK will be broken because it will see that the matching
uninative tarball doesn't exist and if there is a default value of
UNINATIVE_URL it will attempt to download the file and will then fail
because the checksums don't match up; alternatively if no UNINATIVE_URL
is set then it'll also fail with an error about misconfiguration. To fix
this, add some logic to devtool sdk-update to download the matching
uninative tarball(s) for the checksum(s) in the newly fetched SDK
configuration.
Fixes [YOCTO #9301].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
toasterconf.json: Remove fido from supported configurations
It looks like the master branch will no longer build with the Fido
release, so remove all references to fido and make sure that the file
sets up local, master and jethro releases.
Signed-off-by: Belen Barros Pena <belen.barros.pena@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ed Bartosh [Mon, 18 Apr 2016 12:27:24 +0000 (15:27 +0300)]
oetest: make console output more verbose
Added output of test runner to bitbake console output.
bitbake <image> -c testimage now reports test progress
to the console:
NOTE: Executing RunQueue Tasks
...
NOTE: recipe core-image-lsb-1.0-r0: task do_testimage: Started
core-image-lsb-1.0-r0 do_testimage: test_ping (oeqa.runtime.ping.PingTest) ... ok
core-image-lsb-1.0-r0 do_testimage: test_ssh (oeqa.runtime.ssh.SshTest) ... ok
...
----------------------------------------------------------------------
core-image-lsb-1.0-r0 do_testimage: Ran 38 tests in 785.100s
core-image-lsb-1.0-r0 do_testimage:
core-image-lsb-1.0-r0 do_testimage: OK (skipped=1)
Adding more output to the console should also prevent autobuilder to kill
long running tests as ab assumes that test is stuck if no console output
produced by it for a long time.
[YOCTO #8238]
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
ISC DHCP 4.1.x before 4.1-ESV-R13 and 4.2.x and 4.3.x before
4.3.4 does not restrict the number of concurrent TCP sessions,
which allows remote attackers to cause a denial of service
(INSIST assertion failure or request-processing outage)
by establishing many sessions.
Paul Eggleton [Mon, 18 Apr 2016 03:27:07 +0000 (15:27 +1200)]
buildtools-tarball: fix perl being included when building with ipk
Due to some logic within opkg, a package with the name matching a
dependency will always win over a package with that name in RPROVIDES -
even if there is an RCONFLICTS (which is silently ignored), higher feed
priority and version. The end result is that buildtools gets perl
installed instead of the nativesdk-buildtools-perl-dummy package and
that perl (with missing dependencies) gets used in preference to the
host one, which is precisely what we were trying to avoid.
This is almost certainly a bug in opkg, especially as the other
package's dependencies aren't properly installed under these
circumstances either. However, specifying RREPLACES works around this,
and with no apparent side-effects is probably the safest solution for
now.
At the same time I noticed that in prepending to SDK_PACKAGE_ARCHS we
were actually ending up with a low priority for the dummy package feed
rather than a high one, so change to append it instead. This has no
effect on the packages that get installed at the moment, but should be
done in case the package manager behaviour changes to factor in the feed
priority in future.
Fixes [YOCTO #9469].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Replace git pull with fetch and reset to avoid the merge logic in the
event that the layers repo in the published SDK we're updating to isn't
fast-forward merge from the local repo.
Also add gitignore and committer info during publish to avoid errors and
to be sure that the first commit has a dummy user in it.
[ YOCTO #9368 ]
Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
This patch addresses the issue of not being able to execute "runqemu"
in the Build Appliance.
The root cause of the problem was that TAP/TUN was not available,
although required by "runqemu". In addition, the recommended remedy
$ sudo modprobe tun
would fail for two reasons: modprobe not in PATH (user builder),
and "iptables" located in /usr/sbin but expected in /sbin.
[YOCTO #9437]
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Andre McCurdy [Thu, 14 Apr 2016 22:38:16 +0000 (15:38 -0700)]
default-providers.inc: set openssl PREFERRED_PROVIDER to openssl
Although the oe-core openssl recipe is currently the only provider of
openssl, make the preference for using it explicit in anticipation of
a libressl recipe being added to meta-oe.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Jussi Kukkonen [Fri, 15 Apr 2016 12:03:17 +0000 (15:03 +0300)]
bind: CVE-2016-2088
Duplicate EDNS COOKIE options in a response could trigger an
assertion failure: Fix with a backport.
bind as built with the oe-core recipe is not at risk: Only servers
which are built with DNS cookie support (--enable-sit) are vulnerable
to denial of service.
Fixes [YOCTO #9438]
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Marek Vasut [Fri, 15 Apr 2016 10:20:15 +0000 (12:20 +0200)]
rpm: Disable __sync_add_and_fetch_8 on nios2
The NIOS2 softcore does not implement the __sync_add_and_fetch_8,
so disable it accordingly.
Signed-off-by: Marek Vasut <marex@denx.de> Cc: Ley Foon Tan <lftan@altera.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Ross Burton <ross.burton@intel.com> Cc: Thomas Chou <thomas@wytron.com.tw> Cc: Walter Goossens <waltergoossens@home.nl> Signed-off-by: Ross Burton <ross.burton@intel.com>
Marek Vasut [Fri, 15 Apr 2016 10:19:46 +0000 (12:19 +0200)]
kernel: fitimage: Fix do_deploy taskhash mismatch
The kernel_do_deploy_append() uses DATETIME variable , so the taskhash
of the kernel_do_deploy() function changes if fitImage is used. The
buildsystem will complain accordingly:
Bill Randle [Wed, 13 Apr 2016 17:17:42 +0000 (10:17 -0700)]
ext-sdk-prepare.py: exclude do_rm_work from unexpected output; create unit test
When installing the esdk with INHERIT += "rm_work", the script complains
about do_rm_work as unexpected output from the bitbake run. This patch
ignores any output lines with do_rm_work and further refactors the
output comparison into its own function creates a new unit test to
verify the fix. The unit test can be run direct from the command line or
via oe-selftest.
[YOCTO #9019]
Signed-off-by: Bill Randle <william.c.randle@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Robert Yang [Wed, 6 Apr 2016 05:34:25 +0000 (22:34 -0700)]
fs-perms.txt: fix ROOT_HOME's permission
It should be 0700 rather than 0755.
Reported-by: Charles Chan <charles.wh.chan@gmail.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Richard Purdie [Thu, 14 Apr 2016 13:53:14 +0000 (14:53 +0100)]
buildstats: Fix tracebacks for early task failures
If a failure occurs early in the task, its possible we can have a
TaskFailed before the TaskStarted event can be triggered. This in
turn causes another traceback as the directory buildstats writes
files into doesn't exist.
Ensure the directory exists so we can see the original error.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Zhenhua Luo [Thu, 14 Apr 2016 09:26:44 +0000 (17:26 +0800)]
meta/classes/qemu.bbclass: set -cpu of ppce5500/ppce6500 to e500mc
The e5500 and e6500 cpu types are not supported by native qemu, set the value
of -cpu to e500mc. Without this change, build will fail for packages which use
qemuwrapper in compile phase due to the following error.
| Unable to find CPU definition
e.g. gobject-introspection
Signed-off-by: Zhenhua Luo <zhenhua.luo@nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building shadow-native, syslog was disabled for useradd and
groupadd. This disables it also for groupdel, groupmems, groupmod,
userdel and usermod (i.e., the use of syslog is now disabled for all
commands supported by useradd_base.bbclass).
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Thu, 14 Apr 2016 08:24:19 +0000 (20:24 +1200)]
devtool: upgrade: handle recipes where source is not first entry in SRC_URI
It is unusual but not impossible to find recipes whose first entry is
not the main source URL but instead some patch or other local file, for
example python-cryptography in meta-python (which sets SRC_URI before
inheriting pypi). There's nothing inherently wrong with this, and we
shouldn't assume that the first entry is the main source URL, so just
take the first non-local entry instead.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Thu, 14 Apr 2016 08:24:18 +0000 (20:24 +1200)]
devtool: update-recipe: handle where SRC_URI is appended to with +=
If a recipe sets SRC_URI and then appends more items to it with +=
(such as the current rpm recipe in OE-Core), the code in
patch_recipe_file() was failing with a traceback. Work around the
problem for now by dropping the existing lines if we understand the
operation, else just set the value outright at the end. This leaves
something to be desired as it either doesn't respect the existing
structure or leaves a mess but it's better than the current
breakage.
We'll need to come up with a better solution later. Part of the problem
is the existing code structure doesn't allow for patch_recipe_file() to
know what's being added or removed - it only knows the final value that
the caller wants set.
Fixes [YOCTO #9458].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 13 Apr 2016 16:12:13 +0000 (12:12 -0400)]
linux-yocto: make aufs4 optional
An always on configuration of aufs4 crept into the default kernel
configuration blocks.
With this change, aufs-enable.scc can be used to turn on aufs via
a KERNEL_FEATURES entry. We can now have co-existing unionfs solutions
and can update them without breaking builds that haven't opted-in.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
db28bb1e7a68 async: export current_is_async() e89355d51cc4 PM / runtime: Add new helper for conditional usage count incrementation dcf8de0931b1 ALSA: hda - hdmi defer to register acomp eld notifier da1bcdb4415e ALSA: hda - Allow i915 binding later in codec driver fb95901a1724 ALSA: hda - Enable audio component for old Intel PCH devices 0a082020f0c4 ALSA: hda - Autosuspend controller after probe even if codecs are already suspended 7f7608752b37 ALSA: hda - hdmi add wmb barrier for audio component 7a32403bb06f ALSA: hdac: add snd_hdac_ext_bus_link_power_up_all 0d593c9fcf75 ALSA: hdac: Add support for hda DMA Resume capability e453b7e42563 ALSA: hdac: structure definition for ext_dma_params da5b15cea3a0 drm/edid: Add API to help find connection type 723224e90dfe ASoC: hdac_hdmi: Fix codec power state in S3 during playback 006d407c400d ASoC: hdac_hdmi: Fix to use dev_pm ops instead soc pm 149316f63e17 ASoC: hdac_hdmi: Add broxton device ID f94dc80e4ac5 ASoC: hdac_hdmi: Fix infoframe programming 623b2f9b33f1 ASoC: hdac_hdmi: Add PM support 9d0c9e8114f8 ASoC: hdac_hdmi: Fix to reconfigure registers in runtime resume 4afb4f7a3760 ASoC: hdac_hdmi: Don't fail in dai startup to make userland happy ec497d3f13c3 ASoC: hdac_hdmi: Enable playback on all enumerated ports d94da5c4fe3b ASoC: hdac_hdmi: Apply constraints based on ELD 401a43cac5a4 ASoC: hdac_hdmi: Fix to wait for D3 before powering off codec 69fd08bfd8a8 ASoC: hdac_hdmi: Fix to keep codec power active during enumeration. fe945a86a8c8 ASoC: hdac_hdmi: Fix possible memory leak in hw_params 2e2a20f383c4 ASoC: hdac_hdmi: Remove 'edev' NULL check 9f781dd80b54 ASoC: hdac_hdmi: Add infoframe support for dp audio b8110510884a ASoC: hdac_hdmi: Add jack reporting 1cdebc2d6e78 ASoC: hdac_hdmi: Create widget/route based on nodes enumerated 73b4b1dc5b63 ASoC: hdac_hdmi: create dais based on number of cvts e59b34525953 ASoC: hdac_hdmi: Enable DP1.2 and all converters/pins 760989e722ef ASoC: hdac_hdmi: Add hotplug notification and read ELD 30364a5601ae ASoC: hdac_hdmi: remove unused hdac_hdmi_query_pin_connlist 2764583d744e ASoC: hdac_hdmi: Use list to add pins and converters 9458ca02aa7e ASoC: hdac_hdmi: Fix to warn instead of err for no connected nids 477a88699c5e ASoC: hdac_hdmi: Fix to check num nodes correctly acdc6421f720 ASoC: hdac_hdmi: use dev_to_hdac_dev and to_ehdac_device bd4ba9cdf188 ASoC: hdac_hdmi: check error return b6898f18eaca ASoC: hdac_hdmi: fix possible NULL dereference 4836a9c5bc4e ASoC: hdac_hdmi: Use i915 component framework for PM c70f3eab8f81 ASoC: hdac_hdmi: Setup and start infoframe f0f09f63f4f5 ASoC: hdac_hdmi: Add hdac hdmi dai ops 4bab2c42e58a ASoC: hdac_hdmi: Add PM support for HDMI d1237b8c1a21 ASoC: hdac-hdmi: Add hdmi driver 0e0a7bb86eb8 mei: me: add broxton pci device ids 2af333b2beee usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host 7ae2e3bce771 dmaengine: idma64: set maximum allowed segment size for DMA 53e822a3c638 dmaengine: idma64: drop IRQ enable / disable in handler 97e4071b6885 spi: pxa2xx: Fix too early chipselect deassert 46cc317c74dd i2c: designware: remove redundant lock 03a6b1c85e0a i2c: designware: Prevent runtime suspend during adapter registration d5da4042ad5b mmc: sdhci-pci: Add support and PCI IDs for more Broxton host controllers c3d97cf9fe19 mmc: sdhci-pci: Do not set DMA mask in enable_dma() f20ad778b58e mmc: sdhci-pci: Do not default to 33 Ohm driver strength for Intel SPT ca9a77c6869b mmc: sdhci: Fix override of timeout clk wrt max_busy_timeout 74982dc84940 mmc: sdhci-acpi: Fix card detect race for Intel BXT/APL 8017269a25bf mmc: sdhci-pci: Fix card detect race for Intel BXT/APL b532b30c3e41 mmc: sdhci: Allow override of get_cd() called from sdhci_request() 9e96c0c00221 mmc: sdhci: Allow override of mmc host operations 0148b3601f29 gpio-pca953x: fix the "drive" property cannot read/write
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 13 Apr 2016 16:12:09 +0000 (12:12 -0400)]
linux-yocto/4.4: gpio-pca953x: fix the "drive" property cannot read/write
The gpio_drive_show/store use incorrect gpio_desc,
this causes the drive sysfs property cannot be used,
This patch fixes this issue
Upstream-status: Inappropriate, custom code for legacy userspace
Signed-off-by: Yong Li <yong.b.li@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Dan McGregor [Wed, 13 Apr 2016 22:17:56 +0000 (16:17 -0600)]
package.bbclass: improve permission handling
Change fs_link_table to be keyed by path, just like fs_perms_table.
When a new entry is coming in for either table, remove any previous
entry for that path. This way later permission file entries override
earlier ones.
[YOCTO #9430]
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Wed, 6 Apr 2016 05:34:25 +0000 (22:34 -0700)]
fs-perms.txt: fix ROOT_HOME's permission
It should be 0700 rather than 0755.
Reported-by: Charles Chan <charles.wh.chan@gmail.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
