Re: [OE-core] [PATCH 06/10] mc: upgrade to 4.8.16

On Tue, 03 May 2016 19:45:57 Maxin B. John wrote: > On Tue, May 03, 2016 at 06:41:01PM +0200, Martin Jansa wrote: > > On Tue, May 03, 2016 at 05:49:45PM +0300, Maxin B. John wrote: > > > 4.8.15 -> 4.8.16 > > > > Can you please use -M when sending the patches, it's much easier to > > review. > >

[OE-core] [master][krogoth][PATCH] openssl: Security fix via update to 1.0.2h

From: Armin Kuster <akus...@mvista.com> CVE-2016-2105 CVE-2016-2106 CVE-2016-2109 CVE-2016-2176 https://www.openssl.org/news/secadv/20160503.txt fixup openssl-avoid-NULL-pointer-dereference-in-EVP_DigestInit_ex.patch drop crypto_use_bigint_in_x86-64_perl.patch as that fix is in latest.

Re: [OE-core] [PATCH v3 0/6] bmaptool support

On Mon, May 2, 2016 at 12:22 PM, Ed Bartosh wrote: > Hi, > > This patchset adds ability to use bmaptool to flash images faster than > using traditional methods. It contains bmap-tools recipe and generation > of .bmap files for the images generated by bitbake and wic.

[OE-core] [PATCH] image-live.bbclass: make the INITRD optional

From: Christopher Larson This aligns with image-vm, and makes sense for wic bootimg-efi images, which don't actually want any of the live installer bits. Signed-off-by: Christopher Larson --- meta/classes/image-live.bbclass | 2 +- 1 file

Re: [OE-core] clarifying details about "is not set" lines in kernel config fragment files

On Tue, 3 May 2016, Denys Dmytriyenko wrote: > On Tue, May 03, 2016 at 02:27:38PM -0400, Robert P. J. Day wrote: > > On Tue, 3 May 2016, Bruce Ashfield wrote: > > > > > On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day > > > wrote: > > > > > >   oddly, in the current

Re: [OE-core] clarifying details about "is not set" lines in kernel config fragment files

On Tue, 3 May 2016, Tom Rini wrote: > On Tue, May 03, 2016 at 02:27:38PM -0400, Robert P. J. Day wrote: > > On Tue, 3 May 2016, Bruce Ashfield wrote: > > > > > On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day > > > wrote: > > > > > >   oddly, in the current YP

[OE-core] [oe-core PATCH v2 3/7] weston-init: Rework do_install to use install -D option

The install -D allow for the parent directories to be created in a single command line, reducing the code and number of fork during the build. Signed-off-by: Otavio Salvador --- Changes in v2: None meta/recipes-graphics/wayland/weston-init.bb | 7 ++- 1 file

[OE-core] [oe-core PATCH v2 5/7] weston-init: Error out if loading a nested instance

The Weston nested instance support is not implemented. This errors out displaying an informative error message so someone insterested on it may look at implement this later. Signed-off-by: Otavio Salvador --- Changes in v2: None

[OE-core] [oe-core PATCH v2 6/7] weston-init: Add module support for the weston-start helper

To make weston-start more flexible we now support module loading. For such modules, following functions can be used: - add_weston_argument - add_openvt_argument Signed-off-by: Otavio Salvador --- Changes in v2: - Drop weston-lunch use as it requires PAM

[OE-core] [oe-core PATCH v2 7/7] weston: Add Xwayland initialization support using weston-start

The weston-start script now supports loading modules so the Xwayland support can be loaded optionally. Use this to load Weston accordingly. Signed-off-by: Otavio Salvador --- Changes in v2: - Move weston-start module to weston package - Stop using weston-launch

[OE-core] [oe-core PATCH v2 4/7] weston-init: Rework init sequence to avoid code duplication

The new 'weston-start' script redcues the code duplication for SysV and SystemD based images. Signed-off-by: Otavio Salvador --- Changes in v2: None meta/recipes-graphics/wayland/weston-init.bb | 4 ++- meta/recipes-graphics/wayland/weston-init/init | 9

[OE-core] [oe-core PATCH v2 2/7] weston: Remove XWayland dependencies on PACKAGECONFIG

Instead of adding partial dependencies we list the PACKAGECONFIG options that are required. Those are: X11 and Wayland. The previous value were redudant with X11 PACKAGECONFIG option and as it is a requirement, for XWayland, it can be removed to easy maintenance. Signed-off-by: Otavio Salvador

[OE-core] [oe-core PATCH v2 1/7] weston: Enable XWayland when X11 and Wayland support are available

When the DISTRO has X11 and Wayland support enabled, XWayland ought to be enabled by default. Signed-off-by: Otavio Salvador --- Changes in v2: - Remove PAM requirement meta/recipes-graphics/wayland/weston_1.9.0.bb | 1 + 1 file changed, 1 insertion(+) diff --git

[OE-core] [oe-core PATCH v2 0/7] Improve Xwayland integration

Up to now, to make Xwayland to work it required several manual hacks and it was difficult to make an image which had support for it out of box. This patchset intends to set the base for it. It enables weston-init to be extended to support Xwayland launch when needed. There are still some issues

Re: [OE-core] [PATCH v3 4/6] bmap-tools: generate standalone script

On Tue, May 3, 2016 at 7:31 PM, Christopher Larson wrote: > > > On Mon, May 2, 2016 at 12:22 PM, Ed Bartosh > wrote: > >> Generated standalone bmaptool script that is more convenient >> to use than native script. It can be run straight from >>

Re: [OE-core] [PATCH v3 4/6] bmap-tools: generate standalone script

On Mon, May 2, 2016 at 12:22 PM, Ed Bartosh wrote: > Generated standalone bmaptool script that is more convenient > to use than native script. It can be run straight from > its location ./tmp/deploy/tools/bmaptool. The script doesn't > depend on anything except

Re: [OE-core] clarifying details about "is not set" lines in kernel config fragment files

On Tue, May 03, 2016 at 02:27:38PM -0400, Robert P. J. Day wrote: > On Tue, 3 May 2016, Bruce Ashfield wrote: > > > On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day > > wrote: > > > >   oddly, in the current YP kernel dev manual, i don't see the > > phrase "is

Re: [OE-core] clarifying details about "is not set" lines in kernel config fragment files

On Tue, May 3, 2016 at 2:27 PM, Robert P. J. Day wrote: > On Tue, 3 May 2016, Bruce Ashfield wrote: > > > On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day > wrote: > > > > oddly, in the current YP kernel dev manual, i don't see the > >

Re: [OE-core] clarifying details about "is not set" lines in kernel config fragment files

On Tue, May 03, 2016 at 02:27:38PM -0400, Robert P. J. Day wrote: > On Tue, 3 May 2016, Bruce Ashfield wrote: > > > On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day > > wrote: > > > >   oddly, in the current YP kernel dev manual, i don't see the > > phrase "is

Re: [OE-core] clarifying details about "is not set" lines in kernel config fragment files

On Tue, 3 May 2016, Bruce Ashfield wrote: > On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day > wrote: > >   oddly, in the current YP kernel dev manual, i don't see the > phrase "is not set" explained anywhere in the entire doc, > which is weird since it

Re: [OE-core] [master][PATCH] gcc-cross{, -canadian}: remove --with-linker-hash-style

On Tue, May 03, 2016 at 10:09:13AM +0200, Martin Jansa wrote: > On Mon, May 02, 2016 at 02:37:43PM -0700, Khem Raj wrote: > > > > > On May 2, 2016, at 1:37 PM, Christopher Larson wrote: > > > > > > > > > > > > On Mon, May 2, 2016 at 8:34 PM, Khem Raj

Re: [OE-core] clarifying details about "is not set" lines in kernel config fragment files

On Tue, May 3, 2016 at 1:04 PM, Robert P. J. Day wrote: > > oddly, in the current YP kernel dev manual, i don't see the phrase > "is not set" explained anywhere in the entire doc, which is weird > since it seems like it would be important. > The manuals don't cover the

[OE-core] clarifying details about "is not set" lines in kernel config fragment files

oddly, in the current YP kernel dev manual, i don't see the phrase "is not set" explained anywhere in the entire doc, which is weird since it seems like it would be important. first, just to confirm *i* know what it's used for, it's not just a comment -- it's used explicitly by the kernel

Re: [OE-core] [PATCH 06/10] mc: upgrade to 4.8.16

Hi Martin, On Tue, May 03, 2016 at 06:41:01PM +0200, Martin Jansa wrote: > On Tue, May 03, 2016 at 05:49:45PM +0300, Maxin B. John wrote: > > 4.8.15 -> 4.8.16 > > Can you please use -M when sending the patches, it's much easier to > review. > Thanks. Noticed it after sending the patch. Sorry for

Re: [OE-core] [PATCH 06/10] mc: upgrade to 4.8.16

On Tue, May 03, 2016 at 05:49:45PM +0300, Maxin B. John wrote: > 4.8.15 -> 4.8.16 Can you please use -M when sending the patches, it's much easier to review. > Signed-off-by: Maxin B. John > --- > meta/recipes-extended/mc/mc_4.8.15.bb | 49 >

[OE-core] npm class usage

Hi all! I'm trying to install some recipes that use npm class and I have two questions. 1 - Why use S = "${WORKDIR}/npmpkg"? This not work for me. 2 - Using option --no-registry inside npm_do_compile task I get this error: | npm ERR! Registry not defined and registry files not found:

Re: [OE-core] [master][PATCH] gcc-cross{, -canadian}: remove --with-linker-hash-style

On Tue, May 3, 2016 at 9:11 AM, Anders Darander wrote: > * Martin Jansa [160503 10:08]: > > > It would be nice to really poison the value if possible > > --with-linker-hash-style=YOU_NEED_TO_RESPECT_LDFLAGS > > to cause linker call to fail when

Re: [OE-core] [PATCH] lib/oe/rootfs: Fix DEBUGFS generation when using opkg

On 05/03/2016 02:49 AM, Patrick Ohly wrote: > But how does opkg know that "config file not present" is an error? It > depends on the the semantic of the file and thus the package providing > the file. It's not declared explicitly, so it is a fairly arbitrary > judgment call to treat "missing" as

Re: [OE-core] how can i tell which default kernel config OE started with?

On Tue, 3 May 2016, Bruce Ashfield wrote: > On Tue, May 3, 2016 at 11:13 AM, Robert P. J. Day > wrote: > >   also, that same section in the YP manual is slightly > confusing -- if your SRC_URI refers to a defconfig file *and* > some .cfg fragment files,

Re: [OE-core] how can i tell which default kernel config OE started with?

On Tue, May 3, 2016 at 11:13 AM, Robert P. J. Day wrote: > On Tue, 3 May 2016, Bruce Ashfield wrote: > > > If you are not supplying a defconfig, and are inheriting the > > standard kernel options, then yes, you'd be getting those fragments > > as well. > > ah, this

Re: [OE-core] [meta-oe]: Run time dependencies(i.e. Python package/modules) are not mentioned in dstat recipe

On Tue, May 3, 2016 at 1:48 PM, mubin syed wrote: > Hi, > > I am beginner to the yocto recipes. > > I have following observation regarding dstat recipe, > > 1. dstat utility requires some python modules during it's execution(i.e. > run time dependencies). > 2. As per my

Re: [OE-core] [PATCH] image_types.bbclass: add WIC_CREATE_EXTRA_ARGS

On Tue, May 3, 2016 at 7:27 AM, Ed Bartosh wrote: > Hi Christopher, > > Thank you for the patch! I like the idea. > > Would you mind adding or modifying wic oe-selftest to cover this? > > Signed-off-by: Ed Bartosh > > PS: You've mentioned

Re: [OE-core] how can i tell which default kernel config OE started with?

On Tue, 3 May 2016, Bruce Ashfield wrote: > If you are not supplying a defconfig, and are inheriting the > standard kernel options, then yes, you'd be getting those fragments > as well. ah, this actually leads me into my next question -- what is magic about a "defconfig" file that changes the

[OE-core] [PATCH 10/10] iproute2: upgrade to version 4.5.0

4.4.0 -> 4.5.0 Refreshed iproute2 musl build fix patch for 4.5.0 Remove backported patch: iproute2-fix-building-with-musl.patch Signed-off-by: Maxin B. John --- .../iproute2/iproute2/iproute2-4.3.0-musl.patch| 97 +-

[OE-core] [PATCH 08/10] harfbuzz: upgrade to 1.2.6

1.2.3 -> 1.2.6 Signed-off-by: Maxin B. John --- meta/recipes-graphics/harfbuzz/harfbuzz_1.2.3.bb | 39 meta/recipes-graphics/harfbuzz/harfbuzz_1.2.6.bb | 39 2 files changed, 39 insertions(+), 39 deletions(-) delete mode

[OE-core] [PATCH 06/10] mc: upgrade to 4.8.16

4.8.15 -> 4.8.16 Signed-off-by: Maxin B. John --- meta/recipes-extended/mc/mc_4.8.15.bb | 49 --- meta/recipes-extended/mc/mc_4.8.16.bb | 49 +++ 2 files changed, 49 insertions(+), 49 deletions(-) delete mode

[OE-core] [PATCH 00/10] package version upgrades

Here are the initial list of package upgrades: Maxin B. John (10): acpid: upgrade to 2.0.27 ethtool: upgrade to 4.5 pkgconfig: update to version 0.29.1 libtasn1: upgrade to 4.8 bluez5: upgrade to 5.39 mc: upgrade to 4.8.16 orc: upgrade to 0.4.25 harfbuzz: upgrade to 1.2.6

[OE-core] [PATCH 09/10] sqlite3: upgrade to 3.12.2

3.11.0 -> 3.12.2 Remove upstreamed patch: 1. fix-disable-static-shell.patch Signed-off-by: Maxin B. John --- .../sqlite/sqlite3/fix-disable-static-shell.patch | 61 -- meta/recipes-support/sqlite/sqlite3_3.11.0.bb | 11

[OE-core] [PATCH 07/10] orc: upgrade to 0.4.25

0.4.24 -> 0.4.25 Signed-off-by: Maxin B. John --- meta/recipes-devtools/orc/orc_0.4.24.bb | 27 --- meta/recipes-devtools/orc/orc_0.4.25.bb | 27 +++ 2 files changed, 27 insertions(+), 27 deletions(-) delete mode 100644

[OE-core] [PATCH 03/10] pkgconfig: update to version 0.29.1

87152c0 : Update to 0.29.1 753f0ba : glib: Fix OSX build with internal glib 5164b9d : Revert "Quote pc_path virtual variable" a3e58e7 : check: More thoroughly test variable usage 1c564a3 : Only unquote --variable when it appears quoted e6d33fb : Revert "Unquote values of requested variables"

[OE-core] [PATCH 04/10] libtasn1: upgrade to 4.8

4.7 -> 4.8 Signed-off-by: Maxin B. John --- meta/recipes-support/gnutls/libtasn1_4.7.bb | 20 meta/recipes-support/gnutls/libtasn1_4.8.bb | 20 2 files changed, 20 insertions(+), 20 deletions(-) delete mode 100644

[OE-core] [PATCH 01/10] acpid: upgrade to 2.0.27

2.0.26 -> 2.0.27 Remove upstreamed patch: 0001-Fix-out-of-source-build.patch Signed-off-by: Maxin B. John --- .../acpid/acpid/0001-Fix-out-of-source-build.patch | 46 -- meta/recipes-bsp/acpid/acpid_2.0.26.bb | 9 -

[OE-core] [PATCH 02/10] ethtool: upgrade to 4.5

4.2 -> 4.5 Signed-off-by: Maxin B. John --- meta/recipes-extended/ethtool/ethtool_4.2.bb | 30 meta/recipes-extended/ethtool/ethtool_4.5.bb | 30 2 files changed, 30 insertions(+), 30 deletions(-) delete mode

Re: [OE-core] how can i tell which default kernel config OE started with?

On Tue, May 3, 2016 at 9:12 AM, Robert P. J. Day wrote: > On Tue, 3 May 2016, Bruce Ashfield wrote: > > > > > > > On Tue, May 3, 2016 at 6:53 AM, Robert P. J. Day > wrote: > > > > (actually, working in wind river linux but i suspect the

[OE-core] [meta-oe]: Run time dependencies(i.e. Python package/modules) are not mentioned in dstat recipe

Hi, I am beginner to the yocto recipes. I have following observation regarding dstat recipe, 1. dstat utility requires some python modules during it's execution(i.e. run time dependencies). 2. As per my understanding, yocto recipes should mention their run time dependencies under RDEPENDS

[OE-core] [Master][krogoth][PATCH] librsvg: Security fixes via update to 2.40.15

From: Armin Kuster CVE-2016-4347 librsvg2: DoS parsing SVGs with circular definitions in certain rsvg_cairo_*() functions CVE-2016-4348 librsvg2: DoS parsing SVGs with circular definitions _rsvg_css_normalize_font_size() function Signed-off-by: Armin Kuster

Re: [OE-core] how can i tell which default kernel config OE started with?

On Tue, 3 May 2016, Bruce Ashfield wrote: > > > On Tue, May 3, 2016 at 6:53 AM, Robert P. J. Day > wrote: > >   (actually, working in wind river linux but i suspect the answer will > be the same.) > >   i've defined a target board and, rather than

Re: [OE-core] how can i tell which default kernel config OE started with?

On Tue, May 3, 2016 at 6:53 AM, Robert P. J. Day wrote: > > (actually, working in wind river linux but i suspect the answer will > be the same.) > > i've defined a target board and, rather than supplying a full > "defconfig" file as a starting point for kernel

[OE-core] [PATCH] lib/oe/rootfs: Fix DEBUGFS generation for opkg & openssl-cnf

When enabling extra DEBUGFS image generation with opkg, the following error is seen when openssl-cnf is included in the image. Collected errors: * file_md5sum_alloc: Failed to open file

Re: [OE-core] [PATCH v2] Allow different filesystems to be used for VM images.

What is the status of this patch? On Fri, 29 Apr 2016 08:41:49 -0400 Ian Reinhart Geiser wrote > This allows for things like btrfs to be used vs just ext4. > The default value of ext4 is kept so there is no functional > change unless VM_ROOTFS_TYPE is

Re: [OE-core] [PATCH] arch-powerpc64.inc: disable the use of qemu usermode on ppc64

On 05/02/2016 06:46 PM, Khem Raj wrote: should we replace qemu-ppc with qemu-ppc64 instead of disabling it qemu-ppc64 is already used on 64 bit powerpc, the problem is that it always crashes. Do we need to adjust the emulated machine parameter ? I don't see how. The CPU list produced by

[OE-core] how can i tell which default kernel config OE started with?

(actually, working in wind river linux but i suspect the answer will be the same.) i've defined a target board and, rather than supplying a full "defconfig" file as a starting point for kernel configuration, my BSP layer starts by applying a "kernel_baseline.cfg" file which contains only a

Re: [OE-core] [PATCH] image_types.bbclass: add WIC_CREATE_EXTRA_ARGS

Hi Christopher, Thank you for the patch! I like the idea. Would you mind adding or modifying wic oe-selftest to cover this? Signed-off-by: Ed Bartosh PS: You've mentioned --bmap as a possible use case scenario for this. I don't think this is the case as it's

Re: [OE-core] [master][PATCH] gcc-cross{, -canadian}: remove --with-linker-hash-style

* Martin Jansa [160503 10:08]: > It would be nice to really poison the value if possible > --with-linker-hash-style=YOU_NEED_TO_RESPECT_LDFLAGS > to cause linker call to fail when someone is using oe-core toolchain > outside OE itself (so might ignore LDFLAGS, but without

Re: [OE-core] Make runqemu knows nothing about machine

On 05/03/2016 01:51 AM, Randy Witt wrote: On 04/29/2016 03:09 AM, Robert Yang wrote: On 04/29/2016 05:45 PM, Richard Purdie wrote: On Tue, 2016-04-26 at 11:42 +0800, Robert Yang wrote: Hello, The qemu-native can boot a lot of machines, but oe-core's runqemu can only boot a few of them

Re: [OE-core] [master][PATCH] gcc-cross{, -canadian}: remove --with-linker-hash-style

On Mon, May 02, 2016 at 02:37:43PM -0700, Khem Raj wrote: > > > On May 2, 2016, at 1:37 PM, Christopher Larson wrote: > > > > > > > > On Mon, May 2, 2016 at 8:34 PM, Khem Raj > > wrote: > > > > > On May 2, 2016, at 1:09 PM,

Re: [OE-core] [PATCH] lib/oe/rootfs: Fix DEBUGFS generation when using opkg

On Mon, 2016-05-02 at 11:15 -0500, Alejandro del Castillo wrote: > > On 05/02/2016 08:39 AM, Patrick Ohly wrote: > > On Fri, 2016-04-22 at 14:51 +0100, Richard Purdie wrote: > >> When enabling extra DEBUGFS image generation with opkg, errors are seen > >> like: > >> > >> ERROR: