Hello Khem,
Long-wait for any feedback !!!
Mit freundlichen Grüßen / Best regards
Rajendran Vignesh
RBEI/ECF33
Tel. +91 422 67-65103
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Friday, July 06, 2018 10:21 AM
To: Vignesh Rajendran (RBEI/ECF3)
Cc: Patches and discussions about the oe-core
On 08/09/2018 10:10 AM, Daniel Díaz wrote:
> Hello!
>
>
> On 26 July 2018 at 09:38, Daniel Díaz wrote:
>> Once another header #includes , there is a
>> potential recursion going on because the
>> multilib_header_wrapper.h #includes again!
>>
>> This should not happen because an __arm__
On 08/03/2018 04:55 AM, Alejandro Enedino Hernandez Samaniego wrote:
> We can give it a try but do you have a specific example of how it fails
> for you?
> Because I know theres lots of nested sccs on the yocto kernel cache, but
> in that case
> it wouldn't be a problem since this bug is
Avoids producing different build results in different timezones.
Uses UTC with SOURCE_DATE_EPOCH.
Signed-off-by: Christopher Clark
---
meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.3.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
When using a recipe space kernel-meta, scc files are added through
SRC_URI, but they may include corresponding kernel fragments or patches
that are not necessarily in SRC_URI.
For bitbake, this is not a problem because the kernel-yocto class adds
the path where the .scc file was found to includes
Converts sstate so that it can use a hash equivalence server to
determine if a task really needs to be rebuilt, or if it can be restored
from a different (equivalent) sstate object.
The dependency IDs are cached persistently using persist_data. This has
a number of advantages:
1) Dependency IDs
Implements a reference implementation of the hash equivalence server.
This server has minimal dependencies (and no dependencies outside of the
standard Python library), and implements the minimum required to be a
conforming hash equivalence server.
Signed-off-by: Joshua Watt
---
If the dependency ID is being used to track task dependencies, the hash
validation function needs to know about it in order to properly validate
the hash.
TODO: This currently isn't going to be backward compatible with older
hashvalidate functions. Is that necessary, and if so are there any
Handles the argument that passes task dependency IDs in the hash check
function, as it is now required by bitbake
Signed-off-by: Joshua Watt
---
meta/classes/sstate.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/sstate.bbclass
The dependency ID is now passed to the task in the BB_DEPID variable
Signed-off-by: Joshua Watt
---
bitbake/bin/bitbake-worker | 7 ---
bitbake/lib/bb/runqueue.py | 10 ++
2 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/bitbake/bin/bitbake-worker
Adds a test suite for testing the persistent data cache
Signed-off-by: Joshua Watt
---
bitbake/bin/bitbake-selftest | 1 +
bitbake/lib/bb/tests/persist_data.py | 188 +++
2 files changed, 189 insertions(+)
create mode 100644
Requests the task dependency ID from siggen and tracks it
Signed-off-by: Joshua Watt
---
bitbake/lib/bb/runqueue.py | 25 +
1 file changed, 17 insertions(+), 8 deletions(-)
diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
index
The mechanism used to get the hash for a stamp file is split out so that
it can be overridden by derived classes
Signed-off-by: Joshua Watt
---
bitbake/lib/bb/siggen.py | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/bitbake/lib/bb/siggen.py
Abstracts the function to get the dependency ID for a task so it can
return something other that the taskhash
Signed-off-by: Joshua Watt
---
bitbake/lib/bb/siggen.py | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/bitbake/lib/bb/siggen.py b/bitbake/lib/bb/siggen.py
sqlite gets really angry if a database is closed across a fork() call,
and will give all sorts of messages ranging from I/O errors to database
corruption errors. To deal with this, close all database connections
before forking, and reopen them (lazily) on the other side.
Signed-off-by: Joshua
Pass the task hash as a parameter to the 'runtask' message instead of
passing the entire dictionary of hashes when the worker is setup. This
is possible less efficient, but prevents the worker taskhashes from
being out of sync with the runqueue in the event that the taskhashes in
the runqueue
Turns off the shared cache. It isn't a significant factor in performance
(now that WAL is enabled), and is a really bad idea to have enabled in
processes that fork() (as bitbake it prone to do).
Signed-off-by: Joshua Watt
---
bitbake/lib/bb/persist_data.py | 6 --
1 file changed, 6
Constructs the "key" column in the persistent database as a non-NULL
primary key. This significantly speeds up lookup operations in large
databases.
Signed-off-by: Joshua Watt
---
bitbake/lib/bb/persist_data.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Enabling the write ahead log improves database reliability, speeds up
writes (since they mostly happen sequentially), and speeds up readers
(since they are no longer blocked by most write operations). The
persistent database is very read heavy, so the auto-checkpoint size is
reduced from the
The original implementation of persistent data executed all SQL
statements via sqlite3.Connection.execute(). Behind the scenes, this
function created a sqlite3 Cursor object, executed the statement, then
returned the cursor. However, the implementation did not account for
this and failed to close
Adds a compatibility wrapper around os.fork() that backports the ability
to register fork event handlers (os.register_at_fork()) from Python 3.7
Signed-off-by: Joshua Watt
---
bitbake/bin/bitbake-worker | 2 +-
bitbake/lib/bb/fork.py | 71 ++
2 files
These patches are a first pass at implementing a hash equivalence server
in bitbake & OE.
Apologies for cross-posting this to both the bitbake-devel and
openembedded-devel; this work necessarily intertwines both places, and
it is really necessary to look at both parts to get an idea of what is
Thank you Andreas, Martin and Alex for your responses.
I will follow your leads and hopefully will be able to do it.
Regards
Ankur
On Fri 10 Aug, 2018, 4:16 AM Andreas Müller,
wrote:
> On Thu, Aug 9, 2018 at 2:40 PM, Martin Jansa
> wrote:
> > For daisy you probably don't have support for
When building with `clang -target bpf` using the
multilib_header, a recursion was unavoidable because
bits/wordsize.h would #include itself, still lacking
a definition for __MHWORDSIZE or __WORDSIZE.
Signed-off-by: Daniel Díaz
---
scripts/multilib_header_wrapper.h | 4 +++-
1 file changed, 3
As reported by ChenQi, leaving bits/wordsize.h out of being
multilibbed introduced a problem in building the SDK for
arm64:
Error: Transaction check error:
file /usr/include/bits/wordsize.h conflicts between attempted installs of
lib32-libc6-dev-2.27-r0.armv7vet2hf_vfp and
Hello!
On 26 July 2018 at 09:38, Daniel Díaz wrote:
> Once another header #includes , there is a
> potential recursion going on because the
> multilib_header_wrapper.h #includes again!
>
> This should not happen because an __arm__ (32-bits) or an
> __aarch64__ (64-bits) environment guarantees
Hello!
On 30 July 2018 at 21:01, ChenQi wrote:
> This patch causes a regression in multilib SDK for qemuarm64.
>
> Error: Transaction check error:
> file /usr/include/bits/wordsize.h conflicts between attempted installs of
> lib32-libc6-dev-2.27-r0.armv7vet2hf_vfp and
On Thu, Aug 9, 2018 at 2:40 PM, Martin Jansa wrote:
> For daisy you probably don't have support for PACKAGECONFIG_CONFARGS which
> was added in Yocto 2.1 krogoth.
>
I remember doing similar for other reasons. We have images based on
jethro (ok - daisy is a bit older) with later Qt's. Our builds
Hi,
I am writing this email with reference to upgrading openssl to 1.1 in
open-embedded packages in yocto project.
I am using older version of open embedded (yocto project version:
2.3872.08518) for one of my projects and would like to upgrade openssl only.
Please help me identify the
Raphael Kubo da Costa writes:
> The upstream commit merges several bug fixes into the GCC 6 branch; we are
> specifically interested in the fix for GCC bug 83623, which was causing
> Chromium 68+ to fail to build on ARM and aarch64 with
>
> In file included from
>
On 08/03/2018 05:48 AM, Hongzhi.Song wrote:
Hw breakpoint is based on hardware.
We need a better commit log explanation.
Was this test added in error originally?
Can you explain briefly whether their are any
qemu configurations would be able to efficiently
test the hardware breakpoint
On 08/09/2018 04:54 AM, Richard Purdie wrote:
On Wed, 2018-08-08 at 13:27 -0400, Randy MacLeod wrote:
On 07/28/2018 04:53 AM, Anuj Mittal wrote:
rm_work if enabled leads to some tests failing that rely on
artifacts being present. Check if rm_work.bbclass is included and
show an error and exit
* let manpages.bbclass to enable manpages PACKAGECONFIG based on
api-documentation DISTRO_FEATURES
PACKAGECONFIG_append_class-target = " ${@bb.utils.contains('DISTRO_FEATURES',
'api-documentation', 'manpages','', d)}"
* it's true that building man-pages without manpages being enabled
For daisy you probably don't have support for PACKAGECONFIG_CONFARGS which
was added in Yocto 2.1 krogoth.
Read the meta-qt5 commit about PACKAGECONFIG_CONFARGS.
It's relatively easy to fix (I was also using older OE with newer Qt5), but
it's unsupported, so you're on your own and you need to
2018-08-09 12:10 GMT+02:00 Ankur Tyagi :
> Our product is based upon 'daisy' branch (I know it's pretty old !) and now
> we have a need to support BLE in it (typical business case).
>
> My inner-self says it's the right time to upgrade everything but from
> business unit point of view, best would
configure tests crypt() existence with:
dnl We test for crypt() specially. On Linux (and others?) it resides in libcrypt
dnl but we don't want link all binaries to -lcrypt, just dropbear server.
dnl OS X doesn't need -lcrypt
AC_CHECK_FUNC(crypt, found_crypt_func=here)
AC_CHECK_LIB(crypt, crypt,
Signed-off-by: Martin Jansa
---
meta/recipes-kernel/perf/perf.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
index 2c6bbb42b9..ccd2c7d11b 100644
--- a/meta/recipes-kernel/perf/perf.bb
+++
== Series Details ==
Series: "go(-dep): add INSANE_SKIP for ..." and 2 more
Revision: 1
URL : https://patchwork.openembedded.org/series/13444/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
* I'm not using glide, so I'm not going to fix it proplerly,
it was just bothering me in world builds
* this is reproducible only with ptest in DISTRO_FEATUREs (for aarch64
issue) and included security_flags.inc, more specifically with the PIE
flags, so alternative work around is:
* I'm not using go or go-dep, so I'm not going to fix it proplerly,
it was just bothering me in world builds
* this is reproducible only with ptest in DISTRO_FEATUREs (for aarch64
issue) and included security_flags.inc, more specifically with the PIE
flags, so alternative work around is:
---
meta/recipes-kernel/perf/perf.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
index 2c6bbb42b9..ccd2c7d11b 100644
--- a/meta/recipes-kernel/perf/perf.bb
+++ b/meta/recipes-kernel/perf/perf.bb
@@ -39,7
Hi,
Our product is based upon 'daisy' branch (I know it's pretty old !) and now
we have a need to support BLE in it (typical business case).
My inner-self says it's the right time to upgrade everything but from
business unit point of view, best would be to upgrade "just enough" to get
BLE
On Thu, 2018-08-09 at 10:00 +0100, André Draszik wrote:
> I should maybe explain my ultimate goal here:
>
> meta-java is completely self-hosted, which is nice. But to be able to
> compile OpenJDK v8, various other Java compilers need to be compiled
> first.
> This of course means that all those
On Sun, 2018-06-17 at 14:13 +0100, Richard Purdie wrote:
> On Tue, 2018-05-22 at 13:25 +0100, André Draszik wrote:
> > From: André Draszik
> >
> > Currently, a dependency on any -native recipe will pull in
> > all dependencies of that -native recipe in the recipe
> > sysroot. This behaviour
On Wed, 2018-08-08 at 13:27 -0400, Randy MacLeod wrote:
> On 07/28/2018 04:53 AM, Anuj Mittal wrote:
> > rm_work if enabled leads to some tests failing that rely on
> > artifacts being present. Check if rm_work.bbclass is included and
> > show an error and exit if it is.
> >
> > Fixes [YOCTO
Fix nullptr deref with XPath logic ops
If the XPath stack is corrupted, for example by a misbehaving extension
function, the "and" and "or" XPath operators could dereference NULL
pointers. Check that the XPath stack isn't empty and optimize the
logic operators slightly.
CVE: CVE-2018-14404
Setting CMAKE_SYSROOT in the toolchain file allows CMake to correctly
remove user-provided system include directories pointing to
/usr/include. The mentioned projects failed with "stdlib.h:
No such file or directory #include_next ".
Signed-off-by: Urs Fässler
Signed-off-by: Raphael Freudiger
47 matches
Mail list logo
