On Fri, Aug 17, 2018 at 6:00 PM Ankur Tyagi wrote:
>
> Respect PERSISTENT_LOG_DIR variable. In this way, if the user overrides
> this variable to be e.g "/home/root/log", /var/log on the final image would
> be a link pointing to /home/root/log on persistent storage.
>
I would suggest to stick
This is nice addition, but maybe it would be worth explaining somewhere
what these numbers actually mean.
e.g. my current build shows:
Sstate summary: Wanted 181 Found 39 Missed 142 Current 279 (21% match, 69%
complete)
>From quick look at the code my understanding is that:
1) Wanted = Found +
Ping
Regards
Ankur
On Sat 18 Aug, 2018, 12:59 PM Ankur Tyagi, wrote:
> This variable is only respected when VOLATILE_LOG_DIR is "no".
>
> The default value is "" which results in the /var/log being log directory.
>
> The user could override this value to a path e.g "/home/root/log" which
>
Ping
Regards
Ankur
On Sat 18 Aug, 2018, 12:59 PM Ankur Tyagi, wrote:
> Respect PERSISTENT_LOG_DIR variable. In this way, if the user overrides
> this variable to be e.g "/home/root/log", /var/log on the final image would
> be a link pointing to /home/root/log on persistent storage.
>
>
When building more than one device tree it's inefficient to serially
build them in multiple make calls. It's much faster and efficient to
build them in one call where they can run in parallel.
Signed-off-by: Dan Dedrick
---
meta/classes/kernel-devicetree.bbclass | 6 +-
1 file changed, 5
On Fri, Aug 24, 2018 at 9:41 AM wrote:
>
> On Fri, Aug 24, 2018 at 09:23:45AM -0700, Khem Raj wrote:
> > On Fri, Aug 24, 2018 at 9:17 AM wrote:
> > >
> > > On Fri, Aug 24, 2018 at 08:51:42AM -0700, Khem Raj wrote:
> > > > On Fri, Aug 24, 2018 at 8:48 AM wrote:
> > > > > So to me it looks like
On Fri, Aug 24, 2018 at 09:23:45AM -0700, Khem Raj wrote:
> On Fri, Aug 24, 2018 at 9:17 AM wrote:
> >
> > On Fri, Aug 24, 2018 at 08:51:42AM -0700, Khem Raj wrote:
> > > On Fri, Aug 24, 2018 at 8:48 AM wrote:
> > > > So to me it looks like using SYSTEM with target_include_directories()
> > > >
On Fri, Aug 24, 2018 at 9:17 AM wrote:
>
> On Fri, Aug 24, 2018 at 08:51:42AM -0700, Khem Raj wrote:
> > On Fri, Aug 24, 2018 at 8:48 AM wrote:
> > > So to me it looks like using SYSTEM with target_include_directories()
> > > is no longer possible with CMake and gcc > 6:
> > >
> > >
> > >
On Fri, Aug 24, 2018 at 08:51:42AM -0700, Khem Raj wrote:
> On Fri, Aug 24, 2018 at 8:48 AM wrote:
> > So to me it looks like using SYSTEM with target_include_directories()
> > is no longer possible with CMake and gcc > 6:
> >
> >
> >
On Fri, Aug 24, 2018 at 8:48 AM wrote:
> On Fri, Aug 24, 2018 at 03:10:28PM +, Bach, Pascal wrote:
> >
> > > > Fixes problems which we have also seen on sumo branch. Thanks for
> this!
> > >
> > > Sorry, spoke too soon. This fixes compilation on a few recipes in my
> tree but
> > > there are
On Fri, Aug 24, 2018 at 03:10:28PM +, Bach, Pascal wrote:
>
> > > Fixes problems which we have also seen on sumo branch. Thanks for this!
> >
> > Sorry, spoke too soon. This fixes compilation on a few recipes in my tree
> > but
> > there are still lots failures with the same error message.
Uprev'ing lttng to 2.10.7 to support 4.18+ kernels.
Dropped the brtfs patch as it is no longer required to for the tested
kernel range.
License-Update: headers changed to include SPDX information
Signed-off-by: Bruce Ashfield
---
v2: addressed patch appliation issues
Added
On Fri, Aug 24, 2018 at 8:19 AM Bach, Pascal
wrote:
>
> > > Fixes problems which we have also seen on sumo branch. Thanks for this!
> >
> > Sorry, spoke too soon. This fixes compilation on a few recipes in my
> tree but
> > there are still lots failures with the same error message. We had a
== Series Details ==
Series: kernel: consolidated pull request (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/11131/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
> > Fixes problems which we have also seen on sumo branch. Thanks for this!
>
> Sorry, spoke too soon. This fixes compilation on a few recipes in my tree but
> there are still lots failures with the same error message. We had a hacky
> patch to cmake as a workaround but that too causes some
Armin,
Could you please backport this to sumo now that is has been accepted to
master (409c8a32659ac707d427cd4cdcd105eb17d6f733)?
Thanks.
On Thu, 2018-08-23 at 16:24 -0500, Joshua Watt wrote:
> The actual dependency on native Python and is handled by inheriting
> python3native
>
>
4.18 is replacing 4.15 as the latest kernel in the upcoming
release, so we update our preferred versions to match.
Signed-off-by: Bruce Ashfield
---
meta/conf/machine/include/x86-base.inc | 2 +-
meta/conf/machine/qemuarm.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Updating to the 4.18 headers to match the newest kernel that will
be part of the release.
4.18 brings a requirement on bison-native to the libc-headers, since
it is required as part of the configuration steps.
We also tweak the license md5sum, since the kernel now includes SPDX
headers in the
Introducing the 4.18 kernel as the 'newest' kernel for the oe core
release.
This update includes tweaked configs, carried forward BSPs, features
(aufs, yaffs2, preempt-rt) and has been tested on all arches for boot
and performance sanity.
Signed-off-by: Bruce Ashfield
---
Uprev'ing lttng to 2.10.7 to support 4.18+ kernels.
Signed-off-by: Bruce Ashfield
---
.../lttng/{lttng-modules_2.10.6.bb => lttng-modules_2.10.7.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-modules_2.10.6.bb =>
Adding two new configuration blocks/features to the 4.14+ kernel
variants.
One is for enabling selftest options, and the other is a collection
of kernel security/hardening configs.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb | 2 +-
From: Joshua Watt
Replace usage of os.utils.getstatusoutput() with direct subprocess
calls. Pass a modified environment and working directory where necessary
to bypass the need to execute in a shell.
Signed-off-by: Joshua Watt
Signed-off-by: Bruce Ashfield
---
Adding the preempt-rt BSP definition for qemuarm64 to allow -rt testing
on this ARCH.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.14.bb | 2 +-
Enabling the bpf feature for the standard kernel configurations
by default. Systemd (and other) userspace applications are looking
for BPF more often, and we get warnings such as this:
[ 12.810554] systemd[1]: File
/lib/systemd/system/systemd-journald.service:36 configures an IP
Reverting mm/vmstat.c: fix vmstat_update() preemption BUG, to fix
failures in the 4.14 -rt kernel.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb | 2 +-
Integrating Paul Gortmaker's -stable updates to 4.12 that comprise the
following changes:
f4fd7580487d Linux 4.12.28
d15dfc7d192f net: mvneta: eliminate wrong call to handle rx descriptor error
c7a79cbd2b44 net: mvneta: use proper rxq_number in loop on rx queues
f65f1aed2ef2 net:
Integratign the korg -stable updates that comprise the following
commits:
1aa1166eface Linux 4.14.62
7d29fb53439c jfs: Fix inconsistency between memory allocation and
ea_buf->max_size
59f35b983e8a xfs: don't call xfs_da_shrink_inode with NULL bp
6f021e4ef39a xfs: validate cached
During the re-working of kernel fragments and status output cleanup the
visibility for BSP level errors was dropped/removed.
The audit phase can detect errors, redefinition and invalid
configuration fragments. We control the visibility of these reports via
the existing KCONF_BSP_AUDIT_LEVEL
Hi all,
This series is a collection of fixes I've been carrying, as well as new
work for the upcoming release (in particular the 4.18 kernel work).
If there are isses with the 4.18 parts, everything else should be stand
alone enough for merging.
The breakdown of changes are:
- stable updates:
> Fixes problems which we have also seen on sumo branch. Thanks for this!
Sorry, spoke too soon. This fixes compilation on a few recipes in my tree
but there are still lots failures with the same error message. We had a hacky
patch to cmake as a workaround but that too causes some problems:
---
Hi Jair,
Thanks to let us know the background of the ticket.
I see some good feedback from people mentioned they are working on similar
solutions and should come out soon. We will continuously work on this ticket.
Regards,
-Yang (Young)
-Original Message-
From: Gonzalez Plascencia,
On 08/23/2018 11:06 PM, Hongxu Jia wrote:
On 2018年08月24日 04:47, Randy MacLeod wrote:
On 08/22/2018 05:16 AM, Hongxu Jia wrote:
While invoking mtools frequently, the unblocking request
s/unblocking/non-blocking/
I would read 'unblocking' as a request that results in the
system becoming
On Fri, Aug 24, 2018 at 02:33:46PM +0200, Pascal Bach wrote:
> This already got fixed in the toolchain file that is used during development
> in
> https://github.com/openembedded/openembedded-core/commit/cb42802f2fe1760f894a435b07286bca3a220364
>
> The toolchain file generated by the
This already got fixed in the toolchain file that is used during development
in
https://github.com/openembedded/openembedded-core/commit/cb42802f2fe1760f894a435b07286bca3a220364
The toolchain file generated by the cmake.bbclass however does not set
CMAKE_SYSROOT. Under certain circumstances this
Hi Martin,
On 24 August 2018 at 10:04, Martin Jansa wrote:
> One way to keep it allarch would be to package
> ${nonarch_base_libdir}/firmware/brcm/brcmfmac43430-sdio.AP6212.txt
> ${nonarch_base_libdir}/firmware/brcm/brcmfmac43430-sdio.MUR1DX.txt
> in 2 separate packages and handle
>
On 2018年08月24日 16:39, richard.pur...@linuxfoundation.org wrote:
On Fri, 2018-08-24 at 15:16 +0800, Hongxu Jia wrote:
Hi RP,
With this fix, we could not use yesterday's workaround fix
`git: create symlink rather than hardlink between bin/ and libexec/',
But it is no harm for us, btw, Ubuntu
One way to keep it allarch would be to package
${nonarch_base_libdir}/firmware/brcm/brcmfmac43430-sdio.AP6212.txt
${nonarch_base_libdir}/firmware/brcm/brcmfmac43430-sdio.MUR1DX.txt
in 2 separate packages and handle
${nonarch_base_libdir}/firmware/brcm/brcmfmac43430-sdio.txt
symlink with
It's better to refer to binaries in postinst script with
full path which also works on SDK when
/opt/nativesysroot/usr/bin is not in PATH.
Fixes install of nativesdk-nss:
Configuring nativesdk-nss.
/var/lib/opkg/info/nativesdk-nss.postinst: line 14: signlibs.sh: not found
Signed-off-by: Mikko
The devshell.bbclass set var-SHELL to var-DEVSHELL, and terminal.bbclass
initial var-SHELL with `bash'. Keep sync with it, use var-SHELL rather
than hardcoded `/bin/sh' as the shebang of wrapper script.
On Ubuntu host, default shell is dash (/bin/sh -> dash), even though
we assign var-SHELL with
On Fri, 2018-08-24 at 15:16 +0800, Hongxu Jia wrote:
> Hi RP,
>
> With this fix, we could not use yesterday's workaround fix
> `git: create symlink rather than hardlink between bin/ and libexec/',
>
> But it is no harm for us, btw, Ubuntu use symlink in git , and Fedora
> use hardlink in git
This reverts commit 2e61533e7c1b1cfd49dc771e907207f11a15c44f.
---
meta/classes/cpan.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/cpan.bbclass b/meta/classes/cpan.bbclass
index 926c6358a6..8e079e0d55 100644
--- a/meta/classes/cpan.bbclass
+++
Hi Jens
This patch has been pushed but its causing several
recipes to break, I can confirm that with reverting this fix
Here is list
http://errors.yoctoproject.org/Errors/Build/66538/
IMO, this fix should be reverted and delayed until
these regressions are fixed.
On Wed, Aug 22, 2018 at 2:04
This fixes issues mainly seen when mounting eMMC devices:
The wildcard /sys/block/${DEVBASE}/${DEVBASE}*1 matches both "mmcblk0p1"
and "mmcblk0boot1" for example, and this results in syntax errors. Fix this
by searching for a "partition" file instead, which only exists for real
partitions and not
CVE-2018-10689: blktrace (aka Block IO Tracing) 1.2.0, as used with the
Linux kernel and Android, has a buffer overflow in the dev_map_read
function in btt/devmap.c because the device and devno arrays are too
small, as demonstrated by an invalid free when using the btt program
with a crafted file.
Hi RP,
With this fix, we could not use yesterday's workaround fix
`git: create symlink rather than hardlink between bin/ and libexec/',
But it is no harm for us, btw, Ubuntu use symlink in git , and Fedora
use hardlink in git
[Ubuntu 1604/1804]
$ ls /usr/bin/git* -al
-rwxr-xr-x 1 root root
From: Kai Kang
The following changes since commit bd374216048581bcb3ea54d69998342525cf2da5:
util-linux: upgrade 2.32 -> 2.32.1 (2018-08-23 18:02:23 +0100)
are available in the Git repository at:
git://git.pokylinux.org/poky-contrib kangkai/sstate_prune
From: Kai Kang
Define variable SSTATE_PRUNE_OBSOLETEWORKDIR with '?=' in sstate.bbclass,
then it could be overwritten by user configuration.
Signed-off-by: Kai Kang
---
meta/classes/sstate.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/sstate.bbclass
While multiple hardlinks of binary located in different dirs,
there are also multiple hardlinks of separated debug info file
with the same binary name in same debug dirs. But in each dir,
only one debug file with original name works. Because all of
binary hardlinks have one `.gnu_debuglink' which
On Fri, 2018-08-24 at 11:46 +0800, Chen Qi wrote:
> The following statement was accidently removed. Add it back.
>
> values['ml'] = ['']
>
> This patch fixes the following error.
>
> Exception: KeyError: 'ml'
>
> Signed-off-by: Chen Qi
> ---
> meta/classes/utils.bbclass | 1 +
> 1 file
From: Mingli Yu
The below test hangs infinitely
$ ./run-ptest
Actually it stuck at test-gatt unit test and
the detailed test output as below:
$ unit/test-gatt -p /robustness/unkown-request -d
/robustness/unkown-request - init
/robustness/unkown-request - setup
/robustness/unkown-request -
Will resend V2 to update the typo from Upsteam-Status to Upstream-Status.
Thanks,
On 2018年08月24日 14:33, Patchwork wrote:
== Series Details ==
Series: bluez5: Fix ptest hang
Revision: 1
URL : https://patchwork.openembedded.org/series/13703/
State : failure
== Summary ==
Thank you for
== Series Details ==
Series: bluez5: Fix ptest hang
Revision: 1
URL : https://patchwork.openembedded.org/series/13703/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the
From: Mingli Yu
The below test hangs infinitely
$ ./run-ptest
Actually it stuck at test-gatt unit test and
the detailed test output as below:
$ unit/test-gatt -p /robustness/unkown-request -d
/robustness/unkown-request - init
/robustness/unkown-request - setup
/robustness/unkown-request -
53 matches
Mail list logo
