On 2016-08-27 05:51 AM, Wang Xin wrote:
Upgrade qemu from 2.6.0 to 2.6.1.
Not merged yet even in master-next.
Hmmm, 2.7.0 is also available as of Sept 2nd.
It's too late for oe-core-2.2 - right?
The Changelog is interesting:
http://wiki.qemu.org/ChangeLog/2.7
and here are a couple of
On 09/07/2016 08:14 PM, Pau Espin Pedrol wrote:
2016-09-07 11:22 GMT+02:00 Chen Qi >:
Add new variable SYSTEMD_USER_SERVICE and SYSTEM_USER_AUTO_ENABLE
to manage user services. Their usage is like SYSTEMD_SERVICE and
From: Edwin Plauchu
When trying to re-test smart rpm tests. A fail arises
due to a linux user previously created upon the image.
W've added a few lines to delete such user and his home dir
when finishing test.
[YOCTO #9204]
Signed-off-by: Edwin Plauchu
Some of the meta-data from the 4.4 kernel was missing from the 4.8
branch. This resulted in some functionality drops and also a size/time
increase in the kernel build (due to debug being turned on).
With this resync, we now have the missing config restored.
Signed-off-by: Bruce Ashfield
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_4.8.bb | 18 +-
3 files changed, 13 insertions(+),
Integrating the following patch:
[
We try to make this change a generic extension, but it is
actually for a corner case. When a VM (qemu) gets a very limited
cpu bandwidth from host, which could be under a heavy load, the
existing 5000 ms timeout could occur and trigger error messages
Before the kernel tools were simplified and streamlined, there was code
which not only migrated a patch/cfg/scc to the kernel build tree, it
also migrated any subdirectories of those patches.
The effect of this data migration was that any other meta data in
a patch's directory structure would be
Previously merge_config.sh was wrapped by the configme script, configme
took the different KCONFIG_MODES as options, and used --allnoconfig
or --alldefconfig.
With the switch to merge_config.sh no longer being wrapped, the new
processing wasn't matching the existing values and only supported
Hi all,
Here are some fixes for the minor issues cased by the kern-tools update
and the recent 4.8 kernel introduction.
RP reported a build and footprint time increase for 4.8, that was due to
some missing kernel meta data that (re)enabled DEBUG and for the standard
kernel. commit [kernel-yocto:
When runqemu is invoked from a running bitbake instance it will be
unable to call `bitbake -e` due to the lock held by the calling
bitbake instance.
Our test code sets an OE_TMPDIR environment variable from which we
can infer/guess paths. Add code to do so when self.bitbake_e can't
be set, much
We aim to support Python 3.4+ whereas subprocess.run() was added
in Python 3.5.
Replace subprocess.run() with subprocess.check_output().
Signed-off-by: Joshua Lock
---
scripts/runqemu | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
Note: This patch is against master-next, as the Python 3 runqemu hasn't made it
to master yet.
This supercedes my earlier one patch series "Python3 runqemu: remove use of
subprocess.run()" (both versions)
Two fixes for the Python3 runqemu:
* Use of subprocess.run() in recent runqemu changes (by
Defeat automatic neon detection.
Signed-off-by: Joe Slater
---
meta/recipes-multimedia/webp/libwebp_0.5.1.bb |5 +
1 file changed, 5 insertions(+)
diff --git a/meta/recipes-multimedia/webp/libwebp_0.5.1.bb
b/meta/recipes-multimedia/webp/libwebp_0.5.1.bb
index
85f38a573fc47472ab792e813b6f6b6f0b1df112 in libcap drops
this dependency. Not seeing much necessity of using
EXTRA_OECONF (which doesn't seem effective) for the left,
we purge these code in libcap recipe.
Signed-off-by: Jianxun Zhang
---
Limited test is performed
Need some experts to review this patch series. I am not really
sure for if what I fixed is a valid case or if fix is the best
answer. The validation before submission is very limited too.
I ran into the compiling issue when build an application and
found this recipe cannot be built without
Select a genericx86-64 target and run
bitbake libcap
This error shows up:
-
pam_cap.c:19:34: fatal error: security/pam_modules.h:
No such file or directory
#include
^
compilation terminated.
Makefile:23:
Fixes [YOCTO #10146]
Signed-off-by: Henry Bruce
---
meta/classes/utils.bbclass | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/meta/classes/utils.bbclass b/meta/classes/utils.bbclass
index d56f51e..3c2a14f 100644
---
Hi Ola,
On Wed, 07 Sep 2016 06:23:15 Ola x Nilsson wrote:
> > From: openembedded-core-boun...@lists.openembedded.org
> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> > Of Paul Eggleton
> > Sent: den 6 september 2016 12:03
> >
> > Ensure we fetch submodules and set
On 2016-09-07 10:15 AM, Bruce Ashfield wrote:
On 2016-09-07 10:00 AM, Markus Lehtonen wrote:
On Wed, 2016-09-07 at 08:44 -0400, Bruce Ashfield wrote:
On 2016-09-07 8:33 AM, Markus Lehtonen wrote:
On Wed, 2016-09-07 at 07:56 -0400, Bruce Ashfield wrote:
On 2016-09-07 5:27 AM, Richard Purdie
Defeat automatic neon detection.
Signed-off-by: Joe Slater
---
meta/recipes-multimedia/webp/libwebp_0.5.1.bb |5 +
1 file changed, 5 insertions(+)
diff --git a/meta/recipes-multimedia/webp/libwebp_0.5.1.bb
b/meta/recipes-multimedia/webp/libwebp_0.5.1.bb
index
On Wed, Sep 7, 2016 at 9:27 AM, Burton, Ross wrote:
> On 6 September 2016 at 23:11, Henry Bruce wrote:
>
>> + if [[ "$libname" == *.so ]]; then
>>
>
> That's a lot of bashisms in one place ;)
>
> [ not [[
> = not ==
> *.so will need to be
On 6 September 2016 at 23:11, Henry Bruce wrote:
> + if [[ "$libname" == *.so ]]; then
>
That's a lot of bashisms in one place ;)
[ not [[
= not ==
*.so will need to be escaped in case it matches anything in cwd and expands.
Ross
--
We aim to support Python 3.4+ whereas subprocess.run() was added
in Python 3.5.
Replace subprocess.run() with subprocess.check_output().
Signed-off-by: Joshua Lock
---
scripts/runqemu | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
Note: This patch is against master-next, as the Python 3 runqemu hasn't made it
to master yet.
Use of subprocess.run() in recent runqemu changes (by me) elevates the Python 3
requirement from 3.4+ to 3.5+. Replace subprocess.run() with
subprocess.check_output(), as that is available in Python
We sed this file after the .pyc has been generated, so re-compile the .pyc to
ensure that it is up to date.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/python/python_2.7.12.bb | 1 +
1 file changed, 1 insertion(+)
diff --git
On Wed, 2016-09-07 at 15:10 +0100, Joshua Lock wrote:
> We aim to support Python 3.4+ whereas subprocess.run() was added
> in Python 3.5.
> Replace subprocess.run() with subprocess.check_output().
>
> Signed-off-by: Joshua Lock
> ---
> scripts/runqemu | 9 +
> 1
On 2016-09-07 10:00 AM, Markus Lehtonen wrote:
On Wed, 2016-09-07 at 08:44 -0400, Bruce Ashfield wrote:
On 2016-09-07 8:33 AM, Markus Lehtonen wrote:
On Wed, 2016-09-07 at 07:56 -0400, Bruce Ashfield wrote:
On 2016-09-07 5:27 AM, Richard Purdie wrote:
Hi Bruce,
I deliberately spaced out the
We aim to support Python 3.4+ whereas subprocess.run() was added
in Python 3.5.
Replace subprocess.run() with subprocess.check_output().
Signed-off-by: Joshua Lock
---
scripts/runqemu | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
Note: This patch is against master-next, as the Python 3 runqemu hasn't made it
to master yet.
Use of subprocess.run() in recent runqemu changes (by me) elevates the Python 3
requirement from 3.4+ to 3.5+. Replace subprocess.run() with
subprocess.check_output(), as that is available in Python
On 2016-09-07 10:00 AM, Markus Lehtonen wrote:
On Wed, 2016-09-07 at 08:44 -0400, Bruce Ashfield wrote:
On 2016-09-07 8:33 AM, Markus Lehtonen wrote:
On Wed, 2016-09-07 at 07:56 -0400, Bruce Ashfield wrote:
On 2016-09-07 5:27 AM, Richard Purdie wrote:
Hi Bruce,
I deliberately spaced out the
On Wed, 2016-09-07 at 08:44 -0400, Bruce Ashfield wrote:
> On 2016-09-07 8:33 AM, Markus Lehtonen wrote:
> > On Wed, 2016-09-07 at 07:56 -0400, Bruce Ashfield wrote:
> > > On 2016-09-07 5:27 AM, Richard Purdie wrote:
> > > > Hi Bruce,
> > > >
> > > > I deliberately spaced out the merges of
Hi,
On 09/06/2016 12:35 PM, André Draszik wrote:
On Sa, 2016-09-03 at 15:33 +0100, André Draszik wrote:
It looks like you are a few days to late - a slightly different patch was
applied upstream:
https://github.com/libffi/libffi/pull/272
It'd be good if you could update your OE patch to
On Wed, 2016-09-07 at 08:44 -0400, Bruce Ashfield wrote:
> On 2016-09-07 8:33 AM, Markus Lehtonen wrote:
> > On Wed, 2016-09-07 at 07:56 -0400, Bruce Ashfield wrote:
> > > On 2016-09-07 5:27 AM, Richard Purdie wrote:
> > > > Hi Bruce,
> > > >
> > > > I deliberately spaced out the merges of
On 2016-09-07 8:33 AM, Markus Lehtonen wrote:
On Wed, 2016-09-07 at 07:56 -0400, Bruce Ashfield wrote:
On 2016-09-07 5:27 AM, Richard Purdie wrote:
Hi Bruce,
I deliberately spaced out the merges of various things so we could get
performance measurements of the system as it happened.
On Wed, 2016-09-07 at 07:56 -0400, Bruce Ashfield wrote:
> On 2016-09-07 5:27 AM, Richard Purdie wrote:
> > Hi Bruce,
> >
> > I deliberately spaced out the merges of various things so we could get
> > performance measurements of the system as it happened. Unfortunately
> > the 4.8 kernel appears
2016-09-07 11:22 GMT+02:00 Chen Qi :
> Add new variable SYSTEMD_USER_SERVICE and SYSTEM_USER_AUTO_ENABLE
> to manage user services. Their usage is like SYSTEMD_SERVICE and
> SYSTEMD_AUTO_ENABLE.
>
> [YOCTO #7800]
>
> Signed-off-by: Chen Qi
> ---
>
On 2016-09-07 5:27 AM, Richard Purdie wrote:
Hi Bruce,
I deliberately spaced out the merges of various things so we could get
performance measurements of the system as it happened. Unfortunately
the 4.8 kernel appears to regress the kernel build time quite
significantly:
The raw data:
From: Jack Mitchell
when using a toolchain not shipped by OE core such as linaro we
can't be sure what the std will be set to. Set to compile as c99
which is the lowest version supported.
Signed-off-by: Jack Mitchell
---
Pau Espin Pedrol
2016-09-07 11:22 GMT+02:00 Chen Qi :
> Make use of the new SYSTEMD_USER_SERVICE variable added in systemd.bbclass
> to manage user services in pulseaudio-server package.
>
> Signed-off-by: Chen Qi
> ---
>
Paul Eggleton writes:
>> I would read the file as a binary ('rb' instead of 'r') and make the
>> GitApplyTree.* strings a 'bytes' type.
>
> The code is not just passing the data through, it is actually processing
> it. If we did what you propose wouldn't it make
On 06/09/16 22:41, Andreas Müller wrote:
CMake sets all imported headers as system headers. This causes trouble for c++
projects [1].
Thanks to Jack Mitchell for pointing to the setting [2]. Build tested upon
meta-qt5-extra-world which had lots of fallout before.
[1]
It's probably worth updating the documentation too... this is a usefull
feature and it deserves the exposure
Regards
Jeremy Rosen
On 07/09/2016 11:22, Chen Qi wrote:
The following changes since commit 55bb6816aca39bfa25d4f7e2158a57a5f0ac1cca:
oeqa.buildperf: correct globalres time
Hi Bruce,
I deliberately spaced out the merges of various things so we could get
performance measurements of the system as it happened. Unfortunately
the 4.8 kernel appears to regress the kernel build time quite
significantly:
The raw data:
The following changes since commit 55bb6816aca39bfa25d4f7e2158a57a5f0ac1cca:
oeqa.buildperf: correct globalres time format (2016-09-06 10:24:00 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/systemd-user-units
Add '--global' option to our own systemctl script to manage user services.
[YOCTO #7800]
Signed-off-by: Chen Qi
---
.../systemd/systemd-systemctl/systemctl| 45 ++
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git
Make use of the new SYSTEMD_USER_SERVICE variable added in systemd.bbclass
to manage user services in pulseaudio-server package.
Signed-off-by: Chen Qi
---
meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Add new variable SYSTEMD_USER_SERVICE and SYSTEM_USER_AUTO_ENABLE
to manage user services. Their usage is like SYSTEMD_SERVICE and
SYSTEMD_AUTO_ENABLE.
[YOCTO #7800]
Signed-off-by: Chen Qi
---
meta/classes/systemd.bbclass | 17 +
1 file changed, 13
libpcre uses CCLD_FOR_BUILD as the name of the host command to use for
linking. This is not a standard autotools symbol but particular to this
recipe. We need to set it explicitely
Signed-off-by: Jérémy Rosen
---
meta/recipes-support/libpcre/libpcre_8.39.bb | 2 ++
1 file
Signed-off-by: Jérémy Rosen
---
meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch
| 39 +++
meta/recipes-core/glibc/glibc_2.24.bb
| 3 ++-
2 files changed,
version 5.4.1 of rpm was not properly distclean before release, which
causes problems when cross-compiling.
The previous version this recipe called make distclean, but that would
trigger a call to ./configure which would fail when no gcc is
available and make the whole do_configure fail further
The KConfig infrastructure needs to build HOST binaries in order to
provide its infratstructure. Yocto needs to force the HOSTCC and HOSTCPP
variables to BUILD_CC and BUILD_CPP to make sure that the proper compiler
is used when compiling host binaries
---
meta/recipes-core/busybox/busybox.inc | 2
Signed-off-by: Jérémy Rosen
---
meta/classes/sanity.bbclass | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index 202b5db..f17e2d4 100644
--- a/meta/classes/sanity.bbclass
+++
The KConfig infrastructure needs to build HOST binaries in order to
provide its infratstructure. Yocto needs to force the HOSTCC and HOSTCPP
variables to BUILD_CC and BUILD_CPP to make sure that the proper compiler
is used when compiling host binaries
---
The BUILD_* family of variables allow the user to specify the name of the host
compiler to use at build time. This feature is particularly important for long
term maintainance. Future versions of gcc might not be compatible with old
yocto distributions and we can't assume that "gcc" is the correct
cross-compilers are native recipes that need to be compiled by the host's
compiler. However they do not use native.bbclass
As a consequence, the various CC, CXX etc environment variables are not
correctly set and they will not honor the host compiler name provided
by the BUILD_* variables.
The KConfig infrastructure needs to build HOST binaries in order to
provide its infratstructure. Yocto needs to force the HOSTCC and HOSTCPP
variables to BUILD_CC and BUILD_CPP to make sure that the proper compiler
is used when compiling host binaries
---
meta/classes/kernel.bbclass | 1 +
1 file
The PACKAGECONFIG's value doens't go into EXTRA_OECONF, but
PACKAGECONFIG_CONFARGS.
Fixed:
pciutils-3.5.1: libpci rdepends on libudev, but it isn't a build dependency,
missing eudev in DEPENDS or PACKAGECONFIG? [build-deps]
pciutils-3.5.1: pciutils rdepends on libudev, but it isn't a build
The following changes since commit 55bb6816aca39bfa25d4f7e2158a57a5f0ac1cca:
oeqa.buildperf: correct globalres time format (2016-09-06 10:24:00 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/3fixes
Fixed:
WARNING: QA Issue: lighttpd: configure was passed unrecognised options:
--without-memcache [unknown-configure-option]
Signed-off-by: Robert Yang
---
meta/recipes-extended/lighttpd/lighttpd_1.4.41.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Fixed:
apt-1.2.12: apt rdepends on lz4, but it isn't a build dependency, missing lz4
in DEPENDS or PACKAGECONFIG? [build-deps]
Signed-off-by: Robert Yang
---
meta/recipes-devtools/apt/apt_1.2.12.bb | 1 +
1 file changed, 1 insertion(+)
diff --git
On Tue, Sep 6, 2016 at 10:23 PM, Khem Raj wrote:
>
> > On Aug 29, 2016, at 5:45 AM, Sujith H wrote:
> >
> > From: Christopher Larson
> >
> > rdoc gets unhappy if this already exists, so remove it before building.
> >
> > Without
On 7 September 2016 at 03:58, Wang Xin
wrote:
> 1) Upgrade wayland from 1.11.0 to 1.11.93.
> 2) Delete one patch, since it is no use.
> 0001-scanner-Use-unit32_t-instead-of-uint.patch
>
1.11.93 is a release candidate, not a release, so we'd go straight from
Try to be more intelligent when splitting out recipe name, epoch,
version and revision from the buildstat directory name. Previous
assumption was that package versions never contain a dash but obviously
that is not necessarily true. The new assumption is that the package
version starts with a
Be sure to take the latest buildstats if multiple buildstats are found.
Signed-off-by: Markus Lehtonen
---
meta/lib/oeqa/buildperf/base.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/buildperf/base.py
Two small miscellanious fixes to build perf tests.
Markus Lehtonen (2):
oeqa.buildperf: try harder when splitting 'nevr' string
oeqa.buildperf: be sure to use the latest buildstats
meta/lib/oeqa/buildperf/base.py | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
--
2.6.6
--
On 7 Sep 2016, at 1:32, wenzong fan wrote:
Yes, I believe it's not a 100 reproducible issue. Maybe you could run
it with other builds in parallel and try it 3 times or more.
I can try, but that might need bigger hardware than I have to hand at
the moment.
-s
--
On 09/02/2016 10:10 AM, Seebs wrote:
On 1 Sep 2016, at 20:33, wenzong fan wrote:
No, I didn't think it's related to any specific docker version.
I tested it on "Docker version 1.7.1, build 786b29d" & "Docker version
1.11.2, build b9f10c9".
BTW, I also tested the docker build w/o dumb-init,
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of Paul Eggleton
> Sent: den 6 september 2016 12:03
>
> Ensure we fetch submodules and set SRC_URI correctly when pointing to a
> git repository that contains
68 matches
Mail list logo