On 1/8/19 4:57 AM, Ovidiu Panait wrote:
> In Artifex Ghostscript through 9.25, the setpattern operator did not properly
> validate certain types. A specially crafted PostScript document could exploit
> this to crash Ghostscript or, possibly, execute arbitrary code in the context
> of the Ghostscr
On Sat, Jan 12, 2019 at 11:18 AM Richard Purdie
wrote:
>
> On Sat, 2019-01-12 at 10:31 -0800, Khem Raj wrote:
> > On Sat, Jan 12, 2019 at 8:22 AM Richard Purdie
> > wrote:
> > > On Sat, 2019-01-12 at 17:56 +0200, Serhey Popovych wrote:
> > > > Richard Purdie wrote:
> > > > > On Sat, 2019-01-12 at
On Sat, Jan 12, 2019 at 10:45 AM Bruce Ashfield
wrote:
>
> On 2019-01-12 1:34 p.m., Khem Raj wrote:
> > On Sat, Jan 12, 2019 at 10:14 AM Bruce Ashfield
> > wrote:
> >>
> >> Incorporating the BSP definitions for two new qemu targets.
> >>
> >> Signed-off-by: Alistair Francis
> >> Signed-off-by: J
Richard Purdie wrote:
> On Sat, 2019-01-12 at 10:31 -0800, Khem Raj wrote:
>> On Sat, Jan 12, 2019 at 8:22 AM Richard Purdie
>> wrote:
>>> On Sat, 2019-01-12 at 17:56 +0200, Serhey Popovych wrote:
Richard Purdie wrote:
> On Sat, 2019-01-12 at 12:11 +0200, Serhey Popovych wrote:
>> In
On Wed, Jan 9, 2019 at 9:31 PM Jacob Kroon wrote:
>
> Introduce 'sha256' in BUILDHISTORY_FEATURES and enable it by default
> when doing reproducible builds.
>
> When enabled this will additionally create:
>
> files-in-package-sha256.txt
> files-in-image-sha256.txt
> files-in-sdk-sha256.txt
>
On Sat, 2019-01-12 at 10:31 -0800, Khem Raj wrote:
> On Sat, Jan 12, 2019 at 8:22 AM Richard Purdie
> wrote:
> > On Sat, 2019-01-12 at 17:56 +0200, Serhey Popovych wrote:
> > > Richard Purdie wrote:
> > > > On Sat, 2019-01-12 at 12:11 +0200, Serhey Popovych wrote:
> > > > > In Ubuntu 16.04 LTS use
On 2019-01-12 1:34 p.m., Khem Raj wrote:
On Sat, Jan 12, 2019 at 10:14 AM Bruce Ashfield
wrote:
Incorporating the BSP definitions for two new qemu targets.
Signed-off-by: Alistair Francis
Signed-off-by: Jon Mason
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_
On Sat, Jan 12, 2019 at 10:14 AM Bruce Ashfield
wrote:
>
> Incorporating the BSP definitions for two new qemu targets.
>
> Signed-off-by: Alistair Francis
> Signed-off-by: Jon Mason
> Signed-off-by: Bruce Ashfield
> ---
> meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb | 4 ++--
> meta/rec
On Sat, Jan 12, 2019 at 8:22 AM Richard Purdie
wrote:
>
> On Sat, 2019-01-12 at 17:56 +0200, Serhey Popovych wrote:
> > Richard Purdie wrote:
> > > On Sat, 2019-01-12 at 12:11 +0200, Serhey Popovych wrote:
> > > > In Ubuntu 16.04 LTS userspace is build for PowerPC 32-bit while
> > > > kernel
> > >
On Sat, Jan 12, 2019 at 8:53 AM Serhey Popovych
wrote:
>
> Khem Raj wrote:
> > On Sat, Jan 12, 2019 at 1:23 AM Serhey Popovych
> > wrote:
> >>
> >> Building musl for powerpc64 enforces elfv2 ABI since commit 68c964185519
> >> ("arch-powerpc64.inc: Use elfv2 ABI when building with musl") that is
>
This is provided by runit
Signed-off-by: Khem Raj
---
meta/lib/oeqa/runtime/cases/oe_syslog.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/runtime/cases/oe_syslog.py
b/meta/lib/oeqa/runtime/cases/oe_syslog.py
index a92a1f2bcb..ad023fb363 100644
--- a/meta/l
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 23cb355b5ce7..ae8c34300836 100644
--- a/meta/recipe
Incorporating the BSP definitions for two new qemu targets.
Signed-off-by: Alistair Francis
Signed-off-by: Jon Mason
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb | 6 +++---
meta/recipes-kern
Hi all,
Here's the next batch of kernel updates. Nothing particular of note, but we
do gain new BSP descriptions for qemuarma15 and qemuriscv64. Although the
full machine definitions are not in oe-core yet, this sets the table for them
to be made widely available.
Other than that, I bumped the -d
Integrating the korg -stable updates that comprise the following commits:
f630d3cc771e Linux 4.19.14
a4a929aa46b4 MIPS: Only include mmzone.h when CONFIG_NEED_MULTIPLE_NODES=y
feb0be15ee8b spi: bcm2835: Unbreak the build of esoteric configs
62977aad0a52 tpm: tpm_i2c_nuvoton: use correc
Khem Raj wrote:
> On Sat, Jan 12, 2019 at 1:23 AM Serhey Popovych
> wrote:
>>
>> Building musl for powerpc64 enforces elfv2 ABI since commit 68c964185519
>> ("arch-powerpc64.inc: Use elfv2 ABI when building with musl") that is
>> not compatible with valgrind.
>>
>> Signed-off-by: Serhey Popovych
Richard Purdie wrote:
> On Sat, 2019-01-12 at 17:56 +0200, Serhey Popovych wrote:
>> Richard Purdie wrote:
>>> On Sat, 2019-01-12 at 12:11 +0200, Serhey Popovych wrote:
In Ubuntu 16.04 LTS userspace is build for PowerPC 32-bit while
kernel
selected by the installer depending on Power
On Sat, 2019-01-12 at 17:56 +0200, Serhey Popovych wrote:
> Richard Purdie wrote:
> > On Sat, 2019-01-12 at 12:11 +0200, Serhey Popovych wrote:
> > > In Ubuntu 16.04 LTS userspace is build for PowerPC 32-bit while
> > > kernel
> > > selected by the installer depending on PowerPC machine type:
> > >
Hi Paul,
On Fri, 2019-01-11 at 16:44 +, Paul Barker wrote:
> With the recent move to using sha256 checksums in sstate, the lengths
> of some file names can now exceed the 255 char limit seen in most
> Linux filesystems. When this occurs, bitbake crashes as it is unable
> to create the sstate a
Update the code to match the recent switch to sha256 hashes
Signed-off-by: Richard Purdie
---
meta/lib/oe/sstatesig.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index 059e165c7ab..e0eb87e29f0 100644
--- a/meta/lib/oe/s
Richard Purdie wrote:
> On Sat, 2019-01-12 at 12:11 +0200, Serhey Popovych wrote:
>> In Ubuntu 16.04 LTS userspace is build for PowerPC 32-bit while
>> kernel
>> selected by the installer depending on PowerPC machine type:
>>
>> * 32-bit for PowerMac G4 (ppc7400) and below
>> * 64-bit for Power
On Sat, 2019-01-12 at 12:11 +0200, Serhey Popovych wrote:
> In Ubuntu 16.04 LTS userspace is build for PowerPC 32-bit while
> kernel
> selected by the installer depending on PowerPC machine type:
>
> * 32-bit for PowerMac G4 (ppc7400) and below
> * 64-bit for PowerMac G5 and above
>
> Thus un
i am getting http://errors.yoctoproject.org/Errors/Details/216093/
On Tue, Jan 8, 2019 at 5:52 PM Hong Liu wrote:
>
> Upgrade python3-pbr from 4.2.0 to 5.1.1.
>
> Signed-off-by: Hong Liu
> ---
> meta/recipes-devtools/python/python-pbr.inc | 4 ++--
> .../python/{python3-pbr_4.
On Sat, Jan 12, 2019 at 1:23 AM Serhey Popovych
wrote:
>
> With custom BSP and build with musl we still affected by undefined
> reference to stack-protector specific functions.
>
> Use arch overrides instead of machine to ensure fix applied to entire
> architecture instead of custom machine like q
On Sat, Jan 12, 2019 at 1:23 AM Serhey Popovych
wrote:
>
> Building musl for powerpc64 enforces elfv2 ABI since commit 68c964185519
> ("arch-powerpc64.inc: Use elfv2 ABI when building with musl") that is
> not compatible with valgrind.
>
> Signed-off-by: Serhey Popovych
> ---
> meta/recipes-devt
On Sat, Jan 12, 2019 at 2:12 AM Serhey Popovych
wrote:
>
> We need only libbfd, libiberty and libopcodes from binutils native.
> To get them we build entire binutils with --enable-targets=all to
> include all possible output targets support and then remove all but
> these three libs.
>
> This has
Serhey Popovych wrote:
Does anyone have time to look at this? Reviews wanted!
Thanks,
Serhey
> Both changes target ldd helper handling in packages:
>
> 1) For musl this fixes do_install error where ldd provided in both
> main target and multilib packages.
>
> 2) For glibc make behavio
In Ubuntu 16.04 LTS userspace is build for PowerPC 32-bit while kernel
selected by the installer depending on PowerPC machine type:
* 32-bit for PowerMac G4 (ppc7400) and below
* 64-bit for PowerMac G5 and above
Thus uname(2) returns ppc64 for 64-bit kernels and 32-bit userspace
making build
We need only libbfd, libiberty and libopcodes from binutils native.
To get them we build entire binutils with --enable-targets=all to
include all possible output targets support and then remove all but
these three libs.
This has two side effects:
1) it wastes build time
2) may cause errors ca
In some specific environments on PowerPC native builds failing due to:
a) libgpg-error requires TARGET_ARCH tuple mapping to supported tuple
b) binutils fails to build with --enable-targets=all due to small bss
and data relocation failures.
To fix a) is trivial: we need to add tuple mapp
With custom BSP and build with musl we still affected by undefined
reference to stack-protector specific functions.
Use arch overrides instead of machine to ensure fix applied to entire
architecture instead of custom machine like qemux86 and qemuppc.
Signed-off-by: Serhey Popovych
---
meta/reci
Since it does not support float128 type.
Signed-off-by: Serhey Popovych
---
meta/recipes-support/mpfr/mpfr_4.0.1.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-support/mpfr/mpfr_4.0.1.bb
b/meta/recipes-support/mpfr/mpfr_4.0.1.bb
index 2eee76a..ccf7fdc 100644
--- a/meta/re
Use commit 4f07ffa8f5ab ("Use #if instead of #ifdef for ENABLE_GSHADOW")
from upstream to check ENABLE_GSHADOW correctly that is defined as 0
in case of musl.
While there replace specific patch with one from upstream that does
exactly the same commit 66a5b5ce9b99 ("basic/user-util: properly protec
Building musl for powerpc64 enforces elfv2 ABI since commit 68c964185519
("arch-powerpc64.inc: Use elfv2 ABI when building with musl") that is
not compatible with valgrind.
Signed-off-by: Serhey Popovych
---
meta/recipes-devtools/valgrind/valgrind_3.14.0.bb | 3 +++
1 file changed, 3 insertions(
This is followup set of improvements for recently merged musl on PowerPC
fixes. It fixes more issues discovered later after first series merged.
See individual commit message for details on each change presented.
Build tested following images with musl as libc:
core-image-sato-dev
core-image
SDL2 dumps all cflags to the sdl2.pc, which might then contain paths
to the recipe sysroot include dirs.
Signed-off-by: Samuli Piippo
---
meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
b/meta/
36 matches
Mail list logo
