Packages which depends on attr headers fail due
to uint32_t not being defined, this needed header
to include sys/types.h
Signed-off-by: Khem Raj
---
.../attr/0001-Use-stdint-types-consistently.patch | 69 ++
meta/recipes-support/attr/attr_2.4.47.bb
Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
because ELF core parsing fails with errors like:
Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
Please report this as bug. Using RANGE_RESERVED now.
...
ELF core (kcore) parse failed
Cannot load
Use ucontext_t not struct ucontext in linux-unwind.h files.
Current glibc no longer gives the ucontext_t type the tag struct
ucontext, to conform with POSIX namespace rules. This requires
various linux-unwind.h files in libgcc, that were previously using
struct ucontext, to be fixed to use
When one chooses to use gcc 6.3 with
GCCVERSION = "6.3%"
bitbake libgcc fails.
This patch fixes building this particular issue.
However, there is at least one more recipe that fails with gcc 6.3
(mesa_17.1.7.bb).
Juro Bystricky (1):
gcc-6.3.inc: Use ucontext_t not struct ucontext.
On 14 September 2017 at 22:11, Martin Jansa wrote:
> As of today qemu, qemu-native and nativesdk-qemu can be built with
> virglrenderer, sdl2 and spice support.
>
> I've tested core-image-sato running in qemu-native from headless Gentoo
> chroot, with spicy client on
On Wed, Sep 13, 2017 at 2:18 PM, Richard Purdie
wrote:
> On Wed, 2017-09-13 at 14:12 -0700, Alistair Francis wrote:
>> On Wed, Sep 13, 2017 at 2:09 PM, Richard Purdie
>> wrote:
>> >
>> > On Wed, 2017-09-13 at 13:55 -0700,
On 2017-09-14 1:25 PM, Martin Jansa wrote:
Today I've created backup of this broken state with:
OE raspberrypi3-64@luneos ~/build/owpb/webos-ports/tmp-glibc $ mkdir
kernel-bad
OE raspberrypi3-64@luneos ~/build/owpb/webos-ports/tmp-glibc $ cp -ra
work-shared/raspberrypi3-64/
== Series Details ==
Series: Revamp the Go support (rev10)
Revision: 10
URL : https://patchwork.openembedded.org/series/8697/
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
Bruce,
On 09/14/2017 06:13 AM, Bruce Ashfield wrote:
.. and if anyone notices, there's a kernel part to this CVE as well.
I've applied to fix to all the active linux-yocto kernels, and the
change will be part
of my consolidated pull request that comes out later today.
thanks. I will merge
This adds the meta-go-toolchain. It enables the generation of a Go
toolchain allowing for cross compiling for target architecture.
Signed-off-by: Otavio Salvador
---
Changes in v10:
- new patch
meta/recipes-core/meta/meta-go-toolchain.bb | 12
From: Matt Madison
* Add patch for go's make script to allow for
build system != host system
* Add dependencies on the appropriate crosssdk recipes,
and use the crosssdk C compiler and linker
* Remove bashism in the wrapper script
* Restrict installation to only the
From: Matt Madison
Switch to using an external linker for nativesdk
go, go-runtime, and go package builds, which works
more reliably when building 32-bit SDKs.
Signed-off-by: Matt Madison
Signed-off-by: Otavio Salvador
---
From: Matt Madison
The go build tool creates working directories under
$TMPDIR for all of its processing. Create a directory
under ${WORKDIR} for this and point TMPDIR at it during
compilation, so that systems that have a relatively
small /tmp filesystems can still compile
From: Matt Madison
* The _FOR_TARGET variables need to include SDKNATIVEPATH
* Install tools (cmd) only, and for the build host
* Remove unnecessary FILES setting
Corrects some errors when the build host architecture
is different from the SDKMACHINE's.
Signed-off-by: Matt
This improves the Go support on OE-Core.
We are trying to port as much as possible work done by Matt on
meta-golang back to OE-Core and also to avoid carrying old releases as
there is no need to support more versions of Go toolchain.
This fixes issues in existing support as well as add support
Today I've created backup of this broken state with:
OE raspberrypi3-64@luneos ~/build/owpb/webos-ports/tmp-glibc $ mkdir
kernel-bad
OE raspberrypi3-64@luneos ~/build/owpb/webos-ports/tmp-glibc $ cp -ra
work-shared/raspberrypi3-64/
work/raspberrypi3_64-webos-linux/linux-raspberrypi/ kernel-bad
Upgrade to a new development release and drop patches applied on upstream.
For a full release notes, please see:
https://mesa3d.org/relnotes/17.2.0.html
Signed-off-by: Fabio Berton
---
...1-ac-fix-build-after-LLVM-5.0-SVN-r300718.patch | 40 --
On Thu, 14 Sep 2017 15:53:09 +0100
"Burton, Ross" wrote:
> Example:
>
> path mismatch [5 links]: ino 27539515 db
> '/data/poky-tmp/master/build/work/corei7-64-poky-linux/dbus/1.10.20-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-ld.bfd'
> req
>
On 13 September 2017 at 23:09, Seebs wrote:
> On Wed, 13 Sep 2017 22:46:59 +0200
> Martin Jansa wrote:
>
> > And some-other-unrelated-file is really some different file, not
> > just hardlink to the same file from some different directory (like
> >
On Thu, 14 Sep 2017 00:28:34 +0200
Martin Jansa wrote:
> OK, thanks.
>
> Any insights to the first issue described in commit message? That we
> know that is an Actual Problem, but hard to reproduce it.
This one?
glibc-locale-2.26:
glibc-locale:
I'm sorry for noise, I've reproduced it in LuneOS raspberrypi build and the
root cause is wrongly used override in this bbappend:
https://github.com/webOS-ports/meta-rpi-luneos/blob/3b76e0b7d554e937263e685854819ab8454ebe35/recipes-core/systemd/systemd_%25.bbappend
On Thu, Sep 14, 2017 at 12:05
Signed-off-by: Randy MacLeod
---
README.qemu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.qemu b/README.qemu
index fca04b1..9f56b7d 100644
--- a/README.qemu
+++ b/README.qemu
@@ -7,7 +7,7 @@ are currently supported in 32 and 64 bit
Integrating the following commit:
[
commit 16de0149674ed12d983b77a453852ac2e64584b4
Author: Ben Seri
Date: Sat Sep 9 23:15:59 2017 +0200
Bluetooth: Properly check L2CAP config option output buffer length
Validate the output buffer length for L2CAP config
Integrating the following commit:
[
commit 16de0149674ed12d983b77a453852ac2e64584b4
Author: Ben Seri
Date: Sat Sep 9 23:15:59 2017 +0200
Bluetooth: Properly check L2CAP config option output buffer length
Validate the output buffer length for L2CAP config
Integrating the following commit:
[
commit 16de0149674ed12d983b77a453852ac2e64584b4
Author: Ben Seri
Date: Sat Sep 9 23:15:59 2017 +0200
Bluetooth: Properly check L2CAP config option output buffer length
Validate the output buffer length for L2CAP config
Integrating the following commit:
[
commit 16de0149674ed12d983b77a453852ac2e64584b4
Author: Ben Seri
Date: Sat Sep 9 23:15:59 2017 +0200
Bluetooth: Properly check L2CAP config option output buffer length
Validate the output buffer length for L2CAP config
Integrating the -stable update with the following commits:
573b59e17e37 Linux 4.4.87
d95827490c39 crypto: algif_skcipher - only call put_page on referenced and
used pages
ab3ee6b53d67 epoll: fix race between ep_poll_callback(POLLFREE) and
ep_free()/ep_remove()
628212c89fae kvm:
The aufs4 now has a 4.12 port, so we can integrate it into the
reference kernel and stay consistent with previous releases.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb | 4 ++--
Integrating the korg stable update comprising the following commits:
6ff98e8e5d24 Linux 4.12.12
ce4ef9346d9f rtlwifi: Fix fallback firmware loading
21da5e36f41e rtlwifi: Fix memory leak when firmware request fails
3ef5220bdba7 of/device: Prevent buffer overflow in of_device_modalias()
Introducing the following configuration features:
d67d2221cc2d bpf: add bpf kernel config
3f9fb678aa31 sysrq: add sysrq kernel config
729eb982ffd8 kexec/kdump: Add config fragments
e00e63ef3068 kdump: add config fragments
Signed-off-by: Bruce Ashfield
---
Integrating the korg -stable updates that comprise the following commits:
f07cb3489cff Linux 4.9.49
8bc67f67b763 drm/bridge: adv7511: Switch to using
drm_kms_helper_hotplug_event()
8b5a7e443622 drm/bridge: adv7511: Use work_struct to defer hotplug handing
to out of irq context
Hi all,
This is the last set of -stable and meta data changes for the 2.4
release window. I've also brough aufs4 into the 4.12 tree to keep
it feature consistent with all the previous linux-yocto kernels
(and given some bug reports, folks are using the aufs support).
They are -stable updates,
On 13 September 2017 at 23:08, Seebs wrote:
> On Wed, 13 Sep 2017 22:50:32 +0200
> Martin Jansa wrote:
>
> > inode mismatch:
> > '/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/
> systemd/1_234-r0/recipe-sysroot/etc/group'
> > ino 29361846 in db,
.. and if anyone notices, there's a kernel part to this CVE as well.
I've applied to fix to all the active linux-yocto kernels, and the change
will be part
of my consolidated pull request that comes out later today.
Cheers,
Bruce
On Thu, Sep 14, 2017 at 8:27 AM, Ross Burton
On 13 September 2017 at 11:24, Khem Raj wrote:
> On Tue, Sep 12, 2017 at 4:42 PM, Trevor Woerner wrote:
>> On Tue, Sep 12, 2017 at 4:21 PM, Khem Raj wrote:
>>> On Mon, Sep 11, 2017 at 1:58 AM, Burton, Ross
All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an
information disclosure vulnerability which allows remote attackers to obtain
sensitive information from the bluetoothd process memory. This vulnerability
lies in the processing of SDP search attribute requests.
On Thu, Sep 14, 2017 at 7:26 AM, André Draszik wrote:
> On Wed, 2017-09-13 at 09:30 -0300, Otavio Salvador wrote:
>> On Wed, Sep 13, 2017 at 5:15 AM, André Draszik wrote:
>> > On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
>>
>> ...
>> > AFAICS,
On 09/12/2017 08:31 PM, Mark Hatle wrote:
Also its interesting that nobody else noticed this: multilib images that
installed fonts were segfaulting in rootfs...
If the segfault is causing the postinst to exit w/ an error (non-0) then it's
likely re-running on the target itself (and thus
On 13 September 2017 at 23:49, Mark Hatle wrote:
> On 9/13/17 5:40 PM, Mark Hatle wrote:
> > If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by
> the
> > packages.bbclass. This made it difficult for a recipe or layer to
> 'append'
> > to the
On Wed, 2017-09-13 at 09:30 -0300, Otavio Salvador wrote:
> On Wed, Sep 13, 2017 at 5:15 AM, André Draszik wrote:
> > On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
>
> ...
> > AFAICS, zImage is specific to x86 and arm, all other arches, including
> > MIPS
> > have no
On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
> The are use cases where the Device Tree appended to the kernel is
> convinient, so we generate the bundle concatenating the kernel (and
> potentionally the initramfs) and the Device Tree binaries.
>
> To enable it, set
From: Ooi Cinly
To improve binary reproducibility, only the
relevent part of the Makefile in bzip2-ptest
package that run-ptest needs are copied to
the destination directory.
bzip2-ptest requires Makefile. The original
Makefile contains references to build host.
By copying
Fixed:
1) in pkg_postinst task set wanted file permissions:
---> chmod -R 521 "$D/opt/my_folder"
2) generate the rootfs image
Results:
my_folder hasn't correct permissions on rootfs ext4 image -> permissions are
changed to 721
But it should be 521.
[YOCTO #11652]
Signed-off-by: Robert Yang
Fixed:
WARNING: systemd-machine-units-1.0-r19 do_populate_lic: ${COREBASE}/LICENSE is
not a valid license file, please use '${COMMON_LICENSE_DIR}/MIT' for a MIT
License file in LIC_FILES_CHKSUM. This will become an error in the future
Signed-off-by: Robert Yang
---
The following changes since commit 7b501954198c2a810b2c03096accb27339cfd1f9:
runqemu: let qemuparams override previous settings (2017-09-14 02:11:35 -0700)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/2fixes
Signed-off-by: Huang Qiyu
---
meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb
b/meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb
index
Signed-off-by: Huang Qiyu
---
meta/recipes-extended/minicom/minicom_2.7.1.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/minicom/minicom_2.7.1.bb
b/meta/recipes-extended/minicom/minicom_2.7.1.bb
index 92cf5f9..1a31a87 100644
---
Signed-off-by: Huang Qiyu
---
meta/recipes-kernel/sysprof/sysprof_3.24.1.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-kernel/sysprof/sysprof_3.24.1.bb
b/meta/recipes-kernel/sysprof/sysprof_3.24.1.bb
index 168f2fd..79a27be 100644
---
Signed-off-by: Huang Qiyu
---
meta/recipes-devtools/perl/libxml-perl_0.08.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/perl/libxml-perl_0.08.bb
b/meta/recipes-devtools/perl/libxml-perl_0.08.bb
index 2c01976..0478427 100644
---
Signed-off-by: Huang Qiyu
---
meta/recipes-extended/perl/libxml-namespacesupport-perl_1.12.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/perl/libxml-namespacesupport-perl_1.12.bb
Signed-off-by: Huang Qiyu
---
meta/recipes-gnome/libnotify/libnotify_0.7.7.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-gnome/libnotify/libnotify_0.7.7.bb
b/meta/recipes-gnome/libnotify/libnotify_0.7.7.bb
index 2ab2f1f..6c299bc 100644
---
On 14 September 2017 at 08:59, wrote:
> Is there any other Window manager instead of matchbox which supports QVGA
> theme in Yocto 1.8?
>
For a screen that small matchbox is the only real option for behaviour, you
just need to customise the theme.
Ross
--
Hi ,
Thank You for the valuable information.
Is there any other Window manager instead of matchbox which supports
QVGA theme in Yocto 1.8?
Thanks & Regards,
Anjali
On 13.09.2017 10:33, Burton, Ross wrote:
> The default theme, fonts, padding etc all assume the screen has a higher
53 matches
Mail list logo