Re: [OE-core] [RFC][PATCH v4] mesa: Convert recipe to use meson build system

[Otavio Salvador]

On Mon, Feb 25, 2019 at 4:05 PM Burton, Ross  wrote:
>
> So far:
>
> rburton: according to this commit it's intentional:
> cc15460e182148292be877bec5a8a61cec57377d
> although I'm not sure that patch was correct now, it looks
> like autotools has generated a 1.1.0 since 2014
>
> On Mon, 25 Feb 2019 at 18:54, Burton, Ross  wrote:
> >
> > packages/corei7-64-poky-linux/mesa/libgles1-mesa: FILELIST: removed
> > "/usr/lib/libGLESv1_CM.so.1.1.0", added
> > "/usr/lib/libGLESv1_CM.so.1.0.0"
> >
> > Is that intentional?  Looks like a version mistake in the meson.build.

I intend to wait for 19.0.1 to upgrade to meson, however, we will
again upgrade and then do the meson change so we can track regressions
or behavior changes.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854  Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [RFC][PATCH v4] mesa: Convert recipe to use meson build system

[Burton, Ross]

I'm also not convinced this was right and have submitted
https://lists.freedesktop.org/archives/mesa-dev/2019-February/215791.html.
When that is reviewed we'll know whether this change is fine, or we
should pick a the patch.

Ross

On Mon, 25 Feb 2019 at 19:04, Burton, Ross  wrote:
>
> So far:
>
> rburton: according to this commit it's intentional:
> cc15460e182148292be877bec5a8a61cec57377d
> although I'm not sure that patch was correct now, it looks
> like autotools has generated a 1.1.0 since 2014
>
> On Mon, 25 Feb 2019 at 18:54, Burton, Ross  wrote:
> >
> > packages/corei7-64-poky-linux/mesa/libgles1-mesa: FILELIST: removed
> > "/usr/lib/libGLESv1_CM.so.1.1.0", added
> > "/usr/lib/libGLESv1_CM.so.1.0.0"
> >
> > Is that intentional?  Looks like a version mistake in the meson.build.
> >
> > Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] default-distrovars: Drop DISTRO_FEATURES_LIBC

[Andre McCurdy]

On Mon, Feb 25, 2019 at 11:00 AM Khem Raj  wrote:
>
> After eglibc was merged into glibc, Kconfig support was also dropped so
> these libc features therefore are not effective anymore and can be
> removed
>
> Signed-off-by: Khem Raj 
> ---
>  meta/conf/distro/include/default-distrovars.inc | 10 +-
>  meta/conf/local.conf.sample.extended| 16 ++--
>  2 files changed, 3 insertions(+), 23 deletions(-)
>
> diff --git a/meta/conf/distro/include/default-distrovars.inc 
> b/meta/conf/distro/include/default-distrovars.inc
> index 76edff6480..35da7f10e1 100644
> --- a/meta/conf/distro/include/default-distrovars.inc
> +++ b/meta/conf/distro/include/default-distrovars.inc
> @@ -11,15 +11,7 @@ LOCALE_UTF8_IS_DEFAULT ?= "1"
>  LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
>
>  DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 irda largefile 
> pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
> -DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace libc-big-macros 
> libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \

There are a lot of recipes which check the ipv6 distro feature. Those
recipe should probably be updated before this is merged.

> -   libc-crypt-ufc libc-db-aliases 
> libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
> -   libc-getlogin libc-idn libc-inet-anl 
> libc-libm libc-locales libc-locale-code \
> -   libc-memusage libc-nsswitch libc-rcmd 
> libc-rtld-debug libc-spawn libc-streams \
> -   libc-utmp libc-utmpx libc-wordexp 
> libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
> -   libc-posix-wchar-io"
> -DISTRO_FEATURES_LIBC ?= "${DISTRO_FEATURES_LIBC_DEFAULT}"
> -DISTRO_FEATURES_LIBC_class-nativesdk = "${DISTRO_FEATURES_LIBC_DEFAULT}"
> -DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
> +DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
>
>  IMAGE_FEATURES ?= ""
>
> diff --git a/meta/conf/local.conf.sample.extended 
> b/meta/conf/local.conf.sample.extended
> index 010bf6ca6f..91e321047f 100644
> --- a/meta/conf/local.conf.sample.extended
> +++ b/meta/conf/local.conf.sample.extended
> @@ -24,22 +24,10 @@
>  # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" 
> would
>  # be appropriate for example.
>
> -
> -# glibc configurability is used to reduce minimal image's size.
> -# the all supported glibc options are listed in DISTRO_FEATURES_LIBC
> -# and disabled by default. Uncomment and copy the DISTRO_FEATURES_LIBC
> -# and DISTRO_FEATURES definitions to local.conf to enable the options.
> -#DISTRO_FEATURES_LIBC = "ipv6 libc-backtrace libc-big-macros libc-bsd 
> libc-cxx-tests libc-catgets libc-charsets libc-crypt \
> -#   libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt 
> libc-fmtmsg libc-fstab libc-ftraverse \
> -#   libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm 
> libc-locales libc-locale-code \
> -#   libc-memusage libc-nsswitch libc-rcmd libc-rtld-debug 
> libc-spawn libc-streams \
> -#   libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar 
> libc-posix-regexp libc-posix-regexp-glibc \
> -#   libc-posix-wchar-io"
> -
> -#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> nfs zeroconf pci ${DISTRO_FEATURES_LIBC}"
> +#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> nfs zeroconf pci"
>
>  # If you want to get an image based on directfb without x11, Please copy 
> this variable to build/conf/local.conf
> -#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget 
> usbhost wifi xattr nfs zeroconf pci 3g directfb ${DISTRO_FEATURES_LIBC}"
> +#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget 
> usbhost wifi xattr nfs zeroconf pci 3g directfb"
>
>  # ENABLE_BINARY_LOCALE_GENERATION controls the generation of binary locale
>  # packages at build time using qemu-native. Disabling it (by setting it to 0)
> --
> 2.20.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Xorg issue on qemuarma15

[Jon Mason]

I'm having a problem trying to get Xorg up and running on the
qemuarma15 (from the series
http://lists.openembedded.org/pipermail/openembedded-core/2019-January/278190.html).
I've applied a patch on top of these to get framebuffer added by
default to the kernel config and changes in the default recipe.

I can visually verify that the frame buffer is working by the "tuxes"
that appear during the kernel boot, as well as the presence of
/dev/fb0
However, when X should take over, it logs an error to the screen:

(EE) AddScreen/ScreenInit failed for driver 0



My knowledge of Xorg is very limited.  So, I'm hoping someone can
provide some insight as to what is going on.  The log file output is
below:


# cat /var/log/Xorg.0.log
[12.742]
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[12.747] Build Operating System: Linux 4.19.8-200.fc28.x86_64 x86_64
[12.748] Current Operating System: Linux qemuarm
4.19.14-yocto-standard #1 SMP PREEMPT Fri Jan 25 20:16:06 UTC 2019
armv7l
[12.748] Kernel command line: root=/dev/vda rw highres=off
mem=512M ip=192.168.7.2::192.168.7.1:255.255.255.0 console=ttyAMA0
console=tty1
[12.749] Build Date: 25 January 2019  08:56:06PM
[12.749]
[12.749] Current version of pixman: 0.34.0
[12.749] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[12.749] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[12.751] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 25
20:54:20 2019
[12.766] (==) Using config file: "/etc/X11/xorg.conf"
[12.771] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[12.785] (==) ServerLayout "Default Layout"
[12.785] (**) |-->Screen "Default Screen" (0)
[12.785] (**) |   |-->Monitor "Generic Monitor"
[12.789] (**) |   |-->Device "Graphics Controller"
[12.794] (==) Automatically adding devices
[12.795] (==) Automatically enabling devices
[12.796] (==) Automatically adding GPU devices
[12.799] (==) Max clients allowed: 256, resource mask: 0x1f
[12.821] (WW) The directory "/usr/share/fonts/X11/misc/" does not exist.
[12.821] Entry deleted from font path.
[12.821] (WW) The directory "/usr/share/fonts/X11/TTF/" does not exist.
[12.821] Entry deleted from font path.
[12.821] (WW) The directory "/usr/share/fonts/X11/OTF/" does not exist.
[12.821] Entry deleted from font path.
[12.821] (WW) The directory "/usr/share/fonts/X11/Type1/" does not exist.
[12.821] Entry deleted from font path.
[12.821] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[12.821] Entry deleted from font path.
[12.821] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[12.821] Entry deleted from font path.
[12.821] (==) FontPath set to:

[12.821] (==) ModulePath set to "/usr/lib/xorg/modules"
[12.821] (II) The server relies on udev to provide the list of
input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[12.822] (II) Loader magic: 0x590d78
[12.822] (II) Module ABI versions:
[12.822] X.Org ANSI C Emulation: 0.4
[12.822] X.Org Video Driver: 24.0
[12.822] X.Org XInput driver : 24.1
[12.822] X.Org Server Extension : 10.0
[12.843] (II) xfree86: Adding drm device (/dev/dri/card1)
[12.846] (II) xfree86: Adding drm device (/dev/dri/card0)
[12.931] (--) PCI: (0@0:1:0) 1af4:1050:1af4:1100 rev 1, Mem @
0x1000/4096, 0x/16384
[12.931] (II) no primary bus or device found
[12.931] falling back to
/sys/devices/platform/401000.pcie/pci:00/:00:01.0/virtio2/drm/card1
[12.932] (II) LoadModule: "glx"
[12.939] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[12.995] (II) Module glx: vendor="X.Org Foundation"
[12.995] compiled for 1.20.3, module version = 1.0.0
[12.995] ABI class: X.Org Server Extension, version 10.0
[12.996] (II) LoadModule: "fbdev"
[12.998] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[13.000] (II) Module fbdev: vendor="X.Org Foundation"
[13.000] compiled for 1.20.3, module version = 0.5.0
[13.000] Module class: X.Org Video Driver
[13.000] ABI class: X.Org Video Driver, version 24.0
[13.001] (II) FBDEV: driver for framebuffer: fbdev
[13.001] (--) using VT number 2

[13.050] (WW) Falling back to old probe method for fbdev
[13.051] (II) Loading sub module "fbdevhw"
[13.051] (II) LoadModule: "fbdevhw"
[13.052] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[13.054] (II) Module fbdevhw: vendor="X.Org Foundation"
[13.054] compiled for 1.20.3, module version = 0.0.2
[13.059] ABI class: X.Org Video Driver, version 24.0
[13.067] (II) 

Re: [OE-core] [PATCH v2 1/1] ltp: Update to 20190115

[Petr Vorel]

Hi Richard, Khem,

> > security_flags.inc:SECURITY_STRINGFORMAT ?= "-Wformat -Wformat-security 
> > -Werror=format-security"
> > security_flags.inc:SECURITY_CFLAGS ?= "${SECURITY_STACK_PROTECTOR} 
> > ${SECURITY_PIE_CFLAGS} ${lcl_maybe_fortify} ${SECURITY_STRINGFORMAT}"

> > so the reproducer should be to add "-Wformat -Wformat-security
> > -Werror=format-security" to CFLAGS when building ltp.


> I think this must be new, we are carrying patches to fix similar
> issues in other parts of ltp. Probably something to consider for
> upstreaming
> e.g.
> https://git.openembedded.org/openembedded-core/tree/meta/recipes-extended/ltp/ltp/0036-testcases-network-nfsv4-acl-acl1.c-Security-fix-on-s.patch

I was testing it, but this one was ok. Found problems with setregid01.c,
to realize that it was already posted to LTP mailing list, so pushed it.

Kind regards,
Petr
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] default-distrovars: Drop DISTRO_FEATURES_LIBC

[Khem Raj]

On Mon, Feb 25, 2019 at 12:14 PM Andre McCurdy  wrote:
>
> On Mon, Feb 25, 2019 at 11:00 AM Khem Raj  wrote:
> >
> > After eglibc was merged into glibc, Kconfig support was also dropped so
> > these libc features therefore are not effective anymore and can be
> > removed
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/conf/distro/include/default-distrovars.inc | 10 +-
> >  meta/conf/local.conf.sample.extended| 16 ++--
> >  2 files changed, 3 insertions(+), 23 deletions(-)
> >
> > diff --git a/meta/conf/distro/include/default-distrovars.inc 
> > b/meta/conf/distro/include/default-distrovars.inc
> > index 76edff6480..35da7f10e1 100644
> > --- a/meta/conf/distro/include/default-distrovars.inc
> > +++ b/meta/conf/distro/include/default-distrovars.inc
> > @@ -11,15 +11,7 @@ LOCALE_UTF8_IS_DEFAULT ?= "1"
> >  LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
> >
> >  DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 irda largefile 
> > pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
> > -DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace libc-big-macros 
> > libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \
>
> There are a lot of recipes which check the ipv6 distro feature. Those
> recipe should probably be updated before this is merged.
>

I think I will move ipv6 and ipv4 to DISTRO_FEATURES_DEFAULT
that will avoid immediate need to address it systemwide.

> > -   libc-crypt-ufc libc-db-aliases 
> > libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
> > -   libc-getlogin libc-idn 
> > libc-inet-anl libc-libm libc-locales libc-locale-code \
> > -   libc-memusage libc-nsswitch 
> > libc-rcmd libc-rtld-debug libc-spawn libc-streams \
> > -   libc-utmp libc-utmpx libc-wordexp 
> > libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
> > -   libc-posix-wchar-io"
> > -DISTRO_FEATURES_LIBC ?= "${DISTRO_FEATURES_LIBC_DEFAULT}"
> > -DISTRO_FEATURES_LIBC_class-nativesdk = "${DISTRO_FEATURES_LIBC_DEFAULT}"
> > -DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
> > +DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
> >
> >  IMAGE_FEATURES ?= ""
> >
> > diff --git a/meta/conf/local.conf.sample.extended 
> > b/meta/conf/local.conf.sample.extended
> > index 010bf6ca6f..91e321047f 100644
> > --- a/meta/conf/local.conf.sample.extended
> > +++ b/meta/conf/local.conf.sample.extended
> > @@ -24,22 +24,10 @@
> >  # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" 
> > would
> >  # be appropriate for example.
> >
> > -
> > -# glibc configurability is used to reduce minimal image's size.
> > -# the all supported glibc options are listed in DISTRO_FEATURES_LIBC
> > -# and disabled by default. Uncomment and copy the DISTRO_FEATURES_LIBC
> > -# and DISTRO_FEATURES definitions to local.conf to enable the options.
> > -#DISTRO_FEATURES_LIBC = "ipv6 libc-backtrace libc-big-macros libc-bsd 
> > libc-cxx-tests libc-catgets libc-charsets libc-crypt \
> > -#   libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt 
> > libc-fmtmsg libc-fstab libc-ftraverse \
> > -#   libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm 
> > libc-locales libc-locale-code \
> > -#   libc-memusage libc-nsswitch libc-rcmd libc-rtld-debug 
> > libc-spawn libc-streams \
> > -#   libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar 
> > libc-posix-regexp libc-posix-regexp-glibc \
> > -#   libc-posix-wchar-io"
> > -
> > -#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> > nfs zeroconf pci ${DISTRO_FEATURES_LIBC}"
> > +#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> > nfs zeroconf pci"
> >
> >  # If you want to get an image based on directfb without x11, Please copy 
> > this variable to build/conf/local.conf
> > -#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia 
> > usbgadget usbhost wifi xattr nfs zeroconf pci 3g directfb 
> > ${DISTRO_FEATURES_LIBC}"
> > +#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia 
> > usbgadget usbhost wifi xattr nfs zeroconf pci 3g directfb"
> >
> >  # ENABLE_BINARY_LOCALE_GENERATION controls the generation of binary locale
> >  # packages at build time using qemu-native. Disabling it (by setting it to 
> > 0)
> > --
> > 2.20.1
> >
> > --
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] default-distrovars: Drop DISTRO_FEATURES_LIBC

[Jacob Kroon]

On Mon, Feb 25, 2019 at 8:00 PM Khem Raj  wrote:
>
> After eglibc was merged into glibc, Kconfig support was also dropped so
> these libc features therefore are not effective anymore and can be
> removed
>
> Signed-off-by: Khem Raj 
> ---
>  meta/conf/distro/include/default-distrovars.inc | 10 +-
>  meta/conf/local.conf.sample.extended| 16 ++--
>  2 files changed, 3 insertions(+), 23 deletions(-)
>
> diff --git a/meta/conf/distro/include/default-distrovars.inc 
> b/meta/conf/distro/include/default-distrovars.inc
> index 76edff6480..35da7f10e1 100644
> --- a/meta/conf/distro/include/default-distrovars.inc
> +++ b/meta/conf/distro/include/default-distrovars.inc
> @@ -11,15 +11,7 @@ LOCALE_UTF8_IS_DEFAULT ?= "1"
>  LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
>
>  DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 irda largefile 
> pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
> -DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace libc-big-macros 
> libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \
> -   libc-crypt-ufc libc-db-aliases 
> libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
> -   libc-getlogin libc-idn libc-inet-anl 
> libc-libm libc-locales libc-locale-code \
> -   libc-memusage libc-nsswitch libc-rcmd 
> libc-rtld-debug libc-spawn libc-streams \
> -   libc-utmp libc-utmpx libc-wordexp 
> libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
> -   libc-posix-wchar-io"
> -DISTRO_FEATURES_LIBC ?= "${DISTRO_FEATURES_LIBC_DEFAULT}"
> -DISTRO_FEATURES_LIBC_class-nativesdk = "${DISTRO_FEATURES_LIBC_DEFAULT}"
> -DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
> +DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
>

Maybe remove DISTRO_FEATURES_DEFAULT too ?

>  IMAGE_FEATURES ?= ""
>
> diff --git a/meta/conf/local.conf.sample.extended 
> b/meta/conf/local.conf.sample.extended
> index 010bf6ca6f..91e321047f 100644
> --- a/meta/conf/local.conf.sample.extended
> +++ b/meta/conf/local.conf.sample.extended
> @@ -24,22 +24,10 @@
>  # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" 
> would
>  # be appropriate for example.
>
> -
> -# glibc configurability is used to reduce minimal image's size.
> -# the all supported glibc options are listed in DISTRO_FEATURES_LIBC
> -# and disabled by default. Uncomment and copy the DISTRO_FEATURES_LIBC
> -# and DISTRO_FEATURES definitions to local.conf to enable the options.
> -#DISTRO_FEATURES_LIBC = "ipv6 libc-backtrace libc-big-macros libc-bsd 
> libc-cxx-tests libc-catgets libc-charsets libc-crypt \
> -#   libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt 
> libc-fmtmsg libc-fstab libc-ftraverse \
> -#   libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm 
> libc-locales libc-locale-code \
> -#   libc-memusage libc-nsswitch libc-rcmd libc-rtld-debug 
> libc-spawn libc-streams \
> -#   libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar 
> libc-posix-regexp libc-posix-regexp-glibc \
> -#   libc-posix-wchar-io"
> -
> -#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> nfs zeroconf pci ${DISTRO_FEATURES_LIBC}"
> +#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> nfs zeroconf pci"
>
>  # If you want to get an image based on directfb without x11, Please copy 
> this variable to build/conf/local.conf
> -#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget 
> usbhost wifi xattr nfs zeroconf pci 3g directfb ${DISTRO_FEATURES_LIBC}"
> +#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget 
> usbhost wifi xattr nfs zeroconf pci 3g directfb"
>
>  # ENABLE_BINARY_LOCALE_GENERATION controls the generation of binary locale
>  # packages at build time using qemu-native. Disabling it (by setting it to 0)
> --
> 2.20.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [RFC][PATCH v4] mesa: Convert recipe to use meson build system

[Burton, Ross]

packages/corei7-64-poky-linux/mesa/libgles1-mesa: FILELIST: removed
"/usr/lib/libGLESv1_CM.so.1.1.0", added
"/usr/lib/libGLESv1_CM.so.1.0.0"

Is that intentional?  Looks like a version mistake in the meson.build.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [RFC][PATCH v4] mesa: Convert recipe to use meson build system

[Burton, Ross]

So far:

rburton: according to this commit it's intentional:
cc15460e182148292be877bec5a8a61cec57377d
although I'm not sure that patch was correct now, it looks
like autotools has generated a 1.1.0 since 2014

On Mon, 25 Feb 2019 at 18:54, Burton, Ross  wrote:
>
> packages/corei7-64-poky-linux/mesa/libgles1-mesa: FILELIST: removed
> "/usr/lib/libGLESv1_CM.so.1.1.0", added
> "/usr/lib/libGLESv1_CM.so.1.0.0"
>
> Is that intentional?  Looks like a version mistake in the meson.build.
>
> Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 294 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7"
and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] default-distrovars: Drop DISTRO_FEATURES_LIBC

[Khem Raj]

On Mon, Feb 25, 2019 at 11:41 AM Jacob Kroon  wrote:
>
> On Mon, Feb 25, 2019 at 8:00 PM Khem Raj  wrote:
> >
> > After eglibc was merged into glibc, Kconfig support was also dropped so
> > these libc features therefore are not effective anymore and can be
> > removed
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  meta/conf/distro/include/default-distrovars.inc | 10 +-
> >  meta/conf/local.conf.sample.extended| 16 ++--
> >  2 files changed, 3 insertions(+), 23 deletions(-)
> >
> > diff --git a/meta/conf/distro/include/default-distrovars.inc 
> > b/meta/conf/distro/include/default-distrovars.inc
> > index 76edff6480..35da7f10e1 100644
> > --- a/meta/conf/distro/include/default-distrovars.inc
> > +++ b/meta/conf/distro/include/default-distrovars.inc
> > @@ -11,15 +11,7 @@ LOCALE_UTF8_IS_DEFAULT ?= "1"
> >  LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
> >
> >  DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 irda largefile 
> > pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
> > -DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace libc-big-macros 
> > libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \
> > -   libc-crypt-ufc libc-db-aliases 
> > libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
> > -   libc-getlogin libc-idn 
> > libc-inet-anl libc-libm libc-locales libc-locale-code \
> > -   libc-memusage libc-nsswitch 
> > libc-rcmd libc-rtld-debug libc-spawn libc-streams \
> > -   libc-utmp libc-utmpx libc-wordexp 
> > libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
> > -   libc-posix-wchar-io"
> > -DISTRO_FEATURES_LIBC ?= "${DISTRO_FEATURES_LIBC_DEFAULT}"
> > -DISTRO_FEATURES_LIBC_class-nativesdk = "${DISTRO_FEATURES_LIBC_DEFAULT}"
> > -DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
> > +DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
> >
>
> Maybe remove DISTRO_FEATURES_DEFAULT too ?
>

yes,  I think that can be done as well.

> >  IMAGE_FEATURES ?= ""
> >
> > diff --git a/meta/conf/local.conf.sample.extended 
> > b/meta/conf/local.conf.sample.extended
> > index 010bf6ca6f..91e321047f 100644
> > --- a/meta/conf/local.conf.sample.extended
> > +++ b/meta/conf/local.conf.sample.extended
> > @@ -24,22 +24,10 @@
> >  # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" 
> > would
> >  # be appropriate for example.
> >
> > -
> > -# glibc configurability is used to reduce minimal image's size.
> > -# the all supported glibc options are listed in DISTRO_FEATURES_LIBC
> > -# and disabled by default. Uncomment and copy the DISTRO_FEATURES_LIBC
> > -# and DISTRO_FEATURES definitions to local.conf to enable the options.
> > -#DISTRO_FEATURES_LIBC = "ipv6 libc-backtrace libc-big-macros libc-bsd 
> > libc-cxx-tests libc-catgets libc-charsets libc-crypt \
> > -#   libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt 
> > libc-fmtmsg libc-fstab libc-ftraverse \
> > -#   libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm 
> > libc-locales libc-locale-code \
> > -#   libc-memusage libc-nsswitch libc-rcmd libc-rtld-debug 
> > libc-spawn libc-streams \
> > -#   libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar 
> > libc-posix-regexp libc-posix-regexp-glibc \
> > -#   libc-posix-wchar-io"
> > -
> > -#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> > nfs zeroconf pci ${DISTRO_FEATURES_LIBC}"
> > +#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi 
> > nfs zeroconf pci"
> >
> >  # If you want to get an image based on directfb without x11, Please copy 
> > this variable to build/conf/local.conf
> > -#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia 
> > usbgadget usbhost wifi xattr nfs zeroconf pci 3g directfb 
> > ${DISTRO_FEATURES_LIBC}"
> > +#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia 
> > usbgadget usbhost wifi xattr nfs zeroconf pci 3g directfb"
> >
> >  # ENABLE_BINARY_LOCALE_GENERATION controls the generation of binary locale
> >  # packages at build time using qemu-native. Disabling it (by setting it to 
> > 0)
> > --
> > 2.20.1
> >
> > --
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH V2] musl: Update to latest beyond 1.21

[Khem Raj]

https://git.musl-libc.org/cgit/musl/log/?qt=range=1691b23955590d1eb66a11158fdd91c86337e886..6516282d2adfad2c7e66d854cde3357120c75dbd

Signed-off-by: Khem Raj 
---
v2: Fix TLS installation crash 

https://git.musl-libc.org/cgit/musl/commit/?id=6516282d2adfad2c7e66d854cde3357120c75dbd

 meta/recipes-core/musl/musl_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/musl/musl_git.bb 
b/meta/recipes-core/musl/musl_git.bb
index 73906d0f3c..f1052278c8 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -4,7 +4,7 @@
 require musl.inc
 inherit linuxloader
 
-SRCREV = "1691b23955590d1eb66a11158fdd91c86337e886"
+SRCREV = "6516282d2adfad2c7e66d854cde3357120c75dbd"
 
 BASEVER = "1.1.21"
 
-- 
2.20.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] default-distrovars: Drop DISTRO_FEATURES_LIBC

[Khem Raj]

After eglibc was merged into glibc, Kconfig support was also dropped so
these libc features therefore are not effective anymore and can be
removed

Signed-off-by: Khem Raj 
---
 meta/conf/distro/include/default-distrovars.inc | 10 +-
 meta/conf/local.conf.sample.extended| 16 ++--
 2 files changed, 3 insertions(+), 23 deletions(-)

diff --git a/meta/conf/distro/include/default-distrovars.inc 
b/meta/conf/distro/include/default-distrovars.inc
index 76edff6480..35da7f10e1 100644
--- a/meta/conf/distro/include/default-distrovars.inc
+++ b/meta/conf/distro/include/default-distrovars.inc
@@ -11,15 +11,7 @@ LOCALE_UTF8_IS_DEFAULT ?= "1"
 LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
 
 DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 irda largefile pcmcia 
usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
-DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace libc-big-macros 
libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \
-   libc-crypt-ufc libc-db-aliases 
libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
-   libc-getlogin libc-idn libc-inet-anl 
libc-libm libc-locales libc-locale-code \
-   libc-memusage libc-nsswitch libc-rcmd 
libc-rtld-debug libc-spawn libc-streams \
-   libc-utmp libc-utmpx libc-wordexp 
libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
-   libc-posix-wchar-io"
-DISTRO_FEATURES_LIBC ?= "${DISTRO_FEATURES_LIBC_DEFAULT}"
-DISTRO_FEATURES_LIBC_class-nativesdk = "${DISTRO_FEATURES_LIBC_DEFAULT}"
-DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
+DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
 
 IMAGE_FEATURES ?= ""
 
diff --git a/meta/conf/local.conf.sample.extended 
b/meta/conf/local.conf.sample.extended
index 010bf6ca6f..91e321047f 100644
--- a/meta/conf/local.conf.sample.extended
+++ b/meta/conf/local.conf.sample.extended
@@ -24,22 +24,10 @@
 # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" 
would
 # be appropriate for example.
 
-
-# glibc configurability is used to reduce minimal image's size.
-# the all supported glibc options are listed in DISTRO_FEATURES_LIBC
-# and disabled by default. Uncomment and copy the DISTRO_FEATURES_LIBC
-# and DISTRO_FEATURES definitions to local.conf to enable the options.
-#DISTRO_FEATURES_LIBC = "ipv6 libc-backtrace libc-big-macros libc-bsd 
libc-cxx-tests libc-catgets libc-charsets libc-crypt \
-#   libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt libc-fmtmsg 
libc-fstab libc-ftraverse \
-#   libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm 
libc-locales libc-locale-code \
-#   libc-memusage libc-nsswitch libc-rcmd libc-rtld-debug 
libc-spawn libc-streams \
-#   libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar 
libc-posix-regexp libc-posix-regexp-glibc \
-#   libc-posix-wchar-io"
-
-#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs 
zeroconf pci ${DISTRO_FEATURES_LIBC}"
+#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs 
zeroconf pci"
 
 # If you want to get an image based on directfb without x11, Please copy this 
variable to build/conf/local.conf
-#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget 
usbhost wifi xattr nfs zeroconf pci 3g directfb ${DISTRO_FEATURES_LIBC}"
+#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget 
usbhost wifi xattr nfs zeroconf pci 3g directfb"
 
 # ENABLE_BINARY_LOCALE_GENERATION controls the generation of binary locale
 # packages at build time using qemu-native. Disabling it (by setting it to 0)
-- 
2.20.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] glibc: Remove ChangeLog diff from patch

[Khem Raj]

On Mon, Feb 25, 2019 at 1:50 PM Alistair Francis
 wrote:
>
> To avoid conflicts with other forks of glibc remove the diff from the
> ChangeLog.
>

LGTM

> Signed-off-by: Alistair Francis 
> ---
>  ...e-unsigned-Jcc-instructions-on-size-.patch | 21 +--
>  1 file changed, 1 insertion(+), 20 deletions(-)
>
> diff --git 
> a/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
>  
> b/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
> index 1c625f63c7..1a343149c0 100644
> --- 
> a/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
> +++ 
> b/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
> @@ -21,33 +21,14 @@ Tested on x86-64 and x32, with and without 
> --disable-multi-arch.
>  CVE: CVE-2019-7309
>  Upstream-Status: Backport
>  Signed-off-by: Zhixiong Chi 
> +Signed-off-by: Alistair Francis 
>  ---
> - ChangeLog| 11 
>   sysdeps/x86_64/memcmp.S  | 20 +++---
>   sysdeps/x86_64/x32/Makefile  |  3 +-
>   sysdeps/x86_64/x32/tst-size_t-memcmp-2.c | 79 
>   5 files changed, 111 insertions(+), 10 deletions(-)
>   create mode 100644 sysdeps/x86_64/x32/tst-size_t-memcmp-2.c
>
> -diff --git a/ChangeLog b/ChangeLog
> -index 29bc4451ef..a0dcdac323 100644
>  a/ChangeLog
> -+++ b/ChangeLog
> -@@ -1,3 +1,14 @@
> -+2019-02-04  H.J. Lu  
> -+
> -+  [BZ #24155]
> -+  CVE-2019-7309
> -+  * NEWS: Updated for CVE-2019-7309.
> -+  * sysdeps/x86_64/memcmp.S: Use RDX_LP for size.  Clear the
> -+  upper 32 bits of RDX register for x32.  Use unsigned Jcc
> -+  instructions, instead of signed.
> -+  * sysdeps/x86_64/x32/Makefile (tests): Add tst-size_t-memcmp-2.
> -+  * sysdeps/x86_64/x32/tst-size_t-memcmp-2.c: New test.
> -+
> - 2019-01-31  Carlos O'Donell  
> -   Torvald Riegel  
> -   Rik Prohaska  
>  diff --git a/sysdeps/x86_64/memcmp.S b/sysdeps/x86_64/memcmp.S
>  index 1fc487caa5..1322bb3b92 100644
>  --- a/sysdeps/x86_64/memcmp.S
> --
> 2.20.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH][thud] mesa: ship /etc/drirc in mesa-megadriver

[Ross Burton]

Many years not shipping the stub drirc seemed like a good idea,
but now it has content and is essential for some applications to run.

Following patches in master, ship this file in mesa-megadriver.

Signed-off-by: Ross Burton 
---
 meta/recipes-graphics/mesa/mesa.inc | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-graphics/mesa/mesa.inc 
b/meta/recipes-graphics/mesa/mesa.inc
index 0cc0a82de49..f47f1aa20d8 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -141,8 +141,6 @@ do_install_append () {
 rm -f ${D}${libdir}/gallium-pipe/*.la
 rm -f ${D}${libdir}/gbm/*.la
 
-# it was packaged in libdricore9.1.3-1 and preventing upgrades when 
debian.bbclass was used 
-rm -f ${D}${sysconfdir}/drirc
 chrpath --delete ${D}${libdir}/dri/*_dri.so || true
 
 # libwayland-egl has been moved to wayland 1.15+
@@ -209,8 +207,8 @@ PACKAGESPLITFUNCS_prepend = "mesa_populate_packages "
 
 PACKAGES_DYNAMIC += "^mesa-driver-.*"
 
-FILES_${PN} += "${sysconfdir}/drirc"
-FILES_mesa-megadriver = "${libdir}/dri/*"
+FILES_${PN} = ""
+FILES_mesa-megadriver = "${libdir}/dri/* ${sysconfdir}"
 FILES_mesa-vulkan-drivers = "${libdir}/libvulkan_*.so ${datadir}/vulkan"
 FILES_libegl-mesa = "${libdir}/libEGL.so.*"
 FILES_libgbm = "${libdir}/libgbm.so.*"
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] [PATCH] sqlite3:upgrade to 3.27.2

[Hong Liu]

Upgrade sqlite from 3.26.0 to 3.27.2.

Signed-off-by: Hong Liu 
---
 meta/recipes-support/sqlite/sqlite3_3.26.0.bb | 10 --
 meta/recipes-support/sqlite/sqlite3_3.27.2.bb | 10 ++
 2 files changed, 10 insertions(+), 10 deletions(-)
 delete mode 100644 meta/recipes-support/sqlite/sqlite3_3.26.0.bb
 create mode 100644 meta/recipes-support/sqlite/sqlite3_3.27.2.bb

diff --git a/meta/recipes-support/sqlite/sqlite3_3.26.0.bb 
b/meta/recipes-support/sqlite/sqlite3_3.26.0.bb
deleted file mode 100644
index a0d615bac1..00
--- a/meta/recipes-support/sqlite/sqlite3_3.26.0.bb
+++ /dev/null
@@ -1,10 +0,0 @@
-require sqlite3.inc
-
-LICENSE = "PD"
-LIC_FILES_CHKSUM = 
"file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed00c66"
-
-SRC_URI = "\
-  http://www.sqlite.org/2018/sqlite-autoconf-${SQLITE_PV}.tar.gz \
-  "
-SRC_URI[md5sum] = "ac2b3b8cd3a97600e36fb8e756e8dda1"
-SRC_URI[sha256sum] = 
"5daa6a3fb7d1e8c767cd59c4ded8da6e4b00c61d3b466d0685e35c4dd6d7bf5d"
diff --git a/meta/recipes-support/sqlite/sqlite3_3.27.2.bb 
b/meta/recipes-support/sqlite/sqlite3_3.27.2.bb
new file mode 100644
index 00..294a546ab5
--- /dev/null
+++ b/meta/recipes-support/sqlite/sqlite3_3.27.2.bb
@@ -0,0 +1,10 @@
+require sqlite3.inc
+
+LICENSE = "PD"
+LIC_FILES_CHKSUM = 
"file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed00c66"
+
+SRC_URI = "\
+  http://www.sqlite.org/2019/sqlite-autoconf-${SQLITE_PV}.tar.gz \
+  "
+SRC_URI[md5sum] = "1f72631ce6e8efa5b4a6e55a43b3bdc0"
+SRC_URI[sha256sum] = 
"50c39e85ea28b5ecfdb3f9e860afe9ba606381e21836b2849efca6a0bfe6ef6e"
-- 
2.17.2



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/2] mesa-gl: Set PACKAGECONFIG for target

[Khem Raj]

mesa.inc uses PACKAGECONFIG_class-target override to setup default
packageconfigs, which means that when we build mesa-gl for target then
it does no honor the ??= setting we have in mesa-gl recipe, and ends up
compiling egl, gles2 as well, which is not intended.

Signed-off-by: Khem Raj 
---
 meta/recipes-graphics/mesa/mesa-gl_18.3.4.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-graphics/mesa/mesa-gl_18.3.4.bb 
b/meta/recipes-graphics/mesa/mesa-gl_18.3.4.bb
index 73267eb4f0..d4b1c1c454 100644
--- a/meta/recipes-graphics/mesa/mesa-gl_18.3.4.bb
+++ b/meta/recipes-graphics/mesa/mesa-gl_18.3.4.bb
@@ -7,3 +7,4 @@ PROVIDES = "virtual/libgl virtual/mesa"
 S = "${WORKDIR}/mesa-${PV}"
 
 PACKAGECONFIG ??= "opengl dri ${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}"
+PACKAGECONFIG_class-target = "opengl dri ${@bb.utils.filter('DISTRO_FEATURES', 
'x11', d)}"
-- 
2.20.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH V2 1/2] default-distrovars: Drop DISTRO_FEATURES_LIBC

[Khem Raj]

After eglibc was merged into glibc, Kconfig support was also dropped so
these libc features therefore are not effective anymore and can be
removed

Signed-off-by: Khem Raj 
---
v2:
- Add ipv4 and ipv6 to default distro features, they are not libc
  specific anyway
- Remove DISTRO_FEATURES_DEFAULT as this is redundant now

 meta/conf/distro/include/default-distrovars.inc | 11 +--
 meta/conf/local.conf.sample.extended| 16 ++--
 2 files changed, 3 insertions(+), 24 deletions(-)

diff --git a/meta/conf/distro/include/default-distrovars.inc 
b/meta/conf/distro/include/default-distrovars.inc
index 76edff6480..d57329ec17 100644
--- a/meta/conf/distro/include/default-distrovars.inc
+++ b/meta/conf/distro/include/default-distrovars.inc
@@ -10,16 +10,7 @@ LOCALE_UTF8_ONLY ?= "0"
 LOCALE_UTF8_IS_DEFAULT ?= "1"
 LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
 
-DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 irda largefile pcmcia 
usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
-DISTRO_FEATURES_LIBC_DEFAULT ?= "ipv4 ipv6 libc-backtrace libc-big-macros 
libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt \
-   libc-crypt-ufc libc-db-aliases 
libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse \
-   libc-getlogin libc-idn libc-inet-anl 
libc-libm libc-locales libc-locale-code \
-   libc-memusage libc-nsswitch libc-rcmd 
libc-rtld-debug libc-spawn libc-streams \
-   libc-utmp libc-utmpx libc-wordexp 
libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc \
-   libc-posix-wchar-io"
-DISTRO_FEATURES_LIBC ?= "${DISTRO_FEATURES_LIBC_DEFAULT}"
-DISTRO_FEATURES_LIBC_class-nativesdk = "${DISTRO_FEATURES_LIBC_DEFAULT}"
-DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
+DISTRO_FEATURES ?= "acl alsa argp bluetooth ext2 ipv4 ipv6 irda largefile 
pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11"
 
 IMAGE_FEATURES ?= ""
 
diff --git a/meta/conf/local.conf.sample.extended 
b/meta/conf/local.conf.sample.extended
index 010bf6ca6f..0743fefece 100644
--- a/meta/conf/local.conf.sample.extended
+++ b/meta/conf/local.conf.sample.extended
@@ -24,22 +24,10 @@
 # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" 
would
 # be appropriate for example.
 
-
-# glibc configurability is used to reduce minimal image's size.
-# the all supported glibc options are listed in DISTRO_FEATURES_LIBC
-# and disabled by default. Uncomment and copy the DISTRO_FEATURES_LIBC
-# and DISTRO_FEATURES definitions to local.conf to enable the options.
-#DISTRO_FEATURES_LIBC = "ipv6 libc-backtrace libc-big-macros libc-bsd 
libc-cxx-tests libc-catgets libc-charsets libc-crypt \
-#   libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt libc-fmtmsg 
libc-fstab libc-ftraverse \
-#   libc-getlogin libc-idn libc-inet libc-inet-anl libc-libm 
libc-locales libc-locale-code \
-#   libc-memusage libc-nsswitch libc-rcmd libc-rtld-debug 
libc-spawn libc-streams \
-#   libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar 
libc-posix-regexp libc-posix-regexp-glibc \
-#   libc-posix-wchar-io"
-
-#DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs 
zeroconf pci ${DISTRO_FEATURES_LIBC}"
+#DISTRO_FEATURES = "alsa bluetooth ext2 irda ipv4 ipv6 pcmcia usbgadget 
usbhost wifi nfs zeroconf pci"
 
 # If you want to get an image based on directfb without x11, Please copy this 
variable to build/conf/local.conf
-#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget 
usbhost wifi xattr nfs zeroconf pci 3g directfb ${DISTRO_FEATURES_LIBC}"
+#DISTRO_FEATURES = "alsa argp bluetooth ext2 irda ipv4 ipv6 largefile pcmcia 
usbgadget usbhost wifi xattr nfs zeroconf pci 3g directfb"
 
 # ENABLE_BINARY_LOCALE_GENERATION controls the generation of binary locale
 # packages at build time using qemu-native. Disabling it (by setting it to 0)
-- 
2.20.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] libdazzle: add check for GTK3DISTROFEATURES

[mingli.yu]

From: Mingli Yu 

When do world buid, there comes below error:
| ERROR: Nothing PROVIDES 'gtk+3' (but 
/build/layers/oe-core/meta/recipes-gnome/libdazzle/libdazzle_3.30.2.bb DEPENDS 
on or otherwise requires it)
| gtk+3 was skipped: one of 'x11 wayland' needs to be in DISTRO_FEATURES

Add the check for GTK3DISTROFEATURES to make
the world build work even without GTK3DISTROFEATURES.

Signed-off-by: Mingli Yu 
---
 meta/recipes-gnome/libdazzle/libdazzle_3.30.2.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-gnome/libdazzle/libdazzle_3.30.2.bb 
b/meta/recipes-gnome/libdazzle/libdazzle_3.30.2.bb
index 5441c10..3779b15 100644
--- a/meta/recipes-gnome/libdazzle/libdazzle_3.30.2.bb
+++ b/meta/recipes-gnome/libdazzle/libdazzle_3.30.2.bb
@@ -3,7 +3,7 @@ LICENSE = "GPLv3+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=8f0e2cd40e05189ec81232da84bd6e1a"
 
 GNOMEBASEBUILDCLASS = "meson"
-inherit gnomebase upstream-version-is-even vala gobject-introspection
+inherit gnomebase upstream-version-is-even vala distro_features_check 
gobject-introspection
 
 DEPENDS = "glib-2.0-native glib-2.0 gtk+3"
 
@@ -14,5 +14,7 @@ SRC_URI[archive.sha256sum] = 
"78770eae9fa15ac5acb9c733d29459330b2540affbf7293311
 GI_ENABLE_FLAG = "-Dwith_introspection=true"
 GI_DISABLE_FLAG = "-Dwith_introspection=false"
 
+ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
+
 EXTRA_OEMESON_append_class-target = " ${@bb.utils.contains('GI_DATA_ENABLED', 
'True', '${GI_ENABLE_FLAG}', \

'${GI_DISABLE_FLAG}', d)} "
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] ltp: Add patch for string formatting security warning

[Daniel Díaz]

A revamp of the syscalls/setregid tests made to use a new
library [LTP:7a1b4427] required a conversion to test messages.
This test in particular did not include a formatted string,
but a just a string element:
  testcases/kernel/syscalls/setregid/setregid01.c

This patch allows LTP to be built with -Wformat,
-Wformat-security, and -Werror=format-security.

Signed-off-by: Daniel Díaz 
---
 ...etregid01-security-string-formatting.patch | 46 +++
 meta/recipes-extended/ltp/ltp_20190115.bb |  6 +--
 2 files changed, 47 insertions(+), 5 deletions(-)
 create mode 100644 
meta/recipes-extended/ltp/ltp/setregid01-security-string-formatting.patch

diff --git 
a/meta/recipes-extended/ltp/ltp/setregid01-security-string-formatting.patch 
b/meta/recipes-extended/ltp/ltp/setregid01-security-string-formatting.patch
new file mode 100644
index 00..24449148f2
--- /dev/null
+++ b/meta/recipes-extended/ltp/ltp/setregid01-security-string-formatting.patch
@@ -0,0 +1,46 @@
+From 430e05c2169ed15aaa6d7f9459edd607603cee02 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Daniel=20D=C3=ADaz?= 
+Date: Mon, 25 Feb 2019 10:44:33 -0600
+Subject: [PATCH] setregid01: Fix security warning for string formatting
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+GCC 8.2.0 complains with the following:
+  setregid01.c: In function 'run':
+  setregid01.c:47:3: error: format not a string literal and no format 
arguments [-Werror=format-security]
+ tst_res(TFAIL | TTERRNO, tc->msg);
+ ^~~
+because there is no string formatting in the message. This can
+be seen with CFLAGS set to:
+  -Wformat -Wformat-security -Werror=format-security
+as Yocto Project's Poky does, e.g.:
+  http://errors.yoctoproject.org/Errors/Details/230043/
+
+Upstream-Status: Backport [46e1eda55f188810e6bf3a939b92d604321807ae]
+
+Signed-off-by: Daniel Díaz 
+Reviewed-by: Enji Cooper 
+---
+ testcases/kernel/syscalls/setregid/setregid01.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/testcases/kernel/syscalls/setregid/setregid01.c 
b/testcases/kernel/syscalls/setregid/setregid01.c
+index f2e41e134..8c9e11918 100644
+--- a/testcases/kernel/syscalls/setregid/setregid01.c
 b/testcases/kernel/syscalls/setregid/setregid01.c
+@@ -44,9 +44,9 @@ static void run(unsigned int n)
+   TEST(SETREGID(*tc->arg1, *tc->arg2));
+ 
+   if (TST_RET == -1)
+-  tst_res(TFAIL | TTERRNO, tc->msg);
++  tst_res(TFAIL | TTERRNO, "%s", tc->msg);
+   else
+-  tst_res(TPASS, tc->msg);
++  tst_res(TPASS, "%s", tc->msg);
+ }
+ 
+ static void setup(void)
+-- 
+2.17.1
+
diff --git a/meta/recipes-extended/ltp/ltp_20190115.bb 
b/meta/recipes-extended/ltp/ltp_20190115.bb
index ed1cb27112..ddf97e26ce 100644
--- a/meta/recipes-extended/ltp/ltp_20190115.bb
+++ b/meta/recipes-extended/ltp/ltp_20190115.bb
@@ -29,11 +29,6 @@ CFLAGS_append_powerpc64 = " -D__SANE_USERSPACE_TYPES__"
 CFLAGS_append_mipsarchn64 = " -D__SANE_USERSPACE_TYPES__"
 SRCREV = "a6a5caef13632e669dda27b0461726eba546a2f3"
 
-# ltp doesn't currently build cleanly with
-# "-Wformat -Wformat-security -Werror=format-security" in CFLAGS
-# remove this when it does
-SECURITY_STRINGFORMAT = ""
-
 SRC_URI = "git://github.com/linux-test-project/ltp.git \
file://0004-build-Add-option-to-select-libc-implementation.patch \

file://0005-kernel-controllers-Link-with-libfts-explicitly-on-mu.patch \
@@ -53,6 +48,7 @@ SRC_URI = "git://github.com/linux-test-project/ltp.git \
file://0039-commands-ar01-Fix-for-test-in-deterministic-mode.patch \

file://0001-open_posix_testsuite-mmap24-2-Relax-condition-a-bit.patch \
file://define-sigrtmin-and-sigrtmax-for-musl.patch \
+   file://setregid01-security-string-formatting.patch \
"
 
 S = "${WORKDIR}/git"
-- 
2.17.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] openssl10: Fix mutliple include assumptions for bn.h in opensslconf.h

[Denys Dmytriyenko]

Khem, Richard,

Sorry for belated reply. I haven't had time for master yet, but since this 
just got backported to thud, I'm seeing a similar breakage.

First of all, BN_LLONG not being defined does seem to be "fixed" by this 
patch, but I'm not entirely sure why it now checks for OPENSSL_SYS_UEFI - this 
seems to be a new define in OpenSSL 1.1, and doesn't even exist in OpenSSL 1.0
Is it a pure luck that it works now? Any hidden meaning I missded?

And it also breaks exactly the same for DES_LONG due to a similar construct:


#if (defined(HEADER_NEW_DES_H) || defined(HEADER_DES_H)) && !defined(DES_LONG)
/* If this is set to 'unsigned int' on a DEC Alpha, this gives about a
 * %20 speed up (longs are 8 bytes, int's are 4). */
#ifndef DES_LONG
#define DES_LONG unsigned int
#endif
#endif


I was going to fix it similarly as BN_LLONG, but since I don't understand how 
it was supposed to be fixed, I'm not sure how to fix DES_LONG not being 
defined. Any ideas?

Thanks.

-- 
Denys


On Wed, Feb 06, 2019 at 10:25:26PM -0800, Khem Raj wrote:
> After adding #pragma once to wrapper header ( opensslconf.h ) this
> latent issue got to bite us, where it expect bn.h to be including
> openssl.h to define BN_* defines, which is fragile. This patch removes
> the contraints for nested includes for bn.h
> 
> Signed-off-by: Khem Raj 
> ---
>  .../0001-Fix-BN_LLONG-breakage.patch  | 33 +++
>  .../openssl/openssl10_1.0.2q.bb   |  1 +
>  2 files changed, 34 insertions(+)
>  create mode 100644 
> meta/recipes-connectivity/openssl/openssl10/0001-Fix-BN_LLONG-breakage.patch
> 
> diff --git 
> a/meta/recipes-connectivity/openssl/openssl10/0001-Fix-BN_LLONG-breakage.patch
>  
> b/meta/recipes-connectivity/openssl/openssl10/0001-Fix-BN_LLONG-breakage.patch
> new file mode 100644
> index 00..13d39c918c
> --- /dev/null
> +++ 
> b/meta/recipes-connectivity/openssl/openssl10/0001-Fix-BN_LLONG-breakage.patch
> @@ -0,0 +1,33 @@
> +From 247b3188cde5f3347091cd54271127386d3aece0 Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Wed, 6 Feb 2019 22:10:33 -0800
> +Subject: [PATCH] Fix BN_LLONG breakage
> +
> +opensslconf.h is un-defining BN_LLONG only when included from bn.h which
> +is not robust at all, especially when include guards are used and
> +multiple inclusions of a given header is not allowed. so lets take out
> +the nesting constraint and add OPENSSL_SYS_UEFI constraint instead
> +
> +Upstream-Status: Inappropriate [ fixed differently with OpenSSL 1.1+ ]
> +
> +Signed-off-by: Khem Raj 
> +---
> + crypto/opensslconf.h.in | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/crypto/opensslconf.h.in b/crypto/opensslconf.h.in
> +index 7a1c85d..a10c10f 100644
> +--- a/crypto/opensslconf.h.in
>  b/crypto/opensslconf.h.in
> +@@ -56,7 +56,7 @@
> + #endif
> + #endif
> + 
> +-#if defined(HEADER_BN_H) && !defined(CONFIG_HEADER_BN_H)
> ++#if !defined(OPENSSL_SYS_UEFI) && !defined(CONFIG_HEADER_BN_H)
> + #define CONFIG_HEADER_BN_H
> + #undef BN_LLONG
> + 
> +-- 
> +2.20.1
> +
> diff --git a/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb 
> b/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb
> index 809634f6c0..88aefdea4f 100644
> --- a/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb
> +++ b/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb
> @@ -40,6 +40,7 @@ SRC_URI = 
> "http://www.openssl.org/source/openssl-${PV}.tar.gz \
> file://0001-Fix-build-with-clang-using-external-assembler.patch \
> file://0001-openssl-force-soft-link-to-avoid-rare-race.patch \
> file://0001-allow-manpages-to-be-disabled.patch \
> +   file://0001-Fix-BN_LLONG-breakage.patch \
> "
>  
>  SRC_URI_append_class-target = " \
> -- 
> 2.20.1
> 
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] glibc: Remove ChangeLog diff from patch

[Alistair Francis]

To avoid conflicts with other forks of glibc remove the diff from the
ChangeLog.

Signed-off-by: Alistair Francis 
---
 ...e-unsigned-Jcc-instructions-on-size-.patch | 21 +--
 1 file changed, 1 insertion(+), 20 deletions(-)

diff --git 
a/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
 
b/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
index 1c625f63c7..1a343149c0 100644
--- 
a/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
+++ 
b/meta/recipes-core/glibc/glibc/0001-x86-64-memcmp-Use-unsigned-Jcc-instructions-on-size-.patch
@@ -21,33 +21,14 @@ Tested on x86-64 and x32, with and without 
--disable-multi-arch.
 CVE: CVE-2019-7309
 Upstream-Status: Backport
 Signed-off-by: Zhixiong Chi 
+Signed-off-by: Alistair Francis 
 ---
- ChangeLog| 11 
  sysdeps/x86_64/memcmp.S  | 20 +++---
  sysdeps/x86_64/x32/Makefile  |  3 +-
  sysdeps/x86_64/x32/tst-size_t-memcmp-2.c | 79 
  5 files changed, 111 insertions(+), 10 deletions(-)
  create mode 100644 sysdeps/x86_64/x32/tst-size_t-memcmp-2.c
 
-diff --git a/ChangeLog b/ChangeLog
-index 29bc4451ef..a0dcdac323 100644
 a/ChangeLog
-+++ b/ChangeLog
-@@ -1,3 +1,14 @@
-+2019-02-04  H.J. Lu  
-+
-+  [BZ #24155]
-+  CVE-2019-7309
-+  * NEWS: Updated for CVE-2019-7309.
-+  * sysdeps/x86_64/memcmp.S: Use RDX_LP for size.  Clear the
-+  upper 32 bits of RDX register for x32.  Use unsigned Jcc
-+  instructions, instead of signed.
-+  * sysdeps/x86_64/x32/Makefile (tests): Add tst-size_t-memcmp-2.
-+  * sysdeps/x86_64/x32/tst-size_t-memcmp-2.c: New test.
-+
- 2019-01-31  Carlos O'Donell  
-   Torvald Riegel  
-   Rik Prohaska  
 diff --git a/sysdeps/x86_64/memcmp.S b/sysdeps/x86_64/memcmp.S
 index 1fc487caa5..1322bb3b92 100644
 --- a/sysdeps/x86_64/memcmp.S
-- 
2.20.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] [PATCH] wayland:Upgrade to 1.16.91

[Hong Liu]

Upgrade wayland from 1.16.0 to 1.16.91.

Signed-off-by: Hong Liu 
---
 .../wayland/{wayland_1.16.0.bb => wayland_1.16.91.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/wayland/{wayland_1.16.0.bb => wayland_1.16.91.bb} 
(92%)

diff --git a/meta/recipes-graphics/wayland/wayland_1.16.0.bb 
b/meta/recipes-graphics/wayland/wayland_1.16.91.bb
similarity index 92%
rename from meta/recipes-graphics/wayland/wayland_1.16.0.bb
rename to meta/recipes-graphics/wayland/wayland_1.16.91.bb
index 112ee1a25e..8d7a06cdde 100644
--- a/meta/recipes-graphics/wayland/wayland_1.16.0.bb
+++ b/meta/recipes-graphics/wayland/wayland_1.16.91.bb
@@ -15,8 +15,8 @@ DEPENDS = "expat libxml2 libffi wayland-native"
 SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
   file://fixpathinpcfiles.patch \
"
-SRC_URI[md5sum] = "0c215e53de71d6fb26f7102cdc6432d3"
-SRC_URI[sha256sum] = 
"4e72c2b56109ccfb6610d776e465f4ca0af2280c9c2f7d5cc23f0ed2548752f5"
+SRC_URI[md5sum] = "711fea532899f2de096ebafdc54d1e3f"
+SRC_URI[sha256sum] = 
"d51b83a51034ed5474517e0b0bca2d4e7056e4c51d720ea885f0c34f243fee90"
 
 UPSTREAM_CHECK_URI = "https://wayland.freedesktop.org/releases.html;
 
-- 
2.17.2



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] [PATCH] wayland:Upgrade to 1.16.91

[Burton, Ross]

>From https://wayland.freedesktop.org/releases.html:

"The alphas for Wayland 1.17 (version 1.16.91) and Weston 6.0 (version
5.0.91) were released."

We don't ship alpha releases.

Ross

On Tue, 26 Feb 2019 at 05:59, Hong Liu  wrote:
>
> Upgrade wayland from 1.16.0 to 1.16.91.
>
> Signed-off-by: Hong Liu 
> ---
>  .../wayland/{wayland_1.16.0.bb => wayland_1.16.91.bb} | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename meta/recipes-graphics/wayland/{wayland_1.16.0.bb => 
> wayland_1.16.91.bb} (92%)
>
> diff --git a/meta/recipes-graphics/wayland/wayland_1.16.0.bb 
> b/meta/recipes-graphics/wayland/wayland_1.16.91.bb
> similarity index 92%
> rename from meta/recipes-graphics/wayland/wayland_1.16.0.bb
> rename to meta/recipes-graphics/wayland/wayland_1.16.91.bb
> index 112ee1a25e..8d7a06cdde 100644
> --- a/meta/recipes-graphics/wayland/wayland_1.16.0.bb
> +++ b/meta/recipes-graphics/wayland/wayland_1.16.91.bb
> @@ -15,8 +15,8 @@ DEPENDS = "expat libxml2 libffi wayland-native"
>  SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
>file://fixpathinpcfiles.patch \
> "
> -SRC_URI[md5sum] = "0c215e53de71d6fb26f7102cdc6432d3"
> -SRC_URI[sha256sum] = 
> "4e72c2b56109ccfb6610d776e465f4ca0af2280c9c2f7d5cc23f0ed2548752f5"
> +SRC_URI[md5sum] = "711fea532899f2de096ebafdc54d1e3f"
> +SRC_URI[sha256sum] = 
> "d51b83a51034ed5474517e0b0bca2d4e7056e4c51d720ea885f0c34f243fee90"
>
>  UPSTREAM_CHECK_URI = "https://wayland.freedesktop.org/releases.html;
>
> --
> 2.17.2
>
>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [sumo][PATCH 1/8] systemd: fix CVE-2018-15686

[George McCollister]

From: Chen Qi 

Backport patch to fix the following CVE.

CVE: CVE-2018-15686

Signed-off-by: Chen Qi 
Signed-off-by: Richard Purdie 

Cherry-picked from thud 0ef70603bc983315eb0e8a97958d995a31198c35

Signed-off-by: George McCollister 
---
 ...eserializing-state-always-use-read_line-L.patch | 250 +
 meta/recipes-core/systemd/systemd_237.bb   |   1 +
 2 files changed, 251 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
 
b/meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
new file mode 100644
index 00..405300148a
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
@@ -0,0 +1,250 @@
+From 56f77f7fcceea2fbb3b4efb8e307dd7784c63115 Mon Sep 17 00:00:00 2001
+From: Lennart Poettering 
+Date: Wed, 17 Oct 2018 18:36:24 +0200
+Subject: [PATCH] =?UTF-8?q?=3D=3FUTF-8=3Fq=3Fcore:=3D20when=3D20deserializ?=
+ =?UTF-8?q?ing=3D20state=3D20always=3F=3D?=
+
+ =?UTF-8?q?=20use=20read=5Fline(=E2=80=A6,=20LONG=5FLINE=5FMAX,=20?=
+ =?UTF-8?q?=E2=80=A6)?=
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+This should be much better than fgets(), as we can read substantially
+longer lines and overly long lines result in proper errors.
+
+Fixes a vulnerability discovered by Jann Horn at Google.
+
+CVE-2018-15686
+LP: #1796402
+https://bugzilla.redhat.com/show_bug.cgi?id=1639071
+
+(cherry picked from commit 8948b3415d762245ebf5e19d80b97d4d8cc208c1)
+
+CVE: CVE-2018-15686
+Upstream-Status: Backport
+
+Signed-off-by: Chen Qi 
+
+---
+ src/core/job.c | 19 +++
+ src/core/manager.c | 44 
+ src/core/unit.c| 34 ++
+ src/core/unit.h|  2 +-
+ 4 files changed, 50 insertions(+), 49 deletions(-)
+
+diff --git a/src/core/job.c b/src/core/job.c
+index c6de8d27e..e0f9cee2f 100644
+--- a/src/core/job.c
 b/src/core/job.c
+@@ -28,6 +28,7 @@
+ #include "dbus-job.h"
+ #include "dbus.h"
+ #include "escape.h"
++#include "fileio.h"
+ #include "job.h"
+ #include "log.h"
+ #include "macro.h"
+@@ -1067,24 +1068,26 @@ int job_serialize(Job *j, FILE *f) {
+ }
+ 
+ int job_deserialize(Job *j, FILE *f) {
++int r;
++
+ assert(j);
+ assert(f);
+ 
+ for (;;) {
+-char line[LINE_MAX], *l, *v;
++_cleanup_free_ char *line = NULL;
++char *l, *v;
+ size_t k;
+ 
+-if (!fgets(line, sizeof(line), f)) {
+-if (feof(f))
+-return 0;
+-return -errno;
+-}
++r = read_line(f, LONG_LINE_MAX, );
++if (r < 0)
++return log_error_errno(r, "Failed to read 
serialization line: %m");
++if (r == 0)
++return 0;
+ 
+-char_array_0(line);
+ l = strstrip(line);
+ 
+ /* End marker */
+-if (l[0] == 0)
++if (isempty(l))
+ return 0;
+ 
+ k = strcspn(l, "=");
+diff --git a/src/core/manager.c b/src/core/manager.c
+index e837a46f5..423f82c94 100644
+--- a/src/core/manager.c
 b/src/core/manager.c
+@@ -2841,22 +2841,19 @@ int manager_deserialize(Manager *m, FILE *f, FDSet 
*fds) {
+ m->n_reloading++;
+ 
+ for (;;) {
+-char line[LINE_MAX];
++_cleanup_free_ char *line = NULL;
+ const char *val, *l;
+ 
+-if (!fgets(line, sizeof(line), f)) {
+-if (feof(f))
+-r = 0;
+-else
+-r = -errno;
+-
++r = read_line(f, LONG_LINE_MAX, );
++if (r < 0) {
++log_error_errno(r, "Failed to read serialization 
line: %m");
+ goto finish;
+ }
++if (r == 0)
++break;
+ 
+-char_array_0(line);
+ l = strstrip(line);
+-
+-if (l[0] == 0)
++if (isempty(l)) /* end marker */
+ break;
+ 
+ if ((val = startswith(l, "current-job-id="))) {
+@@ -3003,29 +3000,31 @@ int manager_deserialize(Manager *m, FILE *f, FDSet 
*fds) {
+ }
+ 
+ for (;;) {
+-Unit *u;
+-char name[UNIT_NAME_MAX+2];
++_cleanup_free_ char *line = NULL;
+ const char* unit_name;
++Unit *u;
+ 
+ /* Start marker */
+-

[OE-core] [sumo][PATCH 0/8] systemd: fix CVEs

[George McCollister]

Apply CVE patches to systemd. Backport changes from thud when possible
otherwise use patches from:
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.13

The following changes since commit 31f0c5e59c7fb0ae0915de584fbfcf3d95bbb061:

  testsdk: Improvements to the json logging (2018-12-07 10:56:32 +)

are available in the git repository at:

  git://github.com/gmccollister/openembedded-core sumo-cve-fixes
  https://github.com/gmccollister/openembedded-core/tree/sumo-cve-fixes

Chen Qi (2):
  systemd: fix CVE-2018-15686
  systemd: fix CVE-2018-15688

George McCollister (5):
  systemd: fix CVE-2018-15687
  systemd: Security fix CVE-2018-16864
  systemd: Security fix CVE-2018-16865
  systemd: fix CVE-2018-6954
  systemd: fix CVE-2019-6454

Marcus Cooper (1):
  systemd: Security fix CVE-2018-16866

 ...sive-let-s-rework-the-recursive-logic-to-.patch |  252 +++
 ...eserializing-state-always-use-read_line-L.patch |  250 +++
 ...sure-we-have-enough-space-for-the-DHCP6-o.patch |   39 +
 ...n-t-resolve-pathnames-when-traversing-rec.patch |  643 +++
 .../systemd/systemd/0002-Make-tmpfiles-safe.patch  | 1828 
 ...-not-store-the-iovec-entry-for-process-co.patch |  193 +++
 ...ld-set-a-limit-on-the-number-of-fields-1k.patch |   60 +
 ...ote-set-a-limit-on-the-number-of-fields-i.patch |   79 +
 ...nal-fix-out-of-bounds-read-CVE-2018-16866.patch |   49 +
 .../systemd/systemd/CVE-2019-6454.patch|  210 +++
 ...e-receive-an-invalid-dbus-message-ignore-.patch |   61 +
 meta/recipes-core/systemd/systemd_237.bb   |   11 +
 12 files changed, 3675 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0002-Make-tmpfiles-safe.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
 create mode 100644 meta/recipes-core/systemd/systemd/CVE-2019-6454.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/sd-bus-if-we-receive-an-invalid-dbus-message-ignore-.patch

-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [sumo][PATCH 7/8] systemd: fix CVE-2018-6954

[George McCollister]

Apply patches to fix CVE-2018-6954

NVD description from https://nvd.nist.gov/vuln/detail/CVE-2018-6954

systemd-tmpfiles in systemd through 237 mishandles symlinks present in
non-terminal path components, which allows local users to obtain
ownership of arbitrary files via vectors involving creation of a
directory and a file under that directory, and later replacing that
directory with a symlink. This occurs even if the fs.protected_symlinks
sysctl is turned on.

Patches from systemd_237-3ubuntu10.13.debian.

These patches shouldn't be required on newer OE releases since they use
systemd v239 or higher.

Signed-off-by: George McCollister 
---
 ...n-t-resolve-pathnames-when-traversing-rec.patch |  643 +++
 .../systemd/systemd/0002-Make-tmpfiles-safe.patch  | 1828 
 meta/recipes-core/systemd/systemd_237.bb   |2 +
 3 files changed, 2473 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0002-Make-tmpfiles-safe.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
 
b/meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
new file mode 100644
index 00..108e4ad8b8
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
@@ -0,0 +1,643 @@
+From 33dc9a280f952f503e5493ee29f6815bef29d551 Mon Sep 17 00:00:00 2001
+From: Franck Bui 
+Date: Fri, 2 Mar 2018 17:19:32 +0100
+Subject: [PATCH] tmpfiles: don't resolve pathnames when traversing recursively
+ through directory trees
+
+Otherwise we can be fooled if one path component is replaced underneath us.
+
+The patch achieves that by always operating at file descriptor level (by using
+*at() helpers) and by making sure we do not any path resolution when traversing
+direcotry trees.
+
+However this is not always possible, for instance when listing the content of a
+directory or some operations don't provide the *at() helpers or others (such as
+fchmodat()) don't have the AT_EMPTY_PATH flag. In such cases we operate on
+/proc/self/fd/%i pseudo-symlink instead, which works the same for all kinds of
+objects and requires no checking of type beforehand.
+
+Also O_PATH flag is used when opening file objects in order to prevent
+undesired behaviors: device nodes from reacting, automounts from
+triggering, etc...
+
+Fixes: CVE-2018-6954
+
+Origin: upstream, 
https://github.com/systemd/systemd/commit/936f6bdb803c432578e2cdcc5f93f3bfff93aff0
+Bug: https://github.com/systemd/systemd/issues/7986
+
+Patch from:
+systemd_237-3ubuntu10.13.debian CVE-2018-6954.patch
+
+https://usn.ubuntu.com/3816-1/ states that CVE-2018-6954 doesn't
+affect Ubuntu 18.10 which uses the same version of systemd as thud
+(239).
+
+CVE: CVE-2018-6954
+Upstream-Status: Backport
+
+Signed-off-by: George McCollister 
+---
+ src/tmpfiles/tmpfiles.c | 363 +++-
+ 1 file changed, 239 insertions(+), 124 deletions(-)
+
+diff --git a/src/tmpfiles/tmpfiles.c b/src/tmpfiles/tmpfiles.c
+index 88cc543f09..613d418eb3 100644
+--- a/src/tmpfiles/tmpfiles.c
 b/src/tmpfiles/tmpfiles.c
+@@ -792,94 +792,105 @@ static bool hardlink_vulnerable(struct stat *st) {
+ return !S_ISDIR(st->st_mode) && st->st_nlink > 1 && 
dangerous_hardlinks();
+ }
+ 
+-static int path_set_perms(Item *i, const char *path) {
+-char fn[STRLEN("/proc/self/fd/") + DECIMAL_STR_MAX(int)];
+-_cleanup_close_ int fd = -1;
+-struct stat st;
++static int fd_set_perms(Item *i, int fd, const struct stat *st) {
++_cleanup_free_ char *path = NULL;
++int r;
+ 
+ assert(i);
+-assert(path);
+-
+-if (!i->mode_set && !i->uid_set && !i->gid_set)
+-goto shortcut;
+-
+-/* We open the file with O_PATH here, to make the operation
+- * somewhat atomic. Also there's unfortunately no fchmodat()
+- * with AT_SYMLINK_NOFOLLOW, hence we emulate it here via
+- * O_PATH. */
+-
+-fd = open(path, O_NOFOLLOW|O_CLOEXEC|O_PATH);
+-if (fd < 0) {
+-int level = LOG_ERR, r = -errno;
++assert(fd);
+ 
+-/* Option "e" operates only on existing objects. Do not
+- * print errors about non-existent files or directories */
+-if (i->type == EMPTY_DIRECTORY && errno == ENOENT) {
+-level = LOG_DEBUG;
+-r = 0;
+-}
+-
+-log_full_errno(level, errno, "Adjusting owner and mode for %s 
failed: %m", path);
++r = fd_get_path(fd, );
++if (r < 0)
+ return r;
+-}
+ 
+-if (fstatat(fd, "", , AT_EMPTY_PATH) < 0)
+-return log_error_errno(errno, "Failed to fstat() file %s: 
%m", 

[OE-core] [sumo][PATCH 5/8] systemd: Security fix CVE-2018-16865

[George McCollister]

Affects < v240

Based on thud commit d5d2b821fc85b8cf39f683061ac2a45bddd2139f
The second patch in the thud commit doesn't apply against 237. Use the
version of the second patch CVE-2018-16865_2.patch from
systemd_237-3ubuntu10.13.debian.

Signed-off-by: George McCollister 
---
 ...ld-set-a-limit-on-the-number-of-fields-1k.patch | 60 
 ...ote-set-a-limit-on-the-number-of-fields-i.patch | 79 ++
 meta/recipes-core/systemd/systemd_237.bb   |  2 +
 3 files changed, 141 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
 
b/meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
new file mode 100644
index 00..e8a6f2b986
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
@@ -0,0 +1,60 @@
+From 4566aaf97f5b4143b930d75628f3abc905249dcd Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= 
+Date: Wed, 5 Dec 2018 22:45:02 +0100
+Subject: [PATCH] journald: set a limit on the number of fields (1k)
+
+We allocate a iovec entry for each field, so with many short entries,
+our memory usage and processing time can be large, even with a relatively
+small message size. Let's refuse overly long entries.
+
+CVE-2018-16865
+https://bugzilla.redhat.com/show_bug.cgi?id=1653861
+
+What from I can see, the problem is not from an alloca, despite what the CVE
+description says, but from the attack multiplication that comes from creating
+many very small iovecs: (void* + size_t) for each three bytes of input message.
+
+Patch backported from systemd master at
+052c57f132f04a3cf4148f87561618da1a6908b4.
+
+CVE: CVE-2018-16865
+Upstream-Status: Backport
+
+---
+ src/basic/journal-importer.h  | 3 +++
+ src/journal/journald-native.c | 5 +
+ 2 files changed, 8 insertions(+)
+
+diff --git a/src/basic/journal-importer.h b/src/basic/journal-importer.h
+index f49ce734a1..c4ae45d32d 100644
+--- a/src/basic/journal-importer.h
 b/src/basic/journal-importer.h
+@@ -16,6 +16,9 @@
+ #define DATA_SIZE_MAX (1024*1024*768u)
+ #define LINE_CHUNK 8*1024u
+ 
++/* The maximum number of fields in an entry */
++#define ENTRY_FIELD_COUNT_MAX 1024
++
+ struct iovec_wrapper {
+ struct iovec *iovec;
+ size_t size_bytes;
+diff --git a/src/journal/journald-native.c b/src/journal/journald-native.c
+index 5ff22a10af..951d092053 100644
+--- a/src/journal/journald-native.c
 b/src/journal/journald-native.c
+@@ -140,6 +140,11 @@ static int server_process_entry(
+ }
+ 
+ /* A property follows */
++if (n > ENTRY_FIELD_COUNT_MAX) {
++log_debug("Received an entry that has more than " 
STRINGIFY(ENTRY_FIELD_COUNT_MAX) " fields, ignoring entry.");
++r = 1;
++goto finish;
++}
+ 
+ /* n existing properties, 1 new, +1 for _TRANSPORT */
+ if (!GREEDY_REALLOC(iovec, m,
+-- 
+2.11.0
+
diff --git 
a/meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
 
b/meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
new file mode 100644
index 00..f297333e72
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
@@ -0,0 +1,79 @@
+From ce1475b4f69f0a4382c6190f55e080d91de84611 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= 
+Date: Fri, 7 Dec 2018 10:48:10 +0100
+Subject: [PATCH] journal-remote: set a limit on the number of fields in a
+ message
+
+Existing use of E2BIG is replaced with ENOBUFS (entry too long), and E2BIG is
+reused for the new error condition (too many fields).
+
+This matches the change done for systemd-journald, hence forming the second
+part of the fix for CVE-2018-16865
+(https://bugzilla.redhat.com/show_bug.cgi?id=1653861).
+
+Patch backported from systemd master at
+ef4d6abe7c7fab6cbff975b32e76b09feee56074.
+
+Patch for 237 from:
+systemd_237-3ubuntu10.13.debian CVE-2018-16865_2.patch
+
+CVE: CVE-2018-16865
+Upstream-Status: Backport
+
+---
+ src/journal-remote/journal-remote-main.c | 7 +--
+ src/journal-remote/journal-remote.c  | 3 +++
+ src/shared/journal-importer.c| 5 -
+ 3 files changed, 12 insertions(+), 3 deletions(-)
+
+--- a/src/basic/journal-importer.c
 b/src/basic/journal-importer.c
+@@ -38,6 +38,9 @@
+ };
+ 
+ static int iovw_put(struct iovec_wrapper *iovw, void* data, size_t len) {
++if (iovw->count >= ENTRY_FIELD_COUNT_MAX)
++return -E2BIG;
++
+ 

[OE-core] [sumo][PATCH 6/8] systemd: Security fix CVE-2018-16866

[George McCollister]

From: Marcus Cooper 

Affects < v240

Signed-off-by: Marcus Cooper 

>From v2 patch on openembedded-core@lists.openembedded.org
Incresed file name number from 0026 to 0027.

Signed-off-by: George McCollister 
---
 ...nal-fix-out-of-bounds-read-CVE-2018-16866.patch | 49 ++
 meta/recipes-core/systemd/systemd_237.bb   |  1 +
 2 files changed, 50 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
 
b/meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
new file mode 100644
index 00..3925a4abbb
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
@@ -0,0 +1,49 @@
+From ebd06c37d4311db9851f4d3fdd023de3dd590de0 Mon Sep 17 00:00:00 2001
+From: Filipe Brandenburger 
+Date: Thu, 10 Jan 2019 14:53:33 -0800
+Subject: [PATCH] journal: fix out-of-bounds read CVE-2018-16866
+
+The original code didn't account for the fact that strchr() would match on the
+'\0' character, making it read past the end of the buffer if no non-whitespace
+character was present.
+
+This bug was introduced in commit ec5ff4445cca6a which was first released in
+systemd v221 and later fixed in commit 8595102d3ddde6 which was released in
+v240, so versions in the range [v221, v240) are affected.
+
+Patch backported from systemd-stable at 
f005e73d3723d62a39be661931fcb6347119b52b
+also includes a change from systemd master which removes a heap buffer overflow
+a6aadf4ae0bae185dc4c414d492a4a781c80ffe5.
+
+CVE: CVE-2018-16866
+Upstream-Status: Backport
+Signed-off-by: Marcus Cooper 
+---
+ src/journal/journald-syslog.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/journal/journald-syslog.c b/src/journal/journald-syslog.c
+index 9dea116722..809b318c06 100644
+--- a/src/journal/journald-syslog.c
 b/src/journal/journald-syslog.c
+@@ -194,7 +194,7 @@ size_t syslog_parse_identifier(const char **buf, char 
**identifier, char **pid)
+ e = l;
+ l--;
+ 
+-if (p[l-1] == ']') {
++if (l > 0 && p[l-1] == ']') {
+ size_t k = l-1;
+ 
+ for (;;) {
+@@ -219,7 +219,7 @@ size_t syslog_parse_identifier(const char **buf, char 
**identifier, char **pid)
+ if (t)
+ *identifier = t;
+ 
+-if (strchr(WHITESPACE, p[e]))
++if (p[e] != '\0' && strchr(WHITESPACE, p[e]))
+ e++;
+ *buf = p + e;
+ return e;
+-- 
+2.11.0
+
diff --git a/meta/recipes-core/systemd/systemd_237.bb 
b/meta/recipes-core/systemd/systemd_237.bb
index e6ef385f52..b53221896f 100644
--- a/meta/recipes-core/systemd/systemd_237.bb
+++ b/meta/recipes-core/systemd/systemd_237.bb
@@ -60,6 +60,7 @@ SRC_URI += "file://touchscreen.rules \

file://0024-journald-do-not-store-the-iovec-entry-for-process-co.patch \
file://0025-journald-set-a-limit-on-the-number-of-fields-1k.patch \

file://0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch \
+   file://0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch \
"
 SRC_URI_append_qemuall = " 
file://0001-core-device.c-Change-the-default-device-timeout-to-2.patch"
 
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [sumo][PATCH 3/8] systemd: fix CVE-2018-15688

[George McCollister]

From: Chen Qi 

Backport patch to fix the following CVE.

CVE: CVE-2018-15688

Signed-off-by: Chen Qi 
Signed-off-by: Richard Purdie 

Cherry-picked from thud 13591d7224393dc0ae529a03cdf74aceb3540ce9

Signed-off-by: George McCollister 
---
 ...sure-we-have-enough-space-for-the-DHCP6-o.patch | 39 ++
 meta/recipes-core/systemd/systemd_237.bb   |  1 +
 2 files changed, 40 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
 
b/meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
new file mode 100644
index 00..0c912f25df
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
@@ -0,0 +1,39 @@
+From a2622b8398ba026faf481f5eddeb53231d9de4a7 Mon Sep 17 00:00:00 2001
+From: Lennart Poettering 
+Date: Fri, 19 Oct 2018 12:12:33 +0200
+Subject: [PATCH] dhcp6: make sure we have enough space for the DHCP6 option
+ header
+
+Fixes a vulnerability originally discovered by Felix Wilhelm from
+Google.
+
+CVE-2018-15688
+LP: #1795921
+https://bugzilla.redhat.com/show_bug.cgi?id=1639067
+
+(cherry picked from commit 4dac5eaba4e419b29c97da38a8b1f82336c2c892)
+
+CVE: CVE-2018-15688
+Upstream-Status: Backport
+
+Signed-off-by: Chen Qi 
+---
+ src/libsystemd-network/dhcp6-option.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/libsystemd-network/dhcp6-option.c 
b/src/libsystemd-network/dhcp6-option.c
+index c4b402b..dcbaad0 100644
+--- a/src/libsystemd-network/dhcp6-option.c
 b/src/libsystemd-network/dhcp6-option.c
+@@ -103,7 +103,7 @@ int dhcp6_option_append_ia(uint8_t **buf, size_t *buflen, 
DHCP6IA *ia) {
+ return -EINVAL;
+ }
+ 
+-if (*buflen < len)
++if (*buflen < offsetof(DHCP6Option, data) + len)
+ return -ENOBUFS;
+ 
+ ia_hdr = *buf;
+-- 
+2.7.4
+
diff --git a/meta/recipes-core/systemd/systemd_237.bb 
b/meta/recipes-core/systemd/systemd_237.bb
index cae9bccc60..87793dd3af 100644
--- a/meta/recipes-core/systemd/systemd_237.bb
+++ b/meta/recipes-core/systemd/systemd_237.bb
@@ -56,6 +56,7 @@ SRC_URI += "file://touchscreen.rules \

file://0035-Define-glibc-compatible-basename-for-non-glibc-syste.patch \

file://0001-core-when-deserializing-state-always-use-read_line-L.patch \

file://0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch \
+   
file://0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch \
"
 SRC_URI_append_qemuall = " 
file://0001-core-device.c-Change-the-default-device-timeout-to-2.patch"
 
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [sumo][PATCH 4/8] systemd: Security fix CVE-2018-16864

[George McCollister]

Affects < v240

Based on thud commit 403e74b07b6f3c4a2444e68c74a8434fb17aee49
The patch in the thud commit doesn't compile against 237. Use the
version of this patch, CVE-2018-16864.patch from
systemd_237-3ubuntu10.13.debian.

Signed-off-by: George McCollister 
---
 ...-not-store-the-iovec-entry-for-process-co.patch | 193 +
 meta/recipes-core/systemd/systemd_237.bb   |   1 +
 2 files changed, 194 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
 
b/meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
new file mode 100644
index 00..c0b0667d85
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
@@ -0,0 +1,193 @@
+From c29b44cb90e2cc521533e6169cf847553ebefd81 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= 
+Date: Wed, 5 Dec 2018 18:38:39 +0100
+Subject: [PATCH] journald: do not store the iovec entry for process
+ commandline on stack
+
+This fixes a crash where we would read the commandline, whose length is under
+control of the sending program, and then crash when trying to create a stack
+allocation for it.
+
+CVE-2018-16864
+https://bugzilla.redhat.com/show_bug.cgi?id=1653855
+
+The message actually doesn't get written to disk, because
+journal_file_append_entry() returns -E2BIG.
+
+Patch for 237 from:
+systemd_237-3ubuntu10.13.debian CVE-2018-16864.patch
+
+CVE: CVE-2018-16864
+Upstream-Status: Backport
+
+---
+ src/basic/io-util.c   | 10 ++
+ src/basic/io-util.h   |  2 ++
+ src/coredump/coredump.c   | 31 +++
+ src/journal/journald-server.c | 25 +++--
+ 4 files changed, 38 insertions(+), 30 deletions(-)
+
+--- a/src/basic/io-util.c
 b/src/basic/io-util.c
+@@ -26,6 +26,7 @@
+ #include 
+ 
+ #include "io-util.h"
++#include "string-util.h"
+ #include "time-util.h"
+ 
+ int flush_fd(int fd) {
+@@ -270,3 +271,12 @@
+ 
+ return q - (const uint8_t*) p;
+ }
++
++char* set_iovec_string_field(struct iovec *iovec, size_t *n_iovec, const char 
*field, const char *value) {
++char *x;
++
++x = strappend(field, value);
++if (x)
++iovec[(*n_iovec)++] = IOVEC_MAKE_STRING(x);
++return x;
++}
+--- a/src/basic/io-util.h
 b/src/basic/io-util.h
+@@ -91,3 +91,5 @@
+ #define IOVEC_MAKE(base, len) (struct iovec) IOVEC_INIT(base, len)
+ #define IOVEC_INIT_STRING(string) IOVEC_INIT((char*) string, strlen(string))
+ #define IOVEC_MAKE_STRING(string) (struct iovec) IOVEC_INIT_STRING(string)
++
++char* set_iovec_string_field(struct iovec *iovec, size_t *n_iovec, const char 
*field, const char *value);
+--- a/src/coredump/coredump.c
 b/src/coredump/coredump.c
+@@ -1067,19 +1067,10 @@
+ return 0;
+ }
+ 
+-static char* set_iovec_field(struct iovec iovec[27], size_t *n_iovec, const 
char *field, const char *value) {
+-char *x;
+-
+-x = strappend(field, value);
+-if (x)
+-iovec[(*n_iovec)++] = IOVEC_MAKE_STRING(x);
+-return x;
+-}
+-
+ static char* set_iovec_field_free(struct iovec iovec[27], size_t *n_iovec, 
const char *field, char *value) {
+ char *x;
+ 
+-x = set_iovec_field(iovec, n_iovec, field, value);
++x = set_iovec_string_field(iovec, n_iovec, field, value);
+ free(value);
+ return x;
+ }
+@@ -1129,33 +1120,33 @@
+ disable_coredumps();
+ }
+ 
+-set_iovec_field(iovec, n_iovec, "COREDUMP_UNIT=", 
context[CONTEXT_UNIT]);
++set_iovec_string_field(iovec, n_iovec, "COREDUMP_UNIT=", 
context[CONTEXT_UNIT]);
+ }
+ 
+ if (cg_pid_get_user_unit(pid, ) >= 0)
+ set_iovec_field_free(iovec, n_iovec, "COREDUMP_USER_UNIT=", 
t);
+ 
+ /* The next few are mandatory */
+-if (!set_iovec_field(iovec, n_iovec, "COREDUMP_PID=", 
context[CONTEXT_PID]))
++if (!set_iovec_string_field(iovec, n_iovec, "COREDUMP_PID=", 
context[CONTEXT_PID]))
+ return log_oom();
+ 
+-if (!set_iovec_field(iovec, n_iovec, "COREDUMP_UID=", 
context[CONTEXT_UID]))
++if (!set_iovec_string_field(iovec, n_iovec, "COREDUMP_UID=", 
context[CONTEXT_UID]))
+ return log_oom();
+ 
+-if (!set_iovec_field(iovec, n_iovec, "COREDUMP_GID=", 
context[CONTEXT_GID]))
++if (!set_iovec_string_field(iovec, n_iovec, "COREDUMP_GID=", 
context[CONTEXT_GID]))
+ return log_oom();
+ 
+-if (!set_iovec_field(iovec, n_iovec, "COREDUMP_SIGNAL=", 
context[CONTEXT_SIGNAL]))
++if (!set_iovec_string_field(iovec, n_iovec, "COREDUMP_SIGNAL=", 
context[CONTEXT_SIGNAL]))
+ 

[OE-core] [sumo][PATCH 2/8] systemd: fix CVE-2018-15687

[George McCollister]

Backport patch to fix the following CVE.

CVE: CVE-2018-15687

Based on thud commit eeb621aa19f690971caf862290a172a115578ba1
The patch in the thud commit doesn't compile against 237. Use the
version of this patch,  CVE-2018-15687.patch from
systemd_237-3ubuntu10.13.debian.

Signed-off-by: George McCollister 
---
 ...sive-let-s-rework-the-recursive-logic-to-.patch | 252 +
 meta/recipes-core/systemd/systemd_237.bb   |   1 +
 2 files changed, 253 insertions(+)
 create mode 100644 
meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch

diff --git 
a/meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
 
b/meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
new file mode 100644
index 00..9a0b55f97d
--- /dev/null
+++ 
b/meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
@@ -0,0 +1,252 @@
+From 2da8ba3f507345d0401ea9d7191fa16ffa560ebc Mon Sep 17 00:00:00 2001
+From: Lennart Poettering 
+Date: Fri, 19 Oct 2018 11:26:59 +0200
+Subject: [PATCH] chown-recursive: let's rework the recursive logic to use
+ O_PATH
+
+That way we can pin a specific inode and analyze it and manipulate it
+without it being swapped out beneath our hands.
+
+Fixes a vulnerability originally found by Jann Horn from Google.
+
+CVE-2018-15687
+LP: #1796692
+https://bugzilla.redhat.com/show_bug.cgi?id=1639076
+
+Origin: upstream, 
https://github.com/poettering/systemd/commit/5de6cce58b3e8b79239b6e83653459d91af6e57c
+Bug-Ubuntu: https://launchpad.net/bugs/1796692
+
+Patch for 237 from:
+systemd_237-3ubuntu10.13.debian CVE-2018-15687.patch
+
+CVE: CVE-2018-15687
+Upstream-Status: Backport
+
+---
+ src/core/chown-recursive.c | 146 ++---
+ 1 file changed, 70 insertions(+), 76 deletions(-)
+
+diff --git a/src/core/chown-recursive.c b/src/core/chown-recursive.c
+index c479450..27c6448 100644
+--- a/src/core/chown-recursive.c
 b/src/core/chown-recursive.c
+@@ -18,18 +18,20 @@
+   along with systemd; If not, see .
+ ***/
+
+-#include 
+-#include 
+ #include 
++#include 
++#include 
+
+-#include "user-util.h"
+-#include "macro.h"
+-#include "fd-util.h"
+-#include "dirent-util.h"
+ #include "chown-recursive.h"
++#include "dirent-util.h"
++#include "fd-util.h"
++#include "macro.h"
++#include "stdio-util.h"
++#include "strv.h"
++#include "user-util.h"
+
+-static int chown_one(int fd, const char *name, const struct stat *st, uid_t 
uid, gid_t gid) {
+-int r;
++static int chown_one(int fd, const struct stat *st, uid_t uid, gid_t gid) {
++char procfs_path[STRLEN("/proc/self/fd/") + DECIMAL_STR_MAX(int) + 1];
+
+ assert(fd >= 0);
+ assert(st);
+@@ -38,90 +40,82 @@
+ (!gid_is_valid(gid) || st->st_gid == gid))
+ return 0;
+
+-if (name)
+-r = fchownat(fd, name, uid, gid, AT_SYMLINK_NOFOLLOW);
+-else
+-r = fchown(fd, uid, gid);
+-if (r < 0)
+-return -errno;
++/* We change ownership through the /proc/self/fd/%i path, so that we 
have a stable reference that works with
++ * O_PATH. (Note: fchown() and fchmod() do not work with O_PATH, the 
kernel refuses that. */
++xsprintf(procfs_path, "/proc/self/fd/%i", fd);
+
+-/* The linux kernel alters the mode in some cases of chown(). Let's 
undo this. */
+-if (name) {
+-if (!S_ISLNK(st->st_mode))
+-r = fchmodat(fd, name, st->st_mode, 0);
+-else /* There's currently no AT_SYMLINK_NOFOLLOW for 
fchmodat() */
+-r = 0;
+-} else
+-r = fchmod(fd, st->st_mode);
+-if (r < 0)
++if (chown(procfs_path, uid, gid) < 0)
+ return -errno;
+
++/* The linux kernel alters the mode in some cases of chown(). Let's 
undo this. We do this only for non-symlinks
++ * however. That's because for symlinks the access mode is ignored 
anyway and because on some kernels/file
++ * systems trying to change the access mode will succeed but has no 
effect while on others it actively
++ * fails. */
++if (!S_ISLNK(st->st_mode))
++if (chmod(procfs_path, st->st_mode & 0) < 0)
++return -errno;
++
+ return 1;
+ }
+
+ static int chown_recursive_internal(int fd, const struct stat *st, uid_t uid, 
gid_t gid) {
++_cleanup_closedir_ DIR *d = NULL;
+ bool changed = false;
++struct dirent *de;
+ int r;
+
+ assert(fd >= 0);
+ assert(st);
+
+-if (S_ISDIR(st->st_mode)) {
+-_cleanup_closedir_ DIR *d = NULL;
+-struct dirent *de;
+-
+-d = fdopendir(fd);
+-if (!d) {
+-  

[OE-core] [sumo][PATCH 8/8] systemd: fix CVE-2019-6454

[George McCollister]

Apply patches from systemd_237-3ubuntu10.13 to fix CVE-2019-6454.
CVE-2019-6454 is an issue in which systemd (PID1) can be crashed
with a specially formed D-Bus message.

For information see:
https://usn.ubuntu.com/3891-1/
https://git.launchpad.net/ubuntu/+source/systemd/commit/?h=applied/ubuntu/bionic-updates=d7584b894afcaa8a4a1abb69db2a9c81a6276e80

Signed-off-by: George McCollister 
---
 .../systemd/systemd/CVE-2019-6454.patch| 210 +
 ...e-receive-an-invalid-dbus-message-ignore-.patch |  61 ++
 meta/recipes-core/systemd/systemd_237.bb   |   2 +
 3 files changed, 273 insertions(+)
 create mode 100644 meta/recipes-core/systemd/systemd/CVE-2019-6454.patch
 create mode 100644 
meta/recipes-core/systemd/systemd/sd-bus-if-we-receive-an-invalid-dbus-message-ignore-.patch

diff --git a/meta/recipes-core/systemd/systemd/CVE-2019-6454.patch 
b/meta/recipes-core/systemd/systemd/CVE-2019-6454.patch
new file mode 100644
index 00..e3c67c166c
--- /dev/null
+++ b/meta/recipes-core/systemd/systemd/CVE-2019-6454.patch
@@ -0,0 +1,210 @@
+Description: sd-bus: enforce a size limit for dbus paths, and don't allocate
+ them on the stacka
+Forwarded: no
+
+Patch from: systemd_237-3ubuntu10.13
+
+For information see:
+https://usn.ubuntu.com/3891-1/
+https://git.launchpad.net/ubuntu/+source/systemd/commit/?h=applied/ubuntu/bionic-updates=d7584b894afcaa8a4a1abb69db2a9c81a6276e80
+
+CVE: CVE-2019-6454
+Upstream-Status: Backport
+
+Signed-off-by: George McCollister 
+
+--- a/src/libsystemd/sd-bus/bus-internal.c
 b/src/libsystemd/sd-bus/bus-internal.c
+@@ -61,7 +61,7 @@
+ if (slash)
+ return false;
+ 
+-return true;
++return (q - p) <= BUS_PATH_SIZE_MAX;
+ }
+ 
+ char* object_path_startswith(const char *a, const char *b) {
+--- a/src/libsystemd/sd-bus/bus-internal.h
 b/src/libsystemd/sd-bus/bus-internal.h
+@@ -339,6 +339,10 @@
+ 
+ #define BUS_MESSAGE_SIZE_MAX (64*1024*1024)
+ #define BUS_AUTH_SIZE_MAX (64*1024)
++/* Note that the D-Bus specification states that bus paths shall have no size 
limit. We enforce here one
++ * anyway, since truly unbounded strings are a security problem. The limit we 
pick is relatively large however,
++ * to not clash unnecessarily with real-life applications. */
++#define BUS_PATH_SIZE_MAX (64*1024)
+ 
+ #define BUS_CONTAINER_DEPTH 128
+ 
+--- a/src/libsystemd/sd-bus/bus-objects.c
 b/src/libsystemd/sd-bus/bus-objects.c
+@@ -1150,7 +1150,8 @@
+ const char *path,
+ sd_bus_error *error) {
+ 
+-char *prefix;
++_cleanup_free_ char *prefix = NULL;
++size_t pl;
+ int r;
+ 
+ assert(bus);
+@@ -1166,7 +1167,12 @@
+ return 0;
+ 
+ /* Second, add fallback vtables registered for any of the prefixes */
+-prefix = alloca(strlen(path) + 1);
++pl = strlen(path);
++assert(pl <= BUS_PATH_SIZE_MAX);
++prefix = new(char, pl + 1);
++if (!prefix)
++return -ENOMEM;
++
+ OBJECT_PATH_FOREACH_PREFIX(prefix, path) {
+ r = object_manager_serialize_path(bus, reply, prefix, path, 
true, error);
+ if (r < 0)
+@@ -1362,6 +1368,7 @@
+ }
+ 
+ int bus_process_object(sd_bus *bus, sd_bus_message *m) {
++_cleanup_free_ char *prefix = NULL;
+ int r;
+ size_t pl;
+ bool found_object = false;
+@@ -1386,9 +1393,12 @@
+ assert(m->member);
+ 
+ pl = strlen(m->path);
+-do {
+-char prefix[pl+1];
++assert(pl <= BUS_PATH_SIZE_MAX);
++prefix = new(char, pl + 1);
++if (!prefix)
++return -ENOMEM;
+ 
++do {
+ bus->nodes_modified = false;
+ 
+ r = object_find_and_run(bus, m, m->path, false, 
_object);
+@@ -1516,9 +1526,15 @@
+ 
+ n = hashmap_get(bus->nodes, path);
+ if (!n) {
+-char *prefix;
++_cleanup_free_ char *prefix = NULL;
++size_t pl;
++
++pl = strlen(path);
++assert(pl <= BUS_PATH_SIZE_MAX);
++prefix = new(char, pl + 1);
++if (!prefix)
++return -ENOMEM;
+ 
+-prefix = alloca(strlen(path) + 1);
+ OBJECT_PATH_FOREACH_PREFIX(prefix, path) {
+ n = hashmap_get(bus->nodes, prefix);
+ if (n)
+@@ -2108,8 +2124,9 @@
+ char **names) {
+ 
+ BUS_DONT_DESTROY(bus);
++_cleanup_free_ char *prefix = NULL;
+ bool found_interface = false;
+-char *prefix;
++size_t pl;
+ int r;
+ 
+ assert_return(bus, -EINVAL);
+@@ -2128,6 +2145,12 @@
+ if (names && names[0] == NULL)
+ return 0;
+ 
++pl = strlen(path);
++assert(pl <= BUS_PATH_SIZE_MAX);
++prefix = new(char, pl + 1);
++if 

Re: [OE-core] [PATCH] btrfs-tools Makefile: remove duplicated '-o $@' option from CC cmdline for libbtrfsutil/ subfolder

[Burton, Ross]

Please don't send patches in HTML  [1].  The patch you add is also
missing a Signed-off-by and Upstream-Status [2]  For such a trivial
build issue, we encourage submitting the patch upstream too so we
don't have to carry it forever.

[1] https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
[2] https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

On Fri, 22 Feb 2019 at 18:32, Ivan Efimov  wrote:
>
> Command line for target "libbtrfsutil/%.o" contained
> double usage of '-o $@' option and causes compilation error:
>
>  cc1: error: too many filenames given
>
> Signed-off-by: Ivan Efimov 
> ---
>  ...01-Makefile-fix-double-o-compiler-option-using.patch | 17 
> +
>  meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb |  1 +
>  2 files changed, 18 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-double-o-compiler-option-using.patch
>
> diff --git 
> a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-double-o-compiler-option-using.patch
>  b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-dou$
> le-o-compiler-option-using.patch
> new file mode 100644
> index 00..335067bc1f
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-double-o-compiler-option-using.patch
> @@ -0,0 +1,17 @@
> +Command line for target "libbtrfsutil/%.o" contained double usage
> +  of '-o $@' option and caused error:
> +cc1: error: too many filenames given
> +
> +Index: git/Makefile
> +===
> +--- git.orig/Makefile
>  git/Makefile
> +@@ -414,7 +414,7 @@ libbtrfs.so.0 libbtrfs.so: libbtrfs.so.0
> +
> + libbtrfsutil/%.o: libbtrfsutil/%.c
> +   @echo "[CC] $@"
> +-  $(Q)$(CC) $(LIBBTRFSUTIL_CFLAGS) -o $@ -c $< -o $@
> ++  $(Q)$(CC) $(LIBBTRFSUTIL_CFLAGS) -c $< -o $@
> +
> + libbtrfsutil.so.$(libbtrfsutil_version): $(libbtrfsutil_objects)
> +   @echo "[LD] $@"
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb 
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb
> index 1b4f515cb6..f1c4691313 100644
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb
> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb
> @@ -19,6 +19,7 @@ SRC_URI = 
> "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git \
> file://0001-Makefile-build-mktables-using-native-gcc.patch \
> file://0001-Add-LDFLAGS-when-building-libbtrfsutil.so.patch \
> 
> file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
> +   file://0001-Makefile-fix-double-o-compiler-option-using.patch \
> "
>
>  inherit autotools-brokensep pkgconfig manpages distutils3-base
> --
> 2.14.1
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] New QA process/tooling

[Richard Purdie]

I wanted to mention we now have a few developments working in our QA
process/tooling workflow. 

---
In summary:

We have buildhistory data comparing -next/mut builds to master:

https://autobuilder.yocto.io/pub/non-release/20190223-15/testresults/qemux86/buildhistory.txt

We have a summary of the test results (including ptest):

https://autobuilder.yocto.io/pub/non-release/20190223-15/testresults/testresult-report.txt

We have build performance reports:

https://autobuilder.yocto.io/pub/non-release/20190224-3/testresults/buildperf-centos7/perf-centos7.yoctoproject.org_master_20190224030033_47eb3d0.html

All this data is stored into git repos:
http://git.yoctoproject.org/cgit.cgi/poky-buildhistory/
http://git.yoctoproject.org/cgit.cgi/yocto-buildstats/
http://git.yoctoproject.org/cgit.cgi/yocto-testresults/

---
In detail:

Non-release builds publish some data to 
https://autobuilder.yocto.io/pub/non-release/MMDD-NN

e.g. https://autobuilder.yocto.io/pub/non-release/20190223-15

where NN is an incremented number for each build.

For the qemu machines, buildhistory is generated, stored in a git repo
and buildhistory-diff is run against it. For -next/mut builds this is
against master:

https://autobuilder.yocto.io/pub/non-release/20190223-15/testresults/qemux86/buildhistory.txt
https://autobuilder.yocto.io/pub/non-release/20190223-15/testresults/qemuarm/buildhistory.txt

(for master it would be against the last master build)

Historical data is saved into a git repo:

http://git.yoctoproject.org/cgit.cgi/poky-buildhistory/

(master-next and mut branches there will be force pushed)

The structure also contains various testresults.json files. resulttool
is used to find them all and import them into 
http://git.yoctoproject.org/cgit.cgi/yocto-testresults/ 

We then run resulttool report to generate:

https://autobuilder.yocto.io/pub/non-release/20190223-15/testresults/testresult-report.txt

and we also generate the regression report:

https://autobuilder.yocto.io/pub/non-release/20190223-15/testresults/testresult-regressions-report.txt

although right now this isn't working as well as I'd like (since the
previous build was a-quick, not an a-full and therefore there are missing 
components.

The test results report includes ptest data and includes data on how
long the ptests take to run and whether they timed out (a T in the time
column).

The build performance measurements are being run every 6 hours on two
performance measurement workers (ubuntu1604 and centos7) triggered from
the autobuilder. These generate the reports mentioned above as well as
pushing the results data into:

http://git.yoctoproject.org/cgit.cgi/yocto-buildstats/

build performance tests can be run against custom branches to test code
changes and then the report will be against the nearest commit in
master.

In a release build, the same data is generated but its published into:

https://autobuilder.yocto.io/pub/releases/

The hope is that these reports and data storage allow us to much more
accurately and easily figure out what was tested and whether/where we
have regressions.

It sounds relatively simple when put like this but there is a lot of
work that has gone into this by many people both past (Markus' work on
build performance or Paul on buildhistory) and present (Ee Peng on
resulttool). It is great to finally see it being pulled together into
something which is part of every build!

There are no doubt bugs and things to improve but believe this to be in
a good state for our 2.7 feature freeze.

Cheers,

Richard


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] oeqa/utils/gitarchive: Handle case where parent is only on origin

[Richard Purdie]

The parent code currently assumed that any parent branch is locally
checked out which may not be the case.

Use the local branch by default but fall back to the origin. This
also means removing the later saftey check as the branch may not exist
locally.

This fixes the autobuilder resulttool test pushing code.

Signed-off-by: Richard Purdie 
---
 meta/lib/oeqa/utils/gitarchive.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/utils/gitarchive.py 
b/meta/lib/oeqa/utils/gitarchive.py
index ff614d06bbf..9520b2e1261 100644
--- a/meta/lib/oeqa/utils/gitarchive.py
+++ b/meta/lib/oeqa/utils/gitarchive.py
@@ -80,6 +80,8 @@ def git_commit_data(repo, data_dir, branch, message, exclude, 
notes, log):
 
 # Create new commit object from the tree
 parent = repo.rev_parse(branch)
+if not parent:
+parent = repo.rev_parse("origin/" + branch)
 git_cmd = ['commit-tree', tree, '-m', message]
 if parent:
 git_cmd += ['-p', parent]
@@ -93,8 +95,6 @@ def git_commit_data(repo, data_dir, branch, message, exclude, 
notes, log):
 
 # Update branch head
 git_cmd = ['update-ref', 'refs/heads/' + branch, commit]
-if parent:
-git_cmd.append(parent)
 repo.run_cmd(git_cmd)
 
 # Update current HEAD, if we're on branch 'branch'
-- 
2.20.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 00/12] Enable accelerated OpenGL in qemu

[Richard Purdie]

On Fri, 2019-02-22 at 15:33 +0100, Alexander Kanavin wrote:
> V2 changes: addressed feedback from the first review round
> V3 changes:
> - better fix for missing qemu X11 include, as discussed with upstream
> - maintainers.inc entry for virglrenderer
> - egl-headless support (see below for details)
> - improvements to kmscube recipe
> - fix to vte-native to allow building it with gcc 4.8
> V4 changes
> - address failures uncovered by yocto autobuilder
> V5 changes
> - remove patches that have been merged to master
> - replace BBCLASSEXTEND_remove with PREFERRED_PROVIDER for mesa
> recipe variants
> V6 changes
> - again rebase to master
> - tweak oe-selftest to remove unnecessary re-builds of qemu-native
> V7 changes
> - rename virglrender_git.bb to virglrendender_0.7.0.bb
> - update the status of virglrenderer patches
> - further clarify the PACKAGECONFIG settings for qemu

There is a further problem somewhere. I ran more tests over the
weekend and fixed missing libEGL on ubuntu1604 for example. The 
debian8 worker is failing consistently:

https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/91

The log output is useless (which is a separate concern). When I try and
launch qemu manually I get the output below:

pokybuild@debian8-ty-1:~/yocto-worker/oe-selftest-debian/build$
DISPLAY=:1 /home/pokybuild/yocto-worker/oe-selftest-
debian/build/build/tmp/work/x86_64-linux/qemu-helper-native/1.0-
r1/recipe-sysroot-native/usr/bin/qemu-system-x86_64 -device virtio-net-
pci,netdev=net0,mac=52:54:00:12:34:02 -netdev
tap,id=net0,ifname=tap0,script=no,downscript=no -drive
file=/home/pokybuild/yocto-worker/oe-selftest-
debian/build/build/tmp/deploy/images/qemux86-64/core-image-minimal-
qemux86-64.ext4,if=virtio,format=raw -vga vmware -show-cursor -usb
-device usb-tablet -object rng-random,filename=/dev/urandom,id=rng0
-device virtio-rng-pci,rng=rng0  -vga virtio -display gtk,gl=on  -cpu
core2duo -enable-kvm -m 256 -serial tcp:127.0.0.1:51379  -serial
tcp:127.0.0.1:34855 -pidfile pidfile_9641 -snapshot -kernel
/home/pokybuild/yocto-worker/oe-selftest-
debian/build/build/tmp/deploy/images/qemux86-64/bzImage
--4.18.27+git0+9e348b6f9d_62f0a3acff-r0.2-qemux86-64-20190223080225.bin 
-append 'root=/dev/vda rw highres=off  mem=256M
ip=192.168.7.2::192.168.7.1:255.255.255.0 vga=0
uvesafb.mode_option=640x480-32 oprofile.timer=1 uvesafb.task_timeout=-1 
console=tty1 console=ttyS0,115200n8 printk.time=1'
libEGL warning: GLX/DRI2 is not supported

** (qemu-system-x86_64:10289): WARNING **: 09:43:00.199: Unknown X11
keycode mapping ''.
Please report to qemu-de...@nongnu.org
including the following information:

  - Operating system
  - X11 Server
  - xprop -root
  - xdpyinfo

qemu-system-x86_64: -serial tcp:127.0.0.1:51379: Failed to connect
socket: Connection refused
qemu-system-x86_64: -serial tcp:127.0.0.1:51379: could not connect
serial device to character backend 'tcp:127.0.0.1:51379'

Any ideas why this works everywhere else but not on debian8?

Cheers,

Richard

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 02/12] qemu: enable virglrenderer and glx options for native/nativesdk builds

[Richard Purdie]

On Fri, 2019-02-22 at 15:33 +0100, Alexander Kanavin wrote:
> Except for ming32/darwin, which do not support them.
> 
> Signed-off-by: Alexander Kanavin 
> ---
>  meta/recipes-devtools/qemu/qemu.inc | 10 +-
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-
> devtools/qemu/qemu.inc
> index c127434b020..95e9e0ede77 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -74,15 +74,15 @@ PACKAGECONFIG ??= " \
>  fdt sdl kvm \
>  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
>  "
> -PACKAGECONFIG_class-native ??= "fdt alsa kvm"
> -PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
> +PACKAGECONFIG_class-native ??= "fdt alsa kvm virglrenderer glx"
> +PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm virglrenderer glx"
>  
>  # Handle distros such as CentOS 5 32-bit that do not have kvm
> support
>  PACKAGECONFIG_class-native_remove = "${@'kvm' if not
> os.path.exists('/usr/include/linux/kvm.h') else ''}"
>  
> -# Disable kvm on targets that do not support it
> -PACKAGECONFIG_remove_darwin = "kvm"
> -PACKAGECONFIG_remove_mingw32 = "kvm"
> +# Disable kvm/virgl/mesa on targets that do not support it
> +PACKAGECONFIG_remove_darwin = "kvm virglrenderer glx gtk+"
> +PACKAGECONFIG_remove_mingw32 = "kvm virglrenderer glx gtk+"

Sorry, I just spotted this. Please don't use _remove in OE-Core. Can we
rearrange this so we don't need to use remove?

I appreciate there are other users that have crept in but I'd like to
see them gone too...

Cheers,

Richard


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 02/12] qemu: enable virglrenderer and glx options for native/nativesdk builds

[Alexander Kanavin]

On Mon, 25 Feb 2019 at 12:02, Richard Purdie
 wrote:
>
> On Fri, 2019-02-22 at 15:33 +0100, Alexander Kanavin wrote:
> > Except for ming32/darwin, which do not support them.
> >
> > Signed-off-by: Alexander Kanavin 
> > ---
> >  meta/recipes-devtools/qemu/qemu.inc | 10 +-
> >  1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-
> > devtools/qemu/qemu.inc
> > index c127434b020..95e9e0ede77 100644
> > --- a/meta/recipes-devtools/qemu/qemu.inc
> > +++ b/meta/recipes-devtools/qemu/qemu.inc
> > @@ -74,15 +74,15 @@ PACKAGECONFIG ??= " \
> >  fdt sdl kvm \
> >  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
> >  "
> > -PACKAGECONFIG_class-native ??= "fdt alsa kvm"
> > -PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
> > +PACKAGECONFIG_class-native ??= "fdt alsa kvm virglrenderer glx"
> > +PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm virglrenderer glx"
> >
> >  # Handle distros such as CentOS 5 32-bit that do not have kvm
> > support
> >  PACKAGECONFIG_class-native_remove = "${@'kvm' if not
> > os.path.exists('/usr/include/linux/kvm.h') else ''}"
> >
> > -# Disable kvm on targets that do not support it
> > -PACKAGECONFIG_remove_darwin = "kvm"
> > -PACKAGECONFIG_remove_mingw32 = "kvm"
> > +# Disable kvm/virgl/mesa on targets that do not support it
> > +PACKAGECONFIG_remove_darwin = "kvm virglrenderer glx gtk+"
> > +PACKAGECONFIG_remove_mingw32 = "kvm virglrenderer glx gtk+"
>
> Sorry, I just spotted this. Please don't use _remove in OE-Core. Can we
> rearrange this so we don't need to use remove?
>
> I appreciate there are other users that have crept in but I'd like to
> see them gone too...

I'm actually unsure how to override the
PACKAGECONFIG_append_pn-qemu-native = " gtk+"
set in local.conf without using _remove.

(we do not support gtk+ on mingw, and I guess darwin too).

We can rearrange this, enable/not enable gtk+ directly in the recipe,
and drop the qemu related lines from local.conf altogether, if you're
okay with that.

Alex
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] btrfs-tools Makefile: remove duplicated '-o $@' option from CC cmdline for libbtrfsutil/ subfolder

[Ivan Efimov]

Thank you for info about 
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

   I mistakenly followed guide 
https://wiki.yoctoproject.org/wiki/Poky_Contributions.

Best regards,
Ivan

- Original Message -
From: "Ross Burton" 
To: "Ivan Efimov" 
Cc: "OE-core" 
Sent: Monday, February 25, 2019 4:24:24 PM
Subject: Re: [OE-core] [PATCH] btrfs-tools Makefile: remove duplicated '-o $@' 
option from CC cmdline for libbtrfsutil/ subfolder

Please don't send patches in HTML  [1].  The patch you add is also
missing a Signed-off-by and Upstream-Status [2]  For such a trivial
build issue, we encourage submitting the patch upstream too so we
don't have to carry it forever.

[1] https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
[2] https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

On Fri, 22 Feb 2019 at 18:32, Ivan Efimov  wrote:
>
> Command line for target "libbtrfsutil/%.o" contained
> double usage of '-o $@' option and causes compilation error:
>
>  cc1: error: too many filenames given
>
> Signed-off-by: Ivan Efimov 
> ---
>  ...01-Makefile-fix-double-o-compiler-option-using.patch | 17 
> +
>  meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb |  1 +
>  2 files changed, 18 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-double-o-compiler-option-using.patch
>
> diff --git 
> a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-double-o-compiler-option-using.patch
>  b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-dou$
> le-o-compiler-option-using.patch
> new file mode 100644
> index 00..335067bc1f
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-fix-double-o-compiler-option-using.patch
> @@ -0,0 +1,17 @@
> +Command line for target "libbtrfsutil/%.o" contained double usage
> +  of '-o $@' option and caused error:
> +cc1: error: too many filenames given
> +
> +Index: git/Makefile
> +===
> +--- git.orig/Makefile
>  git/Makefile
> +@@ -414,7 +414,7 @@ libbtrfs.so.0 libbtrfs.so: libbtrfs.so.0
> +
> + libbtrfsutil/%.o: libbtrfsutil/%.c
> +   @echo "[CC] $@"
> +-  $(Q)$(CC) $(LIBBTRFSUTIL_CFLAGS) -o $@ -c $< -o $@
> ++  $(Q)$(CC) $(LIBBTRFSUTIL_CFLAGS) -c $< -o $@
> +
> + libbtrfsutil.so.$(libbtrfsutil_version): $(libbtrfsutil_objects)
> +   @echo "[LD] $@"
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb 
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb
> index 1b4f515cb6..f1c4691313 100644
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb
> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.20.1.bb
> @@ -19,6 +19,7 @@ SRC_URI = 
> "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git \
> file://0001-Makefile-build-mktables-using-native-gcc.patch \
> file://0001-Add-LDFLAGS-when-building-libbtrfsutil.so.patch \
> 
> file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
> +   file://0001-Makefile-fix-double-o-compiler-option-using.patch \
> "
>
>  inherit autotools-brokensep pkgconfig manpages distutils3-base
> --
> 2.14.1
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
[ https://inango.com/ |] 
Ivan Efimov 
Architect, Arch Group 
i.efi...@inango-systems.com 
T +7 343 298 0147 C +7 904 9 888 350 
[ https://inango.com/ | inango.com ] [ https://www.linkedin.com/company/inango ]
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 00/12] Enable accelerated OpenGL in qemu

[Alexander Kanavin]

On Mon, 25 Feb 2019 at 10:47, Richard Purdie
 wrote:
> libEGL warning: GLX/DRI2 is not supported

As a guess: Debian 8 has a particularly old version of mesa on the host:
https://packages.debian.org/source/jessie/mesa

I would start by installing a more recent one from jessie-backports repo:
https://packages.debian.org/source/jessie-backports/mesa

I also have to mention that Debian 8 is no longer in full support, but
in the 'LTS phase', which is described as:
'Debian LTS will not be handled by the Debian security team, but by a
separate group of volunteers and companies interested in making it a
success. '
https://wiki.debian.org/LTS/

Should we decommission the Debian 8 builders?

Alex
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] libpcre: upgrade to 8.43

[Ross Burton]

Licence checksum updated because the copyright dates were changed.

Signed-off-by: Ross Burton 
---
 meta/recipes-support/libpcre/{libpcre_8.42.bb => libpcre_8.43.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-support/libpcre/{libpcre_8.42.bb => libpcre_8.43.bb} (93%)

diff --git a/meta/recipes-support/libpcre/libpcre_8.42.bb 
b/meta/recipes-support/libpcre/libpcre_8.43.bb
similarity index 93%
rename from meta/recipes-support/libpcre/libpcre_8.42.bb
rename to meta/recipes-support/libpcre/libpcre_8.43.bb
index 3a488c00b71..d54b3941976 100644
--- a/meta/recipes-support/libpcre/libpcre_8.42.bb
+++ b/meta/recipes-support/libpcre/libpcre_8.43.bb
@@ -6,7 +6,7 @@ SUMMARY = "Perl Compatible Regular Expressions"
 HOMEPAGE = "http://www.pcre.org;
 SECTION = "devel"
 LICENSE = "BSD"
-LIC_FILES_CHKSUM = "file://LICENCE;md5=fc5026403b44c868c25fc9546f7feb05"
+LIC_FILES_CHKSUM = "file://LICENCE;md5=91bee59d1b327eb1599b4c673e2fb3d1"
 SRC_URI = "https://ftp.pcre.org/pub/pcre/pcre-${PV}.tar.bz2 \
file://pcre-cross.patch \
file://fix-pcre-name-collision.patch \
@@ -14,8 +14,8 @@ SRC_URI = "https://ftp.pcre.org/pub/pcre/pcre-${PV}.tar.bz2 \
file://Makefile \
 "
 
-SRC_URI[md5sum] = "085b6aa253e0f91cae70b3cdbe8c1ac2"
-SRC_URI[sha256sum] = 
"2cd04b7c887808be030254e8d77de11d3fe9d4505c39d4b15d2664ffe8bf9301"
+SRC_URI[md5sum] = "636222e79e392c3d95dcc545f24f98c4"
+SRC_URI[sha256sum] = 
"91e762520003013834ac1adb4a938d53b22a216341c061b0cf05603b290faf6b"
 
 CVE_PRODUCT = "pcre"
 
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [thud][PATCH 1/2] libaio: Extend to native

[Peter Kjellerstedt]

> -Original Message-
> From: akuster808 
> Sent: den 22 februari 2019 16:21
> To: Peter Kjellerstedt 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [thud][PATCH 1/2] libaio: Extend to native
> 
> On 2/22/19 3:00 AM, Peter Kjellerstedt wrote:
> > *ping*
> >
> > //Peter
> 
> you mean this?
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-
> extended/libaio?h=thud=40350b46d5c053b4336cc128922f44ce80e7da9a

No. That one extended the recipe to nativesdk, my patch extends it 
for native as well.

This is the one I want:

https://patchwork.openembedded.org/patch/157392/

//Peter

> >> -Original Message-
> >> From: openembedded-core-boun...@lists.openembedded.org
>  On Behalf Of Peter
> Kjellerstedt
> >> Sent: den 22 december 2018 23:13
> >> To: openembedded-core@lists.openembedded.org
> >> Subject: [OE-core] [thud][PATCH 1/2] libaio: Extend to native
> >>
> >> From: Peter Kjellerstedt 
> >>
> >> lvm2 currently requires libaio. So building lvm2-native will result
> in
> >> the following error.
> >>
> >>   ERROR: Required build target 'lvm2-native' has no buildable
> providers.
> >>   Missing or unbuildable dependency chain was: ['lvm2-native',
> 'libaio-native']
> >>
> >> Extend libaio to native to fix this issue.
> >>
> >> Signed-off-by: Peter Kjellerstedt 
> >> Signed-off-by: Richard Purdie 
> >> ---
> >>
> >> This is a backport from master.
> >>
> >>  meta/recipes-extended/libaio/libaio_0.3.111.bb | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/meta/recipes-extended/libaio/libaio_0.3.111.bb
> b/meta/recipes-extended/libaio/libaio_0.3.111.bb
> >> index 04b50b61ec..8e1cd349a0 100644
> >> --- a/meta/recipes-extended/libaio/libaio_0.3.111.bb
> >> +++ b/meta/recipes-extended/libaio/libaio_0.3.111.bb
> >> @@ -20,4 +20,4 @@ do_install () {
> >>  oe_runmake install DESTDIR=${D}
> >>  }
> >>
> >> -BBCLASSEXTEND = "nativesdk"
> >> +BBCLASSEXTEND = "native nativesdk"
> >> --
> >> 2.12.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] ltp: Bump to 20190115

[Daniel Díaz]

Hello!
On Sat, 23 Feb 2019 at 10:07, Richard Purdie
 wrote:
>
> On Thu, 2019-02-21 at 12:21 -0600, Daniel Díaz wrote:
> > This patch has been refreshed:
> > * 0008-Check-if-__GLIBC_PREREQ-is-defined-before-using-it.patch
> >
> > These patches have been dropped as they have been merged:
> > * 0001-netns_helper.sh-use-ping-6-when-ping6-is-not-avaliab.patch
> > * 0001-setrlimit05-Use-another-method-to-get-bad-address.patch
> > * 0001-sigwaitinfo01-recent-glibc-calls-syscall-directly.patch
> > * 0001-statx-fix-compile-errors.patch
> > * 0001-syscalls-fcntl-make-OFD-command-use-fcntl64-syscall-.patch
> > * 0001-getcpu01-Rename-getcpu-to-avoid-conflict-with-glibc-.patch
> >
> > This patch has been added:
> > * define-sigrtmin-and-sigrtmax-for-musl.patch
> >
> > Added these rdependencies:
> > * file: for ld01, file01 and logrotate
> > * quota: for quota_remount_test01
> >
> > Signed-off-by: Daniel Díaz 
>
> I think there was already a previous version of this upgrade which also
> didn't work:
>
> http://errors.yoctoproject.org/Errors/Latest/?filter=480efd388db578106a8a2129c0382b7e56a1ee36=commit=150
> From the -Wformat-security -Werror=format-security security flags.

I thought the problems were with MUSL and Glibc 2.29 (for which I
built). Let me look at these problems, then.

Thanks and greetings!

Daniel Díaz
daniel.d...@linaro.org
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] ltp: Bump to 20190115

[Richard Purdie]

On Mon, 2019-02-25 at 08:00 -0600, Daniel Díaz wrote:
> Hello!
> On Sat, 23 Feb 2019 at 10:07, Richard Purdie
>  wrote:
> > I think there was already a previous version of this upgrade which
> > also
> > didn't work:
> > 
> > http://errors.yoctoproject.org/Errors/Latest/?filter=480efd388db578106a8a2129c0382b7e56a1ee36=commit=150
> > From the -Wformat-security -Werror=format-security security flags.
> 
> I thought the problems were with MUSL and Glibc 2.29 (for which I
> built). Let me look at these problems, then.

Yes, thanks for looking at those.

For now I tweaked the recipe to disable the string security flags for
ltp as I wanted to get the upgrade in. As soon as we get a patchset
which builds, we can remove that workaround. I'm hoping we can get
something upstream for this too...

Cheers,

Richard

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 02/12] qemu: enable virglrenderer and glx options for native/nativesdk builds

[Khem Raj]

On Mon, Feb 25, 2019 at 4:52 AM Alexander Kanavin
 wrote:
>
> On Mon, 25 Feb 2019 at 12:02, Richard Purdie
>  wrote:
> >
> > On Fri, 2019-02-22 at 15:33 +0100, Alexander Kanavin wrote:
> > > Except for ming32/darwin, which do not support them.
> > >
> > > Signed-off-by: Alexander Kanavin 
> > > ---
> > >  meta/recipes-devtools/qemu/qemu.inc | 10 +-
> > >  1 file changed, 5 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-
> > > devtools/qemu/qemu.inc
> > > index c127434b020..95e9e0ede77 100644
> > > --- a/meta/recipes-devtools/qemu/qemu.inc
> > > +++ b/meta/recipes-devtools/qemu/qemu.inc
> > > @@ -74,15 +74,15 @@ PACKAGECONFIG ??= " \
> > >  fdt sdl kvm \
> > >  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
> > >  "
> > > -PACKAGECONFIG_class-native ??= "fdt alsa kvm"
> > > -PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
> > > +PACKAGECONFIG_class-native ??= "fdt alsa kvm virglrenderer glx"
> > > +PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm virglrenderer glx"
> > >
> > >  # Handle distros such as CentOS 5 32-bit that do not have kvm
> > > support
> > >  PACKAGECONFIG_class-native_remove = "${@'kvm' if not
> > > os.path.exists('/usr/include/linux/kvm.h') else ''}"
> > >
> > > -# Disable kvm on targets that do not support it
> > > -PACKAGECONFIG_remove_darwin = "kvm"
> > > -PACKAGECONFIG_remove_mingw32 = "kvm"
> > > +# Disable kvm/virgl/mesa on targets that do not support it
> > > +PACKAGECONFIG_remove_darwin = "kvm virglrenderer glx gtk+"
> > > +PACKAGECONFIG_remove_mingw32 = "kvm virglrenderer glx gtk+"
> >
> > Sorry, I just spotted this. Please don't use _remove in OE-Core. Can we
> > rearrange this so we don't need to use remove?
> >
> > I appreciate there are other users that have crept in but I'd like to
> > see them gone too...
>
> I'm actually unsure how to override the
> PACKAGECONFIG_append_pn-qemu-native = " gtk+"
> set in local.conf without using _remove.
>
> (we do not support gtk+ on mingw, and I guess darwin too).
>

iirc there are overrides for mingw which could be used in local.conf
to narrow this packageconfig setting

> We can rearrange this, enable/not enable gtk+ directly in the recipe,
> and drop the qemu related lines from local.conf altogether, if you're
> okay with that.
>
> Alex
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 02/12] qemu: enable virglrenderer and glx options for native/nativesdk builds

[Richard Purdie]

On Mon, 2019-02-25 at 09:29 -0600, Joshua Watt wrote:
> On Mon, 2019-02-25 at 13:52 +0100, Alexander Kanavin wrote:
> > On Mon, 25 Feb 2019 at 12:02, Richard Purdie
> >  wrote:
> > > On Fri, 2019-02-22 at 15:33 +0100, Alexander Kanavin wrote:
> > > > Except for ming32/darwin, which do not support them.
> > > > 
> > > > Signed-off-by: Alexander Kanavin 
> > > > ---
> > > >  meta/recipes-devtools/qemu/qemu.inc | 10 +-
> > > >  1 file changed, 5 insertions(+), 5 deletions(-)
> > > > 
> > > > diff --git a/meta/recipes-devtools/qemu/qemu.inc
> > > > b/meta/recipes-
> > > > devtools/qemu/qemu.inc
> > > > index c127434b020..95e9e0ede77 100644
> > > > --- a/meta/recipes-devtools/qemu/qemu.inc
> > > > +++ b/meta/recipes-devtools/qemu/qemu.inc
> > > > @@ -74,15 +74,15 @@ PACKAGECONFIG ??= " \
> > > >  fdt sdl kvm \
> > > >  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
> > > >  "
> > > > -PACKAGECONFIG_class-native ??= "fdt alsa kvm"
> > > > -PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
> > > > +PACKAGECONFIG_class-native ??= "fdt alsa kvm virglrenderer
> > > > glx"
> > > > +PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm virglrenderer
> > > > glx"
> > > > 
> > > >  # Handle distros such as CentOS 5 32-bit that do not have kvm
> > > > support
> > > >  PACKAGECONFIG_class-native_remove = "${@'kvm' if not
> > > > os.path.exists('/usr/include/linux/kvm.h') else ''}"
> > > > 
> > > > -# Disable kvm on targets that do not support it
> > > > -PACKAGECONFIG_remove_darwin = "kvm"
> > > > -PACKAGECONFIG_remove_mingw32 = "kvm"
> > > > +# Disable kvm/virgl/mesa on targets that do not support it
> > > > +PACKAGECONFIG_remove_darwin = "kvm virglrenderer glx gtk+"
> > > > +PACKAGECONFIG_remove_mingw32 = "kvm virglrenderer glx gtk+"
> > > 
> > > Sorry, I just spotted this. Please don't use _remove in OE-Core.
> > > Can we
> > > rearrange this so we don't need to use remove?
> > > 
> > > I appreciate there are other users that have crept in but I'd
> > > like
> > > to
> > > see them gone too...
> > 
> > I'm actually unsure how to override the
> > PACKAGECONFIG_append_pn-qemu-native = " gtk+"
> > set in local.conf without using _remove.
> 
> I don't think I quite follow why this is an issue, mingw is not a
> supported build host AFAIK, so the "-native" means it shouldn't be a
> problem (e.g. "native" should never mean "mingw")? Not sure about
> darwin though.

I wasn't quite seeing this either at first. native isn't the problem,
its the nativesdk variant...

Cheers,

Richard

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] alsa-tools: 1.1.6 -> 1.1.7

[Tanu Kaskinen]

Changelog:
http://alsa-project.org/main/index.php/Changes_v1.1.6_v1.1.7

The two patches have now been upstreamed. Apart from those changes, the
only thing that changed was the hwmixvolume tool, which got ported from
PyGTK to PyGObject, and from GTK 2 to GTK 3.

When testing hwmixvolume, I found that it depends on pyalsa, which has
not been packaged for OE. I believe hwmixvolume has never worked on OE.
It certainly didn't work before this patch, trying to build it failed
due to python-pygtk not being available. Even if python-pygtk was
available at some point in the past, hwmixvolume has always used pyalsa,
but the alsa-tools recipe has never had that dependency declared.

Signed-off-by: Tanu Kaskinen 
---
 ...served-user-defined-literal-warnings.patch | 34 --
 .../alsa/alsa-tools/musl.patch| 47 ---
 ...lsa-tools_1.1.6.bb => alsa-tools_1.1.7.bb} | 14 +++---
 3 files changed, 7 insertions(+), 88 deletions(-)
 delete mode 100644 
meta/recipes-multimedia/alsa/alsa-tools/0002-Fix-clang-Wreserved-user-defined-literal-warnings.patch
 delete mode 100644 meta/recipes-multimedia/alsa/alsa-tools/musl.patch
 rename meta/recipes-multimedia/alsa/{alsa-tools_1.1.6.bb => 
alsa-tools_1.1.7.bb} (90%)

diff --git 
a/meta/recipes-multimedia/alsa/alsa-tools/0002-Fix-clang-Wreserved-user-defined-literal-warnings.patch
 
b/meta/recipes-multimedia/alsa/alsa-tools/0002-Fix-clang-Wreserved-user-defined-literal-warnings.patch
deleted file mode 100644
index c137bc8a28..00
--- 
a/meta/recipes-multimedia/alsa/alsa-tools/0002-Fix-clang-Wreserved-user-defined-literal-warnings.patch
+++ /dev/null
@@ -1,34 +0,0 @@
-Upstream-Status: Backport
-Signed-off-by: Khem Raj 
-
-From a861bdabf02cd9bfb3ec7c0571c563c0fa14adfb Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Tue, 24 Apr 2018 12:24:32 -0700
-Subject: [PATCH] us428control: Fix clang -Wreserved-user-defined-literal
- warnings
-
-| us428control.cc:66:18: error: invalid suffix on literal; C++11 requires a 
space between literal and identifier [-Wreserved-user-defined-literal]
-| printf("usage: "PROGNAME" [-v verbosity_level 0..2] [-c card] [-D 
device] [-u usb-device] [-m mode]\n");
-| ^
-
-Signed-off-by: Khem Raj 
-Signed-off-by: Takashi Iwai 

- us428control/us428control.cc | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/us428control/us428control.cc b/us428control/us428control.cc
-index e839bf4..8cb3c42 100644
 a/us428control/us428control.cc
-+++ b/us428control/us428control.cc
-@@ -63,7 +63,7 @@ static void usage(void)
- {
-   printf("Tascam US-428 Control\n");
-   printf("version %s\n", VERSION);
--  printf("usage: "PROGNAME" [-v verbosity_level 0..2] [-c card] [-D 
device] [-u usb-device] [-m mode]\n");
-+  printf("usage: " PROGNAME " [-v verbosity_level 0..2] [-c card] [-D 
device] [-u usb-device] [-m mode]\n");
-   printf("mode is one of (us224, us428, mixxx)\n");
- }
- /*
--- 
-1.7.11.7
diff --git a/meta/recipes-multimedia/alsa/alsa-tools/musl.patch 
b/meta/recipes-multimedia/alsa/alsa-tools/musl.patch
deleted file mode 100644
index 9eb129c379..00
--- a/meta/recipes-multimedia/alsa/alsa-tools/musl.patch
+++ /dev/null
@@ -1,47 +0,0 @@
-Upstream-Status: Backport
-Signed-off-by: Ross Burton 
-
-From 235d9c5e8381518b0a8661786e7e0cbdd1bbcd01 Mon Sep 17 00:00:00 2001
-From: Ross Burton 
-Date: Tue, 12 Jun 2018 13:24:34 +0100
-Subject: [PATCH] ld10k1: define _GNU_SOURCE and use sighandler_t
-
-__sighandler_t is a glibc internal type which doesn't exist in musl.  By using
-AC_USE_SYSTEM_EXTENSIONS to get _GNU_SOURCE defined, both glibc and musl
-then expose sighandler_t.
-
-Signed-off-by: Ross Burton 
-Signed-off-by: Takashi Iwai 

- ld10k1/configure.ac  | 1 +
- ld10k1/src/ld10k1_fnc1.c | 2 +-
- 2 files changed, 2 insertions(+), 1 deletion(-)
-
-diff --git a/ld10k1/configure.ac b/ld10k1/configure.ac
-index 276b24e..f48ca31 100644
 a/ld10k1/configure.ac
-+++ b/ld10k1/configure.ac
-@@ -4,6 +4,7 @@ AC_CONFIG_MACRO_DIR([m4])
- AM_MAINTAINER_MODE([enable])
- 
- AC_CONFIG_HEADERS(config.h)
-+AC_USE_SYSTEM_EXTENSIONS
- AC_PROG_CC
- AC_PROG_LD
- AC_PROG_INSTALL
-diff --git a/ld10k1/src/ld10k1_fnc1.c b/ld10k1/src/ld10k1_fnc1.c
-index 343584c..ddc43c6 100644
 a/ld10k1/src/ld10k1_fnc1.c
-+++ b/ld10k1/src/ld10k1_fnc1.c
-@@ -179,7 +179,7 @@ int main_loop(comm_param *param, int audigy, const char 
*card_id, int tram_size,
- {
-   fd_set active_fd_set/*, read_fd_set*/;
-   int i, j, res = 0;
--  __sighandler_t old_sig_pipe;
-+  sighandler_t old_sig_pipe;
- 
-   int main_sock = 0;
-   int data_sock = 0;
--- 
-2.11.0
-
diff --git a/meta/recipes-multimedia/alsa/alsa-tools_1.1.6.bb 
b/meta/recipes-multimedia/alsa/alsa-tools_1.1.7.bb
similarity index 90%
rename from meta/recipes-multimedia/alsa/alsa-tools_1.1.6.bb
rename to meta/recipes-multimedia/alsa/alsa-tools_1.1.7.bb
index 0662b5a78d..e1b50fac52 100644
--- 

Re: [OE-core] [PATCH 02/12] qemu: enable virglrenderer and glx options for native/nativesdk builds

[Joshua Watt]

On Mon, 2019-02-25 at 13:52 +0100, Alexander Kanavin wrote:
> On Mon, 25 Feb 2019 at 12:02, Richard Purdie
>  wrote:
> > On Fri, 2019-02-22 at 15:33 +0100, Alexander Kanavin wrote:
> > > Except for ming32/darwin, which do not support them.
> > > 
> > > Signed-off-by: Alexander Kanavin 
> > > ---
> > >  meta/recipes-devtools/qemu/qemu.inc | 10 +-
> > >  1 file changed, 5 insertions(+), 5 deletions(-)
> > > 
> > > diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-
> > > devtools/qemu/qemu.inc
> > > index c127434b020..95e9e0ede77 100644
> > > --- a/meta/recipes-devtools/qemu/qemu.inc
> > > +++ b/meta/recipes-devtools/qemu/qemu.inc
> > > @@ -74,15 +74,15 @@ PACKAGECONFIG ??= " \
> > >  fdt sdl kvm \
> > >  ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
> > >  "
> > > -PACKAGECONFIG_class-native ??= "fdt alsa kvm"
> > > -PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
> > > +PACKAGECONFIG_class-native ??= "fdt alsa kvm virglrenderer glx"
> > > +PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm virglrenderer
> > > glx"
> > > 
> > >  # Handle distros such as CentOS 5 32-bit that do not have kvm
> > > support
> > >  PACKAGECONFIG_class-native_remove = "${@'kvm' if not
> > > os.path.exists('/usr/include/linux/kvm.h') else ''}"
> > > 
> > > -# Disable kvm on targets that do not support it
> > > -PACKAGECONFIG_remove_darwin = "kvm"
> > > -PACKAGECONFIG_remove_mingw32 = "kvm"
> > > +# Disable kvm/virgl/mesa on targets that do not support it
> > > +PACKAGECONFIG_remove_darwin = "kvm virglrenderer glx gtk+"
> > > +PACKAGECONFIG_remove_mingw32 = "kvm virglrenderer glx gtk+"
> > 
> > Sorry, I just spotted this. Please don't use _remove in OE-Core.
> > Can we
> > rearrange this so we don't need to use remove?
> > 
> > I appreciate there are other users that have crept in but I'd like
> > to
> > see them gone too...
> 
> I'm actually unsure how to override the
> PACKAGECONFIG_append_pn-qemu-native = " gtk+"
> set in local.conf without using _remove.

I don't think I quite follow why this is an issue, mingw is not a
supported build host AFAIK, so the "-native" means it shouldn't be a
problem (e.g. "native" should never mean "mingw")? Not sure about
darwin though.

> 
> (we do not support gtk+ on mingw, and I guess darwin too).
> 
> We can rearrange this, enable/not enable gtk+ directly in the recipe,
> and drop the qemu related lines from local.conf altogether, if you're
> okay with that.
> 
> Alex
-- 
Joshua Watt 

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core