The code:
bb.fatal("foo1")
bb.fatal("foo2")
Would make the second one not work, use bb.error for first one to fix
the problem.
(From OE-Core rev: 33a87187a8520e190bcade76cc965aa58faaa85a)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The '-l' option which is valid for GNU make (--> limit by load) has a
different meaning in bjam (--> limit maximum execution time) and will
break very likely the build.
Keep only the the '-l' option when passing PARALLEL_MAKE options to
bjam.
(From OE-Core rev: 1ff36aaec25a7ee89514366fe484345e8d1d7b64)
Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd expects fsck programs to be located in /sbin and fails for
dosfstools with
| Checking was requested for ..., but /sbin/fsck.vfat cannot be used: No such file or directory
Other fsck programs (e.g. ext4) are located in /sbin already so move
vfat programs into this directory too.
(From OE-Core rev: fa579cb243b8441d95e6c129e07d9e141f808539)
Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libffi is generally present as it's also a build dependency on glib-2.0, but
explicitly declare it for determinism.
(From OE-Core rev: 85232b154dbaf3fc2ed3fa9291e3cbeaa7f318ab)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the service file to more closely match the service file that has been
committed upstream.
In particular we don't want to restart neard on failure (this results in it
restarting repeatedly if no NFC hardware is found), redirecting stdout to
/dev/null means that any messages are lost instead of being sent to the journal,
and the DBus alias is required for bus activation to work correctly.
(From OE-Core rev: b6afd8e5abcd412c17e14c59379b9583b95fd517)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In some situations where a proxy is required the client can't even do DNS
lookups, so instead of using SOCKS4 use SOCKS4a which moves the name resolution
from the client to the proxy.
(From OE-Core rev: 984455a95b4302d527ff54e019d8ed00611f3664)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The user can enable libssh2 via conf/local.conf or custom distro
configuration, this will pull in libssh2, which is not used by default.
For example, a curl_x.y.z.bbappend file containing the following line:
PACKAGECONFIG += "libssh2"
(From OE-Core rev: d425e005d274cac0ef7160f53c41bda175444f69)
Signed-off-by: Fabrice Coulon <fabrice.coulon@axis.com>
Signed-off-by: Olof Johansson <olof.johansson@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The DRI3 and Present modules are built-in but some drivers (such as
xf86-video-intel) want to query their presence. Backport a patch from upstream
to stop this causing an error.
[ YOCTO #6583 ]
(From OE-Core rev: d7bb1d8b1a7cd11895037b7984b9aa916efa9733)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Creates x11 packageconfig and update DEPENDS and EXTRA_OEMAKE_X
for better handling.
(From OE-Core rev: b853cead2e0965b9797b40d6b59bed67804f459f)
Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed when rebuild:
rm: cannot remove `/path/to/2.1.2-r0/libassuan-2.1.2/m4/*.m4': No such file or directory
The files may not exist when rebuild.
(From OE-Core rev: f04576c761c568083be1143f421e29fc2365846a)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The generation of the environment has change since the change to use a
meta-environment canadian package in the OE-Core, the SDK environment
setting has been broken. This uses the new subscript environment to
fix it.
(From OE-Core rev: e7b9e1df19062cfbcd72c90295829424cae6fbed)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Sometimes we require extra environment settings to be available on the
environment for proper SDK work. This were done, in past, using
'_append' tasks however with the split of the environment in a
canadian package this has been broken.
The easier and more flexible solution is to use environment subscripts
which are sources by the main script. These are now looked at:
$OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh
and sourced.
(From OE-Core rev: 457291f2ca084d1f43c0cca2175b448a22761887)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Forcing strict to be a string, to avoid problems when performing comparisons
[YOCTO #6762]
(Bitbake rev: b8ed2098bdea2afd93ab4e3e1b834f3a31cb60de)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The SRC_URI may contain whitespace, but be otherwise empty. This can happen
in the case:
MYSRC = ""
MYSRC_arm = "file://myarm.patch"
SRC_URI += "${MYSRC}"
Unless we strip blank spaces, to determine if it is empty, we can end up
generating a "Source: " line which in invalid. This leads to the error:
invalid Source: field is speified in the generated CONTROL file
(From OE-Core rev: 16cedc3bce6fc37543e9ef053cd7c589e523ca1c)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Makedoc.sh script uses the following line to set TMPDIR
export TMPDIR=`mktemp -d ${TMPDIR:-/tmp}/ldt.XXXXXXXXXX`;
and then later in the script:
chmod u+x $TMPDIR/linuxdoc
Since TMPDIR is not set the script will default to /tmp and if /tmp
is set to noexec (which is becoming more common), the chmod call fails.
(From OE-Core rev: 3a8b8812ac1b9a724f11b2011f8ee3416ac3d4df)
Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In case a package is not generated (is empty and does not has allow
empty flag set) the package data regarding reverse runtime dependency
shouldn't be done.
This were causing a false-positive in the meta-fsl-arm layer, when
building mesa, as:
,----[ Error during build of MX53 in meta-fsl-arm ]
| ERROR: The recipe mesa is trying to install files into a shared area
| when those files already exist. Those files and their manifest
| location are:
| /.../build/build/tmp/sysroots/imx53qsb/pkgdata/runtime-reverse/libopenvg-dev
| Matched in manifest-imx53qsb-amd-gpu-x11-bin-mx51.packagedata
| Please verify which recipe should provide the above files.
`----
Fixes [YOCTO: #6795]
(From OE-Core rev: 9ef8728514b02dd2e18e87645298d9ec2e8a785a)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The tests for robust mutexes contained conditional clauses which failed in
autoconf and/or used nonexistent variable names. Modified these
conditional clauses to use only the variables actually created by
LTP autoconf for this purpose.
(From OE-Core rev: c0189ef8b58b1e63e227c5040cb1c9e915f225c2)
Signed-off-by: Gary S. Robertson <gary.robertson@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The priority inheritance tests for mutexes used conditional variables
which were non-existent. Changed the conditional clauses to use the
variables which were actually generated by LTP autoconf for that purpose.
(From OE-Core rev: 812114ad23def92306fbf9f7afb03cee4cbd10d4)
Signed-off-by: Gary S. Robertson <gary.robertson@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We upgrade bash_4.3 to patch revision 29, and bash_3.2.48 to 56.
There are numerous community bug fixes included with this set, but the key
items are:
bash32-052 CVE-2014-6271 9/24/2014
bash32-053 CVE-2014-7169 9/26/2014
bash32-054 exported function namespace change 9/27/2014
bash32-055 CVE-2014-7186/CVE-2014-7187 10/1/2014
bash32-056 CVE-2014-6277 10/2/2014
bash43-025 CVE-2014-6271 9/24/2014
bash43-026 CVE-2014-7169 9/26/2014
bash43-027 exported function namespace change 9/27/2014
bash43-028 CVE-2014-7186/CVE-2014-7187 10/1/2014
bash43-029 CVE-2014-6277 10/2/2014
(From OE-Core rev: 43deeff0c6b0ea7729d3e5f1887dfd1647dea1da)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pseudo 1.6.2 fixes problems with 64-bit inodes and some underlying issues
involving file renames that could occasionally cause very strange behaviors
files being deleted, linked, or renamed, mostly observed as strange
recovery if an inode got reused.
(From OE-Core rev: b2c6a032d6e5deb07e76ed75fcd0931fad6a748c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Similarly to native/cross disable this since otherwise the packagedata
can be marked as machine specific and if you switch machines
which share an architecture, you'll get toolchain overlapping files
errors.
(From OE-Core rev: 96d557be3dedd6aea6199b3d28fbb7f5549fad69)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some machines change TARGET_OS, cross-canadian resets this which
is not what we want in this specific case. This fixes spe toolchains
for example.
(From OE-Core rev: 0038634ee6e2b6035c023a2702547f20f67c103a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some architectures can mix different TARGET_OS values, in most cases
we just use one but in the ppc case, can use two different values. In this
case, to use one toolchain with both, we need to ensure the symlinks exist.
This isn't ideal but does fix the ppc toolchains for the release, after
which better ways of handling this can be investiaged. Without this, failures
in the C++ toolchain are seen.
(From OE-Core rev: 112641117f1152bad8a806f1aa872a67575d5316)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Even though the kernel-dev package provides the required support for
building external kernel modules on the target, some commonly used scripts
and utilities fail as they are not finding the kernel module build support
files at the desired location.
Create the /lib/modules/<kernel-version>/build link on target pointing to
the sources provided by the kernel-dev package, to fix the issue.
Fixes Bug:
[YOCTO #2968]
(From OE-Core rev: aafa4bc896eb944aa4fc406807dd7e02f4b9b7ba)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The makefile checks for bc during for compilation
[YOCTO #6781]
(From OE-Core rev: c067e52cffe002de3b39aa1bced308dd532859c1)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a proper sysroot specified in the meta-environment script now,
which isn't a bad thing. We adjust the sed expression to cope with this.
That means the SDK installations in non-default paths start to work again.
(From OE-Core rev: 3be7b59893ed77f63eeca35b686df06a1dafb53d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
Updating the 3.17 tree to the rc7 release.
(From OE-Core rev: 6957ce3e726de5dbdcf3e94c5919916d88736e8d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
Robert Yang
Tudor Florea
Enrico Scholz
Ross Burton
Khem Raj
Fabrice Coulon
Noor
Otavio Salvador
Alejandro Hernandez
Mark Hatle
Konrad Scherer
Gary S. Robertson
Peter Seebach
Richard Purdie
Nitin A Kamble
Scott Rifenbark
Bruce Ashfield