This commit should provide the same functionality as before, but
should make meta-oe xserver-nodm-init-2.0 obsolete as well as
keep systemd and sysvinit startup better in sync.
/etc/X11/Xserver is not called anymore: it is provided by both
x11-common and xserver-common with no useful differences (
1) Upgrade ruby from 2.2.5 to 2.3.1.
2) Modify LIC_FILES_CHKSUM, since the date in it has been changed, But the
LICENSE has not been changed.
Signed-off-by: Wang Xin
---
meta/recipes-devtools/ruby/ruby.inc | 2 +-
meta/recipes-devtools/ruby/{ruby_2.2.5.bb => ruby_2.3.1.b
On 31-08-16 18:57, Richard Purdie wrote:
On Wed, 2016-08-31 at 17:42 +0200, Enrico Scholz wrote:
Hello,
tslib is more or less mandatory for resistive touchscreens but it was
removed some days ago. This breaks e.g. meta-qt5 layer which depends
on it.
Is this removal really final (which would b
From: Jackie Huang
The libidn recipe is now buildable in distros which blacklist
GPL-3.0 without needing to be explicitly whitelisted (since it
provides at least one non GPLv3 package).
Signed-off-by: Jackie Huang
---
meta/conf/distro/include/default-distrovars.inc | 2 +-
1 file changed, 1 in
Richard Purdie writes:
>> tslib is more or less mandatory for resistive touchscreens but it was
>> removed some days ago. This breaks e.g. meta-qt5 layer which depends
>> on it.
>>
>> Is this removal really final (which would be really bad, because
>> resistive touchscreens are used e.g. in in
Can this get backported to krogoth? For now i am just putting my kernel in
RM_WORK_EXCLUDE and that seems to be working properly. Thanks for the hint!
On Wed, 31 Aug 2016 15:07:16 -0400 Martin Jansa
wrote
> You're not alone, this might be the same issue (fixed only in
> master
On 2016-08-31 4:54 AM, André Draszik wrote:
On Di, 2016-08-30 at 14:35 -0400, Bruce Ashfield wrote:
Can you clarify for me if you are are using SRC_URI items tagged with
'kmeta', i.e. a directory of fragments, or are you just adding .cfg/.scc
items directly to the SRC_URI ?
I do both:
in the
On Wed, 31 Aug 2016 11:55:44 Richard Purdie wrote:
> On Wed, 2016-08-31 at 13:48 +1200, Paul Eggleton wrote:
> > We should always shut down tinfoil when we're finished with it,
> > either
> > by explicitly calling the shutdown() method or by using it as a
> > context manager ("with ...").
>
> Coul
Signed-off-by: Alexander Kanavin
---
...hardocode-paths-to-perl-python-in-scripts.patch | 139 +
meta/recipes-gnome/gtk-doc/gtk-doc_1.25.bb | 3 +
2 files changed, 142 insertions(+)
create mode 100644
meta/recipes-gnome/gtk-doc/files/0001-Do-not-hardocode-paths-to-
gtk-doc requires Perl to be at least 5.18 which is more than some
distros provide (CentOS 7 in particular).
Signed-off-by: Alexander Kanavin
---
meta/recipes-gnome/gtk-doc/gtk-doc_1.25.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-gnome/gtk-doc/gtk-doc_1
You're not alone, this might be the same issue (fixed only in master):
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9352
On Wed, Aug 31, 2016 at 8:38 PM, Ian Geiser wrote:
>
> On Tue, 30 Aug 2016 10:13:52 -0400 Ian Geiser
> wrote
> > Greetings, I have an issue where I cannot s
On Tue, 30 Aug 2016 10:13:52 -0400 Ian Geiser
wrote
> Greetings, I have an issue where I cannot seem to build any external kernel
> module recipes. The one in particular is iscsitarget, but it seems none of
> them build now.
>
> It seems that what is happening is that the
On Wed, 2016-08-31 at 17:42 +0200, Enrico Scholz wrote:
> Hello,
>
> tslib is more or less mandatory for resistive touchscreens but it was
> removed some days ago. This breaks e.g. meta-qt5 layer which depends
> on it.
>
> Is this removal really final (which would be really bad, because
> resis
On 31 Aug 2016, at 4:21, wenzong fan wrote:
Finally I narrowed it down to pseudo commit:
Yes, that makes sense, we expect that there'd be potential issues, but I
didn't have a reproducer for any. Thanks! I'll see whether it reproduces
for me now. Any specific version of docker I might need?
Hello,
tslib is more or less mandatory for resistive touchscreens but it was
removed some days ago. This breaks e.g. meta-qt5 layer which depends on
it.
Is this removal really final (which would be really bad, because resistive
touchscreens are used e.g. in industrial environments)?
Enrico
--
I performed a verbose build on my build machine to see how it compares to
yours.
On Wed 2016-08-31 @ 05:41:06 AM, Trevor Woerner wrote:
> On Fri 2016-08-26 @ 05:51:54 PM, Martin Jansa wrote:
> | [2278/20239] CXX obj.host/third_party/icu/source/common/icuuc.servrbf.o
> | FAILED: obj.host/third_part
On Wed, 2016-08-31 at 17:21 +0800, wenzong fan wrote:
> Hi Experts,
>
> While I trying to build Yocto in Docker Container which using dumb-
> init
> as init system, I found the build always be stopped at some point
> and
> the container was terminated as well with below errors:
>
> Child p
With the update to the 4.8 kernel the versatile platform (and hence
qemuarm) has switched to a device tree boot.
We are using an ummodified mainline kernel versatilepb device tree,
which includes definitions of multiple amba devices. These devices
are not present in the qemu system emulation, henc
In a similar manner to diffconfig, tell the bitbake user where the
defconfig will be saved to.
Signed-off-by: Stefan Müller-Klieser
---
meta/classes/kernel.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index db42744..ed41125
Under what conditions is the explicit path to /usr/bin/perl required? Just
before your added code, it creates a symlink from the installed perl
location to the "t" directory where the tests are run. What if the perl
that was built was an alternate version and installed in /usr/local/bin?
-Bill
> From: Manjukumar Harthikote Matha [mailto:manjukumar.harthikote-
> ma...@xilinx.com]
>
> Can we do ${S}/config.mk ? Meaning
> sed -i 's/$(CROSS_COMPILE)ld$/$(CROSS_COMPILE)ld.bfd/g' ${S}/config.mk I
> dont have a setup for gold linker, If you can send the instructions I will
> give it
> a try
>
Need to reference config.mk file in source tree which is no longer
the current directory when using out of tree builds.
Signed-off-by: Andrew Goodbody
---
meta/recipes-bsp/u-boot/u-boot.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-bsp/u-boot/u-boot.inc
b/
On 31-08-16 15:22, Mike Looijmans wrote:
For example bootlogd needs devpts to be running, but bootlogd starts
at 07. Starting bootlogd early makes perfect sense, so the best option
here is to move devpts up to 06 to prevent this error message at boot:
cannot allocate pseudo tty: No such file or d
For example bootlogd needs devpts to be running, but bootlogd starts
at 07. Starting bootlogd early makes perfect sense, so the best option
here is to move devpts up to 06 to prevent this error message at boot:
cannot allocate pseudo tty: No such file or directory
Systems that have CONFIG_LEGACY_P
This allows 4.6 onward kernels to build, backported from upstream
master.
Signed-off-by: Richard Purdie
diff --git a/meta/recipes-kernel/cryptodev/cryptodev.inc
b/meta/recipes-kernel/cryptodev/cryptodev.inc
index ade7ef9..160ab30 100644
--- a/meta/recipes-kernel/cryptodev/cryptodev.inc
+++ b/me
On Wed, Aug 31, 2016 at 3:22 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2016-08-30 at 12:49 -0400, Bruce Ashfield wrote:
> > As of the 4.7 kernel qemuarm must be booted with a dtb. To allow
> > older and recent kernels to both boot qemuarm, we add the device
> > tree
On Wed, Aug 31, 2016 at 7:00 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> Just to update I have:
>
> * Put a runqemu patch in master-next that works with new and old
> kernels to handle the dtb issue
>
Hmm. I tested 4.4 and 4.8 with the ones that I did.
> * Updated the mu
On Wed, Aug 31, 2016 at 3:19 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2016-08-30 at 12:49 -0400, Bruce Ashfield wrote:
> > Updating the libc-headers to use the 4.8 kernel as the default.
> >
> > Signed-off-by: Bruce Ashfield
> > ---
> > meta/conf/distro/include/t
Changed deployment directory from DEPLOY_DIR_IMAGE/SDK_DEPLOY to
DEPLOYDIR to make sstate machinery to do final deployment and
generate manifest.
Renamed variable deploy_dir to deploy_dir_image in selftest code
to avoid confusion with DEPLOYDIR variable.
Updated the code of rootfs.py:Rootfs class
Adding populate_sdk task to SSTATE_TASKS should make sstate machinery
to generate manifest for deployed sdk artifacts and do final deployment
to SDK_DEPLOY.
Set stamp-extra-info flag for do_populate_sdk task. This flag is used
in the name of sstate manifest. Setting it to predetermined value for
p
Fire TaskArtifact MetaData event for deployment tasks when task
either completed or skipped. Event contains full task id
(recipe+task) and list of deployment artifacts from sstate
manifest.
This should allow Toaster to always get notified about deployment
artifacts produced by the build.
[YOCTO #
Adding image_complete task should make sstate machinery
to generate manifest for deployed images and do final
deployment to DEPLOY_DIR_IMAGE.
Made sure DEPLOYDIR doesn't contain images from past deployments
to prevent them to be included into sstate manifests.
Set stamp-extra-info flag for do_ima
SSTATE_SKIP_CREATION variable will be used to skip creation of
sstate .tgz files. It makes sense for image creation tasks as
tarring images and keeping them in sstate would consume a lot of
disk space.
Signed-off-by: Ed Bartosh
---
meta/classes/sstate.bbclass | 2 ++
1 file changed, 2 insertions
This is a preparation for changing deployment directory for image
and populate_sdk targets.
Introduced new variable DEPLOYDIR. Set it to current image/sdk
deployment locations.
Signed-off-by: Ed Bartosh
---
meta/classes/image.bbclass | 2 ++
meta/classes/populate_sdk_base.bbclass |
Hi,
This is a fix for Bug #9869 - Provide a per-target manifest of files which
were, or would have been, produced
The list of artifacts produced by deployment tasks (do_deploy,
do_image_complete and do_populate_sdk[_ext] is
obtained from sstate manifests and fired as a TaskArtifacts metadata ev
Just to update I have:
* Put a runqemu patch in master-next that works with new and old
kernels to handle the dtb issue
* Updated the musl patches in libc-headers
* Updated lttng-* to avoid build failures with 4.8
* Switched the default qemu kernel 4.4 -> 4.8 in poky so we get
testing of 4.8
On Wed, 2016-08-31 at 08:41 +0800, Mark Hatle wrote:
> On 8/30/16 9:05 PM, Joshua Lock wrote:
> > Pass appropriate options to tar invocations in copytree() and
> > copyhardlinktree() to ensure that any extended attributes on the
> > files
> > are preserved during the copy.
> >
> > We have to drop
On Wed, 2016-08-31 at 13:48 +1200, Paul Eggleton wrote:
> We should always shut down tinfoil when we're finished with it,
> either
> by explicitly calling the shutdown() method or by using it as a
> context manager ("with ...").
Could I trouble you to rebase this onto master-next please? It
curren
This avoids having the full paths of perl and python written
into gtk-doc scripts, which can trigger build failures and doesn't
work at all on targets.
Signed-off-by: Alexander Kanavin
---
meta/recipes-gnome/gtk-doc/gtk-doc_1.25.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
We need master for the changes to work with 4.8 kernels.
Signed-off-by: Richard Purdie
diff --git a/meta/recipes-kernel/lttng/lttng-modules_git.bb
b/meta/recipes-kernel/lttng/lttng-modules_git.bb
index d8a7d36..96bd945 100644
--- a/meta/recipes-kernel/lttng/lttng-modules_git.bb
+++ b/meta/recip
Drop backported patch.
Update ust configure option.
Update location of xml m4 file.
Signed-off-by: Richard Purdie
diff --git a/meta/recipes-kernel/lttng/lttng-tools/stop-using-SIGUNUSED.patch
b/meta/recipes-kernel/lttng/lttng-tools/stop-using-SIGUNUSED.patch
deleted file mode 100644
index bd4f7
Drop aarch64_be patch which is now upstream.
Update doc patch to apply to latest version.
Signed-off-by: Richard Purdie
diff --git
a/meta/recipes-kernel/lttng/lttng-ust/lttng-ust-add-support-for-aarch64_be.patch
b/meta/recipes-kernel/lttng/lttng-ust/lttng-ust-add-support-for-aarch64_be.patch
On Wed, Aug 31, 2016 at 11:25 AM, Jack Mitchell wrote:
> On 30/08/16 18:14, Andreas Müller wrote:
>>
>> since gcc6 we see many cmake/c++ based packets failing with:
>>
>> | fatal error: stdlib.h: No such file or directory
>>
>> a fix from gcc is not to expect [1] so work around by replacing '-isys
On Fri 2016-08-26 @ 05:51:54 PM, Martin Jansa wrote:
> === common-x86 (1) ===
> *
> meta-browser/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb:do_patch
It was pointed out to me that while re-organizing the chromium recipes I
dropped an important line in chromium-wayland. However th
On 30/08/16 18:14, Andreas Müller wrote:
since gcc6 we see many cmake/c++ based packets failing with:
| fatal error: stdlib.h: No such file or directory
a fix from gcc is not to expect [1] so work around by replacing '-isystem' by
'-I' for c++.
Build tested with many recipes in meta-qt5-extra
Hi Experts,
While I trying to build Yocto in Docker Container which using dumb-init
as init system, I found the build always be stopped at some point and
the container was terminated as well with below errors:
Child process timeout after 2 seconds.
Child process exit status 4: lock_he
On Di, 2016-08-30 at 14:35 -0400, Bruce Ashfield wrote:
> Can you clarify for me if you are are using SRC_URI items tagged with
> 'kmeta', i.e. a directory of fragments, or are you just adding .cfg/.scc
> items directly to the SRC_URI ?
I do both:
in the 1st layer, my kernel recipe boils down to:
Add patch to fix compile without libtasn headers.
Signed-off-by: Jussi Kukkonen
---
Changes since v1:
* Add patch to fix compile without libtasn headers
Thanks,
Jussi
...001-Use-correct-include-dir-with-minitasn.patch | 31 ++
.../gnutls/{gnutls_3.5.1.bb => gnutls_3.5.3.
On Fri, 2016-08-26 at 17:28 +0300, Alexander Kanavin wrote:
> This patchset adds gtk-doc support to OE-core. It requires running
> transient binaries during build time, which is achieved via qemu,
> and so there are all the same caveats as with gobject-introspection.
>
> Gtk-doc generation happens
On Mon, Aug 29, 2016 at 6:17 PM, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> On 08/29/2016 03:47 PM, Sujith H wrote:
>
>> From: Christopher Larson
>>
>> rdoc gets unhappy if this already exists, so remove it before building.
>>
>> Without this, it's possible to hit this error:
On Tue, 2016-08-30 at 12:49 -0400, Bruce Ashfield wrote:
> As of the 4.7 kernel qemuarm must be booted with a dtb. To allow
> older and recent kernels to both boot qemuarm, we add the device
> tree definitions only to recipes that need it (linux-yocto-dev)
> and make runqemu detect and use the dtb
On Tue, 2016-08-30 at 12:49 -0400, Bruce Ashfield wrote:
> Updating the libc-headers to use the 4.8 kernel as the default.
>
> Signed-off-by: Bruce Ashfield
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../linux-libc-headers/linux-libc-headers_4.8.bb
Hello,
It seems that this one causes build errors on arm AFAIK:
https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/933/steps/BuildImages/logs/stdio
// Robert
On 08/29/2016 10:30 PM, Alexander Kanavin wrote:
Signed-off-by: Alexander Kanavin
---
.../kexec/{kexec-tools_2.0.1
53 matches
Mail list logo
