Before the "Improve handling of SRCPV" change, gitsm SRC_URI entries
were merely missing a dependency on git for do_fetch. But after that
change, the special handling for "needsrcrev" was not applied, leading
to a fetcher error (older bitbake) or even a parse error (recent
bitbake).
Signed-off-by:
Improve the packaging of the libraries built by this recipe. These
are created using special code in the recipe and the debug (-dbg)
packages were not being created. Adding these packages allow the
libraries in question to be debugged using GDB.
Signed-off-by: Gary Thomas
---
meta/recipes-mult
From: Armin Kuster
this is related to [Yocto # 9008]
8.38:
The following security fixes are included:
CVE-2015-3210 pcre: heap buffer overflow in pcre_compile2() compile_regex()
CVE-2015-3217 pcre: stack overflow in match()
CVE-2015-5073 CVE-2015-8388 pcre: Buffer overflow caused by certain pat
this is to meet our obligation for Yocto compatibility.
Armin Kuster (1):
libpcre: Security fixes and package update.
meta/recipes-support/libpcre/{libpcre_8.36.bb => libpcre_8.38.bb} | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
rename meta/recipes-support/libpcre/{libpcre_8.3
Thanks to Alexander Kanavin's patch I can now start an opencv build on
master without the x11 distro feature. However the build fails in the
python module as NPY_SIZEOF_OFF_T is not defined.
[ 89%] Building CXX object
modules/python/CMakeFiles/opencv_python.dir/src2/cv2.cpp.o
...
In file included
From: Armin Kuster
CVE-2016-2090 Heap buffer overflow in fgetwln function of libbsd
affects libbsd <= 0.8.1
Signed-off-by: Armin Kuster
---
.../libbsd/files/CVE-2016-2090.patch | 50 ++
meta/recipes-support/libbsd/libbsd_0.7.0.bb| 4 +-
2 files chang
We pass --disable-cairo-tests but if cairo is in the sysroot it is detected and
used, which causes problems in mass builds as cairo could be removed whilst
libdrm is being built.
Signed-off-by: Ross Burton
---
meta/recipes-graphics/drm/libdrm/detect.patch | 59 +++
meta/r
Upgrades to stable LINUX_VERSION 4.1.17
Signed-off-by: Alejandro Hernandez
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
b/meta-yocto-bsp/re
Upgrades to stable LINUX_VERSION 4.4.1
Signed-off-by: Alejandro Hernandez
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
b/meta-yocto-bsp/rec
On 02/11/16 14:20, Martin Jansa wrote:
Did you add ld-is-gold to DISTRO_FEATURES?
Yes, it's the only way I know of to build an image with gold instead of
bfd. And no other thing that gets built has any problems finding and
running the linker.
I'll post my chromium recipe shortly, although i
The inclusion of STAGING_DIR/BASE_WORKDIR in PATH is contaminating
the environment, i.e. when try to sanity check perl (check_perl_modules)
it takes perl from STAGING_DIR causing eSDK install to fail.
Signed-off-by: Aníbal Limón
---
meta/classes/testsdk.bbclass | 11 ++-
1 file changed,
Since python expansion of bb data variables is disable in order to
provide a standard interface usage for expand variables this variables
aren't expanded now so change to call d.expand('${VAR}').
This API expansion change was causing to install perl in nativesdk.
Signed-off-by: Aníbal Limón
---
Since python expansion of bb data variables is disable in order to
provide a standard interface usage for expand variables this variables
aren't expanded now so change to call d.expand('${VAR}').
This API expansion change was causing to install perl in nativesdk.
Signed-off-by: Aníbal Limón
---
The inclusion of STAGING_DIR/BASE_WORKDIR in PATH is contaminating
the environment, i.e. when try to sanity check perl (check_perl_modules)
it takes perl from STAGING_DIR causing eSDK install to fail.
Signed-off-by: Aníbal Limón
---
meta/classes/testsdk.bbclass | 11 ++-
1 file changed,
On Thu, Feb 11, 2016 at 8:29 AM, Nathan Sowatskey wrote:
> Hi
>
> I am using the Jethro branch of oe-core, and my build is failing with the
> error below.
>
> This has started happening in the last few days. This build worked as
> expected last week.
>
> Has anyone else seen anything like this p
On Thu, Feb 11, 2016 at 12:25:12PM -0500, Trevor Woerner wrote:
> On 02/09/16 23:37, Khem Raj wrote:
> > IIRC gold has its own notions to enable gold
> > so you need to enable that
> >
> >> On Feb 9, 2016, at 8:18 PM, Trevor Woerner wrote:
> >>
> >> I've tried every combination I can think of and
this update includes:
CVE-2015-7096
Versions affected: WebKitGTK+ before 2.10.5.
CVE-2015-7098
Versions affected: WebKitGTK+ before 2.10.5.
http://webkitgtk.org/security.html
On 02/10/2016 04:42 AM, Alexander Kanavin wrote:
> Signed-off-by: Alexander Kanavin
> ---
> meta/recipes-sa
This update includes CVE-2016-2213
Fixes out of array read
http://git.videolan.org/?p=ffmpeg.git;a=commit;h=0aada30510d809bccfd539a90ea37b61188f2cb4
On 02/10/2016 04:42 AM, Alexander Kanavin wrote:
> Add libxv dependency only when libavdevice is enabled (as nothing else needs
> it).
>
> Signe
> On Feb 11, 2016, at 9:25 AM, Trevor Woerner wrote:
>
> On 02/09/16 23:37, Khem Raj wrote:
>> IIRC gold has its own notions to enable gold
>> so you need to enable that
>>
>>> On Feb 9, 2016, at 8:18 PM, Trevor Woerner wrote:
>>>
>>> I've tried every combination I can think of and no matter
On 02/09/16 23:37, Khem Raj wrote:
IIRC gold has its own notions to enable gold
so you need to enable that
On Feb 9, 2016, at 8:18 PM, Trevor Woerner wrote:
I've tried every combination I can think of and no matter what I try, if gold
is the linker the chromium build always errors out with:
Hi
I am using the Jethro branch of oe-core, and my build is failing with the error
below.
This has started happening in the last few days. This build worked as expected
last week.
Has anyone else seen anything like this please?
I have removed the contents of the tmp, downloads and caches a f
On Tue, 2016-02-09 at 09:41 -0600, Mark Hatle wrote:
> I'm sending this as an RFC. I know the patch works, but I think it
> highlights
> a potentially larger issue in the system.
>
> If we're processing data using shell pipes, the return code of a
> failed
> process may end up being lost -- avoid
On Thu, Feb 11, 2016 at 05:18:56PM +0200, Ioan-Adrian Ratiu wrote:
> From: Richard Tollerton
>
> Define tunnings to enable 32 register VFPv3 for cortexa9 processor cores
Can you execute the test from:
http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune2-test
just to verify th
> On Feb 11, 2016, at 2:12 AM, Richard Purdie
> wrote:
>
> I tested this in master-next on the AB, it fails for
> "MACHINE=edgerouter bitbake ltp":
>
> | 1455184833.52: ^
> | 1455184833.52: In file included from
> /media/build1/poky/build/tmp/sysroo
On Tue, Feb 9, 2016 at 8:41 AM Mark Hatle wrote:
> I'm sending this as an RFC. I know the patch works, but I think it
> highlights
> a potentially larger issue in the system.
>
> If we're processing data using shell pipes, the return code of a failed
> process may end up being lost -- avoiding t
From: Richard Tollerton
Define tunnings to enable 32 register VFPv3 for cortexa9 processor cores
More details:
http://www.arm.com/products/processors/technologies/vector-floating-point.php
Signed-off-by: Richard Tollerton
Signed-off-by: Ioan-Adrian Ratiu
---
meta/conf/machine/include/tune-c
== Tested changes (not included in master yet) - bitbake ==
93918f0 world-image: add extra target
== Tested changes (not included in master yet) - openembedded-core ==
2f26ee9 ptest-runner: Explicitly set EXTRA_OEMAKE as required
d5d8d0f unzip: Explicitly set EXTRA_OEMAKE as required
bb062fc syskl
On Thu, 2016-02-11 at 14:59 +, Mike Crowe wrote:
> On Thursday 11 February 2016 at 12:12:41 +, Richard Purdie wrote:
> > This recipe currently relies on EXTRA_OEMAKE having been set to
> > "-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
> > this
> > explicit so that the
Integrating the 4.4.1 stable korg update.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 ++--
3 files changed,
Updating the 4.1 branches with backported mainline support for the
galileo.
a5327464dad9 iio: light: add support for ROHM
BH1710/BH1715/BH1721/BH1750/BH1751 ambient light sensors
7a868ce12675 pwm-pca9685: enable ACPI device found on Galileo Gen2
9f169f0f6493 at24: enable ACPI device foun
Hi all,
Here are the pending updates to the 4.1 and 4.4 kerne to integrate -stable
updates
and to backport the mainline galileo support patches.
I've built and booted these on qemu* and Saul has provided the galileo support.
Cheers,
Bruce
The following changes since commit 738a9b7cc322f3dca94
Updating to the -stable korg release with the following changes:
2d5f6b041335 Linux 4.1.17
d17367a77457 recordmcount: Fix endianness handling bug for nop_mcount
1f6d936d33f4 arm64: restore bogomips information in /proc/cpuinfo
705164dbe08f mn10300: Select CONFIG_HAVE_UID16 to fix build
On Thursday 11 February 2016 at 12:12:41 +, Richard Purdie wrote:
> This recipe currently relies on EXTRA_OEMAKE having been set to
> "-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
> explicit so that the default in bitbake.conf can be change
Minor typo at the end of t
Hi,
I'm proposing that we drop Debian 7 from the supported distributions list
in master, so that the 2.1 release supports Debian 8. Debian 7 was
released in 2013, Debian 8 superceded it in April 2015 so will have been
out for a year when 2.1 is released, which also means that is when Debian 7
sto
On Thu, 2016-02-11 at 12:12 +, Richard Purdie wrote:
> This recipe currently relies on EXTRA_OEMAKE having been set to
> "-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make
> this
> explicit so that the default in bitbake.conf can be change
>
> Signed-off-by: Richard Purdie
S
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be change
Signed-off-by: Richard Purdie
diff --git a/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
b
This recipe currently relies on EXTRA_OEMAKE having been set to
"-e MAKEFLAGS=" in bitbake.conf to operate. It is necessary to make this
explicit so that the default in bitbake.conf can be change
Signed-off-by: Richard Purdie
diff --git a/meta/recipes-support/ptest-runner2/ptest-runner2_0.1.bb
Recent bitbake changes mean the whitespace formatting around the way functions
are
defined, changed which broke the rather ugly construct this test uses to append
to
a python function. This really needs to be rewritten and improved but fix the
whitespace so at least the tests work again and other
I tested this in master-next on the AB, it fails for
"MACHINE=edgerouter bitbake ltp":
| 1455184833.52: ^
| 1455184833.52: In file included from
/media/build1/poky/build/tmp/sysroots/edgerouter/usr/include/asm/types.h:22:0,
| 1455184833.52:
On 11/02/16, Ed Bartosh wrote:
> Hi Oliver,
>
> This looks like a bug in wic code to me. I remember something similar
> was fixed recently. Please, create a bug in for me in bugzilla.
Hello,
filed a Bug for this Issue
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9094
Best regards,
Oliver
Hi Oliver,
This looks like a bug in wic code to me. I remember something similar
was fixed recently. Please, create a bug in for me in bugzilla.
On Wed, Feb 10, 2016 at 05:14:58PM +0100, Oliver Graute wrote:
> Hello list,
>
> I observe a problem with the create_image.wic script after second exec
41 matches
Mail list logo
