[OE-core] MS Windows machine?

[Steffen Sledz]

Anyone tried to cross-compile for MS Windows target with Yocto/OE?

Regards,
Steffen

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

Re: [OE-core] [PATCH 1/1] systemd: fix PACKAGECONFIG for lz4

[ChenQi]

The problem seems to be that the lz4 packaging problem.
lz4-ptest is packages as liblz4 and is installed instead of the lz4 package.

Best Regards,
Chen Qi

On 12/21/2017 12:41 PM, Robert Yang wrote:

Fixed:
MACHINE = "qemux86-64"
PACKAGECONFIG_append_pn-systemd = "lz4"
DISTRO_FEATURES_append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"

$ bitbake core-image-minimal
$ runqemu tmp/deploy/images/qemux86-64/ nographic
/sbin/init: error while loading shared libraries: liblz4.so.1: cannot open 
shared object file: No such file or directory

Add lz4 to RDEPENDS to fix the problem.

Signed-off-by: Robert Yang 
---
  meta/recipes-core/systemd/systemd_234.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/systemd/systemd_234.bb 
b/meta/recipes-core/systemd/systemd_234.bb
index 778b868..ed82c33 100644
--- a/meta/recipes-core/systemd/systemd_234.bb
+++ b/meta/recipes-core/systemd/systemd_234.bb
@@ -122,7 +122,7 @@ PACKAGECONFIG[ldconfig] = 
"--enable-ldconfig,--disable-ldconfig"
  PACKAGECONFIG[libidn] = "--enable-libidn,--disable-libidn,libidn"
  PACKAGECONFIG[localed] = "--enable-localed,--disable-localed"
  PACKAGECONFIG[logind] = "--enable-logind,--disable-logind"
-PACKAGECONFIG[lz4] = "--enable-lz4,--disable-lz4,lz4"
+PACKAGECONFIG[lz4] = "--enable-lz4,--disable-lz4,lz4,lz4"
  PACKAGECONFIG[machined] = "--enable-machined,--disable-machined"
  PACKAGECONFIG[manpages] = "--enable-manpages,--disable-manpages,libxslt-native 
xmlto-native docbook-xml-dtd4-native docbook-xsl-stylesheets-native"
  PACKAGECONFIG[microhttpd] = 
"--enable-microhttpd,--disable-microhttpd,libmicrohttpd"



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

[OE-core] [PATCH 1/1] systemd: fix PACKAGECONFIG for lz4

[Robert Yang]

Fixed:
MACHINE = "qemux86-64"
PACKAGECONFIG_append_pn-systemd = "lz4"
DISTRO_FEATURES_append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"

$ bitbake core-image-minimal
$ runqemu tmp/deploy/images/qemux86-64/ nographic
/sbin/init: error while loading shared libraries: liblz4.so.1: cannot open 
shared object file: No such file or directory

Add lz4 to RDEPENDS to fix the problem.

Signed-off-by: Robert Yang 
---
 meta/recipes-core/systemd/systemd_234.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/systemd/systemd_234.bb 
b/meta/recipes-core/systemd/systemd_234.bb
index 778b868..ed82c33 100644
--- a/meta/recipes-core/systemd/systemd_234.bb
+++ b/meta/recipes-core/systemd/systemd_234.bb
@@ -122,7 +122,7 @@ PACKAGECONFIG[ldconfig] = 
"--enable-ldconfig,--disable-ldconfig"
 PACKAGECONFIG[libidn] = "--enable-libidn,--disable-libidn,libidn"
 PACKAGECONFIG[localed] = "--enable-localed,--disable-localed"
 PACKAGECONFIG[logind] = "--enable-logind,--disable-logind"
-PACKAGECONFIG[lz4] = "--enable-lz4,--disable-lz4,lz4"
+PACKAGECONFIG[lz4] = "--enable-lz4,--disable-lz4,lz4,lz4"
 PACKAGECONFIG[machined] = "--enable-machined,--disable-machined"
 PACKAGECONFIG[manpages] = "--enable-manpages,--disable-manpages,libxslt-native 
xmlto-native docbook-xml-dtd4-native docbook-xsl-stylesheets-native"
 PACKAGECONFIG[microhttpd] = 
"--enable-microhttpd,--disable-microhttpd,libmicrohttpd"
-- 
2.7.4

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

[OE-core] [PATCH 0/1] systemd: fix PACKAGECONFIG for lz4

[Robert Yang]

The following changes since commit 978472c58629d1448399207873bbead96b27102e:

  image.bbclass: Add additional bb.debug to help track 12304 (2017-12-18 
18:02:12 +)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/systemd_lz4
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/systemd_lz4

Robert Yang (1):
  systemd: fix PACKAGECONFIG for lz4

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

-- 
2.7.4

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

Re: [OE-core] systemd PACKAGECONFIG = "lz4" leads to broken init

[Robert Yang]

Hi Marcus,

I think that the following patch can fix the problem:

The following changes since commit 978472c58629d1448399207873bbead96b27102e:

  image.bbclass: Add additional bb.debug to help track 12304 (2017-12-18 
18:02:12 +)


are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/systemd_lz4
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/systemd_lz4

Robert Yang (1):
  systemd: fix PACKAGECONFIG for lz4

// Robert

On 12/21/2017 05:34 AM, Marcus Hoffmann wrote:

Dear all,

when building poky with

PACKAGECONFIG_append_pn-systemd = "lz4"

in local.conf and
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
in bblayers.conf, init (=systemd) can't start because of a missing lz4
library:

/sbin/init: error while loading shared libraries: liblz4.so.1: cannot
open shared object file: No such file or directory

Best wishes,
Marcus Hoffmann


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

[OE-core] [PATCH 0/2] fix for oeqa/core/loader.py and image_types.bbclass

[Robert Yang]

The following changes since commit 978472c58629d1448399207873bbead96b27102e:

  image.bbclass: Add additional bb.debug to help track 12304 (2017-12-18 
18:02:12 +)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/2fixes
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/2fixes

Robert Yang (2):
  oeqa/core/loader.py: fix re for module
  image_types.bbclass: use stat to get sparse file's size

 meta/classes/image_types.bbclass | 2 +-
 meta/lib/oeqa/core/loader.py | 7 ---
 2 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.7.4

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

[OE-core] [PATCH 1/2] oeqa/core/loader.py: fix re for module

[Robert Yang]

Fixed:
$ oe-selftest -r eSDK.oeSDKExtSelfTest.test_image_generation_binary_feeds
Traceback (most recent call last):
[snip]
  File "/workspace2/lyang1/poky/meta/lib/oeqa/core/loader.py", line 49, in 
_built_modules_dict
module_name, class_name, test_name = m.groups()
AttributeError: 'NoneType' object has no attribute 'groups'

The old code assumed the arg should be:
module.Class.test

Note about the module and Class, the lower and upper cases matters, which can't
handle the testcases like 
eSDK.oeSDKExtSelfTest.test_image_generation_binary_feeds
and gotoolchain.oeGoToolchainSelfTest.test_go_dep_build. Use a new re to fix
the problem, now all of the following commmands can work:
$ oe-selftest -r eSDK
$ oe-selftest -r eSDK.oeSDKExtSelfTest
$ oe-selftest -r eSDK.oeSDKExtSelfTest.test_image_generation_binary_feeds

[YOCTO #12438]

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/core/loader.py | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/core/loader.py b/meta/lib/oeqa/core/loader.py
index 975a081..25078ba 100644
--- a/meta/lib/oeqa/core/loader.py
+++ b/meta/lib/oeqa/core/loader.py
@@ -41,9 +41,10 @@ def _built_modules_dict(modules):
 return modules_dict
 
 for module in modules:
-# Assumption: package and module names do not contain upper case
-# characters, whereas class names do
-m = re.match(r'^([^A-Z]+)(?:\.([A-Z][^.]*)(?:\.([^.]+))?)?$', module)
+# The format is module.class.test, while .class and .test is optional.
+m = re.match(r'([^\.]+)(?:\.([^\.]+))?(?:\.([^\.]*))?', module)
+if not m:
+raise OEQATestNotFound("Not found %s in loaded test cases" % 
module)
 
 module_name, class_name, test_name = m.groups()
 
-- 
2.7.4

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

[OE-core] [PATCH 2/2] image_types.bbclass: use stat to get sparse file's size

[Robert Yang]

The "ls -s sparse_file"'s result is 0, use stat to replace of it.

Signed-off-by: Robert Yang 
---
 meta/classes/image_types.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
index e881d0c..4a96f61 100644
--- a/meta/classes/image_types.bbclass
+++ b/meta/classes/image_types.bbclass
@@ -86,7 +86,7 @@ oe_mkext234fs () {
bbdebug 1 Executing "dd if=/dev/zero 
of=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype seek=$ROOTFS_SIZE 
count=$COUNT bs=1024"
dd if=/dev/zero 
of=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype seek=$ROOTFS_SIZE 
count=$COUNT bs=1024
bbdebug 1 "Actual Rootfs size:  `du -s ${IMAGE_ROOTFS}`"
-   bbdebug 1 "Actual Partion size: `ls -s 
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype`"
+   bbdebug 1 "Actual Partion size: `stat -c '%s' 
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype`"
bbdebug 1 Executing "mkfs.$fstype -F $extra_imagecmd 
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype -d ${IMAGE_ROOTFS}"
mkfs.$fstype -F $extra_imagecmd 
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype -d ${IMAGE_ROOTFS}
# Error codes 0-3 indicate successfull operation of fsck (no errors or 
errors corrected)
-- 
2.7.4

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

[OE-core] [rocko][PATCH 4/6] initramfs-module-install: Remove allarch and FILESEXTRAPATHS

[California Sullivan]

From: Martin Jansa 

* files is already included in default FILESPATH
* it cannot inherit allarch as it RDEPENDS on bunch of TUNE_PKGARCH packages
* use the same COMPATIBLE_HOST restrictions as grub has to prevent ERRORs in
  bitbake world
  ERROR: Nothing RPROVIDES 'grub' (but 
oe-core/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb 
RDEPENDS on or otherwise requires it)
  grub was skipped: incompatible with host arm-oe-linux-gnueabi (not in 
COMPATIBLE_HOST)
  grub was skipped: incompatible with host arm-oe-linux-gnueabi (not in 
COMPATIBLE_HOST)
  NOTE: Runtime target 'grub' is unbuildable, removing...
  Missing or unbuildable dependency chain was: ['grub']
  ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.

Signed-off-by: Martin Jansa 
Signed-off-by: Ross Burton 
(cherry picked from commit ecad98a0ffe41d8cc8890d16be09e4b604a1e192)
Signed-off-by: California Sullivan 
---
 .../initrdscripts/initramfs-module-install-efi_1.0.bb | 3 ---
 meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb   | 8 +---
 2 files changed, 5 insertions(+), 6 deletions(-)

diff --git 
a/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb 
b/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb
index 24b53a8498..1e7f76fd56 100644
--- a/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb
+++ b/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb
@@ -5,9 +5,6 @@ RDEPENDS_${PN} = "initramfs-framework-base parted 
e2fsprogs-mke2fs dosfstools ut
 
 PR = "r4"
 
-inherit allarch
-
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
 SRC_URI = "file://init-install-efi.sh"
 
 S = "${WORKDIR}"
diff --git a/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb 
b/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb
index ce7f165bfe..02b69f37a4 100644
--- a/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb
+++ b/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb
@@ -3,11 +3,13 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
 RDEPENDS_${PN} = "initramfs-framework-base grub parted e2fsprogs-mke2fs 
util-linux-blkid"
 
-PR = "r1"
+# The same restriction as grub
+COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|aarch64.*)-(linux.*|freebsd.*)'
+COMPATIBLE_HOST_armv7a = 'null'
+COMPATIBLE_HOST_armv7ve = 'null'
 
-inherit allarch
+PR = "r1"
 
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
 SRC_URI = "file://init-install.sh"
 
 S = "${WORKDIR}"
-- 
2.14.3

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

[OE-core] [rocko][PATCH 5/6] init-install: fix grub-install command

[California Sullivan]

The grub_version variable was calling 'grub-install -v' (verbose) instead
of 'grub-install -V' (version) causing unexpected failures.

Fixes bug [YOCTO #12111].

Signed-off-by: California Sullivan 
Signed-off-by: Ross Burton 
(cherry picked from commit 38dcbd96e82b1c40576a0514f053266429dca5d1)
Signed-off-by: California Sullivan 
---
 meta/recipes-core/initrdscripts/files/init-install.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/initrdscripts/files/init-install.sh 
b/meta/recipes-core/initrdscripts/files/init-install.sh
index 572613ecd4..1cac8064a2 100644
--- a/meta/recipes-core/initrdscripts/files/init-install.sh
+++ b/meta/recipes-core/initrdscripts/files/init-install.sh
@@ -132,7 +132,7 @@ fi
 
 disk_size=$(parted ${device} unit mb print | grep '^Disk .*: .*MB' | cut -d" " 
-f 3 | sed -e "s/MB//")
 
-grub_version=$(grub-install -v|sed 's/.* \([0-9]\).*/\1/')
+grub_version=$(grub-install -V|sed 's/.* \([0-9]\).*/\1/')
 
 if [ $grub_version -eq 0 ] ; then
 bios_boot_size=0
-- 
2.14.3

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

[OE-core] [rocko][PATCH 6/6] install*.sh: add short sleep after parted commands

[California Sullivan]

I wasn't able to install to my Optane SSD due to the following error:

Formatting /dev/nvme0n1p1 to vfat...
mkfs.fat 4.1 (2017-01-24)
mkfs.vfat: unable to open /dev/nvme0n1p1: No such file or directory
Target install-efi failed

A couple lines later I see:

[10.265401]  nvme0n1: p1 p2 p3

Then looking at the device itself after booting from a USB stick:

root@intel-corei7-64: ~# ls /dev/nvme0n1*
/dev/nvme0n1 /dev/nvme0n1p1 /dev/nvme0n1p2 /dev/nvme0n1p3

So it looks like the parted commands return before the device node is
actually created.

Work around this issue by waiting for device nodes for a short duration.

Signed-off-by: California Sullivan 
Signed-off-by: Ross Burton 
(cherry picked from commit 9daafd49b448122e35d67a1637ce2212793a4dc5)
Signed-off-by: California Sullivan 
---
 meta/recipes-core/initrdscripts/files/init-install-efi.sh | 7 +++
 meta/recipes-core/initrdscripts/files/init-install.sh | 7 +++
 2 files changed, 14 insertions(+)

diff --git a/meta/recipes-core/initrdscripts/files/init-install-efi.sh 
b/meta/recipes-core/initrdscripts/files/init-install-efi.sh
index 5ad3a60c05..706418fa9c 100644
--- a/meta/recipes-core/initrdscripts/files/init-install-efi.sh
+++ b/meta/recipes-core/initrdscripts/files/init-install-efi.sh
@@ -186,6 +186,13 @@ parted ${device} mkpart swap linux-swap $swap_start 100%
 
 parted ${device} print
 
+echo "Waiting for device nodes..."
+C=0
+while [ $C -ne 3 ] && [ ! -e $bootfs  -o ! -e $rootfs -o ! -e $swap ]; do
+C=$(( C + 1 ))
+sleep 1
+done
+
 echo "Formatting $bootfs to vfat..."
 mkfs.vfat $bootfs
 
diff --git a/meta/recipes-core/initrdscripts/files/init-install.sh 
b/meta/recipes-core/initrdscripts/files/init-install.sh
index 1cac8064a2..dade059c8f 100644
--- a/meta/recipes-core/initrdscripts/files/init-install.sh
+++ b/meta/recipes-core/initrdscripts/files/init-install.sh
@@ -211,6 +211,13 @@ parted ${device} mkpart $pname linux-swap $swap_start 100%
 
 parted ${device} print
 
+echo "Waiting for device nodes..."
+C=0
+while [ $C -ne 3 ] && [ ! -e $bootfs  -o ! -e $rootfs -o ! -e $swap ]; do
+C=$(( C + 1 ))
+sleep 1
+done
+
 echo "Formatting $bootfs to ext3..."
 mkfs.ext3 $bootfs
 
-- 
2.14.3

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

[OE-core] [rocko][PATCH 1/6] initramfs-module-install-efi: point to original copy and delete new file

[California Sullivan]

There is no need to maintain two of the exact same files.

Signed-off-by: California Sullivan 
Signed-off-by: Ross Burton 
(cherry picked from commit 49ba882be9e28a51651a543779e6f02d33861393)
Signed-off-by: California Sullivan 
---
 .../initramfs-framework/install-efi.sh | 276 -
 .../initramfs-module-install-efi_1.0.bb|   6 +-
 2 files changed, 3 insertions(+), 279 deletions(-)
 delete mode 100644 
meta/recipes-core/initrdscripts/initramfs-framework/install-efi.sh

diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/install-efi.sh 
b/meta/recipes-core/initrdscripts/initramfs-framework/install-efi.sh
deleted file mode 100644
index 5ad3a60c05..00
--- a/meta/recipes-core/initrdscripts/initramfs-framework/install-efi.sh
+++ /dev/null
@@ -1,276 +0,0 @@
-#!/bin/sh -e
-#
-# Copyright (c) 2012, Intel Corporation.
-# All rights reserved.
-#
-# install.sh [device_name] [rootfs_name]
-#
-
-PATH=/sbin:/bin:/usr/sbin:/usr/bin
-
-# We need 20 Mb for the boot partition
-boot_size=20
-
-# 5% for swap
-swap_ratio=5
-
-# Get a list of hard drives
-hdnamelist=""
-live_dev_name=`cat /proc/mounts | grep ${1%/} | awk '{print $1}'`
-live_dev_name=${live_dev_name#\/dev/}
-# Only strip the digit identifier if the device is not an mmc
-case $live_dev_name in
-mmcblk*)
-;;
-nvme*)
-;;
-*)
-live_dev_name=${live_dev_name%%[0-9]*}
-;;
-esac
-
-echo "Searching for hard drives ..."
-
-# Some eMMC devices have special sub devices such as mmcblk0boot0 etc
-# we're currently only interested in the root device so pick them wisely
-devices=`ls /sys/block/ | grep -v mmcblk` || true
-mmc_devices=`ls /sys/block/ | grep "mmcblk[0-9]\{1,\}$"` || true
-devices="$devices $mmc_devices"
-
-for device in $devices; do
-case $device in
-loop*)
-# skip loop device
-;;
-sr*)
-# skip CDROM device
-;;
-ram*)
-# skip ram device
-;;
-*)
-# skip the device LiveOS is on
-# Add valid hard drive name to the list
-case $device in
-$live_dev_name*)
-# skip the device we are running from
-;;
-*)
-hdnamelist="$hdnamelist $device"
-;;
-esac
-;;
-esac
-done
-
-if [ -z "${hdnamelist}" ]; then
-echo "You need another device (besides the live device 
/dev/${live_dev_name}) to install the image. Installation aborted."
-exit 1
-fi
-
-TARGET_DEVICE_NAME=""
-for hdname in $hdnamelist; do
-# Display found hard drives and their basic info
-echo "---"
-echo /dev/$hdname
-if [ -r /sys/block/$hdname/device/vendor ]; then
-echo -n "VENDOR="
-cat /sys/block/$hdname/device/vendor
-fi
-if [ -r /sys/block/$hdname/device/model ]; then
-echo -n "MODEL="
-cat /sys/block/$hdname/device/model
-fi
-if [ -r /sys/block/$hdname/device/uevent ]; then
-echo -n "UEVENT="
-cat /sys/block/$hdname/device/uevent
-fi
-echo
-done
-
-# Get user choice
-while true; do
-echo "Please select an install target or press n to exit ($hdnamelist ): "
-read answer
-if [ "$answer" = "n" ]; then
-echo "Installation manually aborted."
-exit 1
-fi
-for hdname in $hdnamelist; do
-if [ "$answer" = "$hdname" ]; then
-TARGET_DEVICE_NAME=$answer
-break
-fi
-done
-if [ -n "$TARGET_DEVICE_NAME" ]; then
-break
-fi
-done
-
-if [ -n "$TARGET_DEVICE_NAME" ]; then
-echo "Installing image on /dev/$TARGET_DEVICE_NAME ..."
-else
-echo "No hard drive selected. Installation aborted."
-exit 1
-fi
-
-device=/dev/$TARGET_DEVICE_NAME
-
-#
-# The udev automounter can cause pain here, kill it
-#
-rm -f /etc/udev/rules.d/automount.rules
-rm -f /etc/udev/scripts/mount*
-
-#
-# Unmount anything the automounter had mounted
-#
-umount ${device}* 2> /dev/null || /bin/true
-
-mkdir -p /tmp
-
-# Create /etc/mtab if not present
-if [ ! -e /etc/mtab ] && [ -e /proc/mounts ]; then
-ln -sf /proc/mounts /etc/mtab
-fi
-
-disk_size=$(parted ${device} unit mb print | grep '^Disk .*: .*MB' | cut -d" " 
-f 3 | sed -e "s/MB//")
-
-swap_size=$((disk_size*swap_ratio/100))
-rootfs_size=$((disk_size-boot_size-swap_size))
-
-rootfs_start=$((boot_size))
-rootfs_end=$((rootfs_start+rootfs_size))
-swap_start=$((rootfs_end))
-
-# MMC devices are special in a couple of ways
-# 1) they use a partition prefix character 'p'
-# 2) they are detected asynchronously (need rootwait)
-rootwait=""
-part_prefix=""
-if [ ! "${device#/dev/mmcblk}" = "${device}" ] || \
-   [ ! "${device#/dev/nvme}" = "${device}" ]; then
-part_prefix="p"
-rootwait="rootwait"
-fi
-
-# USB devices also require 

[OE-core] [rocko][PATCH 3/6] initramfs-framework: add install module

[California Sullivan]

The non-EFI counterpart for installation was previously missing for
initramfs-framework. This simply puts the normal install script in the
correct location for initramfs-framework to make use of it.

Partial fix for [YOCTO #12346].

Signed-off-by: California Sullivan 
Signed-off-by: Ross Burton 
(cherry picked from commit f9d7cf30b12cbc5f642a11c0511dc1dc3ccf1aa5)
Signed-off-by: California Sullivan 
---
 meta/conf/layer.conf |  4 
 .../initrdscripts/initramfs-module-install_1.0.bb| 20 
 2 files changed, 24 insertions(+)
 create mode 100644 
meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb

diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index 6be2a57a70..4ba0b9378e 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -57,6 +57,10 @@ SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \
   initramfs-module-install-efi->e2fsprogs \
   initramfs-module-install-efi->parted \
   initramfs-module-install-efi->util-linux \
+  initramfs-module-install->e2fsprogs \
+  initramfs-module-install->grub \
+  initramfs-module-install->parted \
+  initramfs-module-install->util-linux \
   liberation-fonts->fontconfig \
   cantarell-fonts->fontconfig \
   gnome-icon-theme->librsvg \
diff --git a/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb 
b/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb
new file mode 100644
index 00..ce7f165bfe
--- /dev/null
+++ b/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb
@@ -0,0 +1,20 @@
+SUMMARY = "initramfs-framework module for installation option"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+RDEPENDS_${PN} = "initramfs-framework-base grub parted e2fsprogs-mke2fs 
util-linux-blkid"
+
+PR = "r1"
+
+inherit allarch
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
+SRC_URI = "file://init-install.sh"
+
+S = "${WORKDIR}"
+
+do_install() {
+install -d ${D}/init.d
+install -m 0755 ${WORKDIR}/init-install.sh ${D}/init.d/install.sh
+}
+
+FILES_${PN} = "/init.d/install.sh"
-- 
2.14.3

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

[OE-core] [rocko][PATCH 0/6] backport installer fixes for rocko

[California Sullivan]

Hi Armin,

I know you're aware of these, but I don't see them in
contrib/stable/rocko-next anymore, so I just wanted to make sure they're
still going in.

These fix bugs [YOCTO #12111] and [YOCTO #12346].

If you already have them queued somewhere else, sorry for the noise!

Thanks,
Cal

California Sullivan (5):
  initramfs-module-install-efi: point to original copy and delete new
file
  initramfs-module-install-efi: update summary
  initramfs-framework: add install module
  init-install: fix grub-install command
  install*.sh: add short sleep after parted commands

Martin Jansa (1):
  initramfs-module-install: Remove allarch and FILESEXTRAPATHS

 meta/conf/layer.conf   |   4 +
 .../initrdscripts/files/init-install-efi.sh|   7 +
 .../initrdscripts/files/init-install.sh|   9 +-
 .../initramfs-framework/install-efi.sh | 276 -
 .../initramfs-module-install-efi_1.0.bb|   9 +-
 .../initrdscripts/initramfs-module-install_1.0.bb  |  22 ++
 6 files changed, 44 insertions(+), 283 deletions(-)
 delete mode 100644 
meta/recipes-core/initrdscripts/initramfs-framework/install-efi.sh
 create mode 100644 
meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb

-- 
2.14.3

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

[OE-core] [rocko][PATCH 2/6] initramfs-module-install-efi: update summary

[California Sullivan]

Note that this is an installation option for EFI systems.

Signed-off-by: California Sullivan 
Signed-off-by: Ross Burton 
(cherry picked from commit 366ddd22245a72df4c8e561761c6df8a6654bba6)
Signed-off-by: California Sullivan 
---
 meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb 
b/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb
index 3d8c9e7ebb..24b53a8498 100644
--- a/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb
+++ b/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb
@@ -1,4 +1,4 @@
-SUMMARY = "initramfs-framework module for installation option"
+SUMMARY = "initramfs-framework module for EFI installation option"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
 RDEPENDS_${PN} = "initramfs-framework-base parted e2fsprogs-mke2fs dosfstools 
util-linux-blkid"
-- 
2.14.3

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

[OE-core] systemd PACKAGECONFIG = "lz4" leads to broken init

[Marcus Hoffmann]

Dear all,

when building poky with

PACKAGECONFIG_append_pn-systemd = "lz4"

in local.conf and
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
in bblayers.conf, init (=systemd) can't start because of a missing lz4
library:

/sbin/init: error while loading shared libraries: liblz4.so.1: cannot
open shared object file: No such file or directory

Best wishes,
Marcus Hoffmann
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/2] systemd: inherit distro_features_check

[Andre McCurdy]

On Wed, Dec 20, 2017 at 1:53 PM, Andre McCurdy  wrote:
> On Tue, Dec 19, 2017 at 5:53 PM, Robert Yang  
> wrote:
>> Use distro_features_check so that we can have a uniform controller.
>>
>> Signed-off-by: Robert Yang 
>> ---
>>  meta/recipes-core/systemd/systemd-serialgetty.bb | 10 --
>>  meta/recipes-core/systemd/systemd_234.bb | 13 +
>>  meta/recipes-core/udev/eudev_3.2.2.bb|  9 +++--
>>  3 files changed, 12 insertions(+), 20 deletions(-)
>>
>> diff --git a/meta/recipes-core/systemd/systemd-serialgetty.bb 
>> b/meta/recipes-core/systemd/systemd-serialgetty.bb
>> index d934716..d67a3c9 100644
>> --- a/meta/recipes-core/systemd/systemd-serialgetty.bb
>> +++ b/meta/recipes-core/systemd/systemd-serialgetty.bb
>> @@ -11,6 +11,10 @@ SRC_URI = "file://serial-getty@.service"
>>
>>  S = "${WORKDIR}"
>>
>> +# As this package is tied to systemd, only build it when we're also 
>> building systemd.
>> +inherit distro_features_check
>> +REQUIRED_DISTRO_FEATURES = "systemd"
>> +
>
> "inherit distro_features_check" needs to be added too.

Oops, sorry. It's right there... I see it now :-)

>>  do_install() {
>> if [ ! -z "${SERIAL_CONSOLES}" ] ; then
>> default_baudrate=`echo "${SERIAL_CONSOLES}" | sed 's/\;.*//'`
>> @@ -43,10 +47,4 @@ do_install() {
>>  FILES_${PN} = "${systemd_unitdir}/system/*.service ${sysconfdir}"
>>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>>
>> -# As this package is tied to systemd, only build it when we're also 
>> building systemd.
>> -python () {
>> -if not bb.utils.contains ('DISTRO_FEATURES', 'systemd', True, False, d):
>> -raise bb.parse.SkipPackage("'systemd' not in DISTRO_FEATURES")
>> -}
>> -
>>  ALLOW_EMPTY_${PN} = "1"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/2] systemd: inherit distro_features_check

[Andre McCurdy]

On Tue, Dec 19, 2017 at 5:53 PM, Robert Yang  wrote:
> Use distro_features_check so that we can have a uniform controller.
>
> Signed-off-by: Robert Yang 
> ---
>  meta/recipes-core/systemd/systemd-serialgetty.bb | 10 --
>  meta/recipes-core/systemd/systemd_234.bb | 13 +
>  meta/recipes-core/udev/eudev_3.2.2.bb|  9 +++--
>  3 files changed, 12 insertions(+), 20 deletions(-)
>
> diff --git a/meta/recipes-core/systemd/systemd-serialgetty.bb 
> b/meta/recipes-core/systemd/systemd-serialgetty.bb
> index d934716..d67a3c9 100644
> --- a/meta/recipes-core/systemd/systemd-serialgetty.bb
> +++ b/meta/recipes-core/systemd/systemd-serialgetty.bb
> @@ -11,6 +11,10 @@ SRC_URI = "file://serial-getty@.service"
>
>  S = "${WORKDIR}"
>
> +# As this package is tied to systemd, only build it when we're also building 
> systemd.
> +inherit distro_features_check
> +REQUIRED_DISTRO_FEATURES = "systemd"
> +

"inherit distro_features_check" needs to be added too.

>  do_install() {
> if [ ! -z "${SERIAL_CONSOLES}" ] ; then
> default_baudrate=`echo "${SERIAL_CONSOLES}" | sed 's/\;.*//'`
> @@ -43,10 +47,4 @@ do_install() {
>  FILES_${PN} = "${systemd_unitdir}/system/*.service ${sysconfdir}"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>
> -# As this package is tied to systemd, only build it when we're also building 
> systemd.
> -python () {
> -if not bb.utils.contains ('DISTRO_FEATURES', 'systemd', True, False, d):
> -raise bb.parse.SkipPackage("'systemd' not in DISTRO_FEATURES")
> -}
> -
>  ALLOW_EMPTY_${PN} = "1"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] systemd: drop obsolete workaround for ARM + gcc 5.2

[Andre McCurdy]

Signed-off-by: Andre McCurdy 
---
 meta/recipes-core/systemd/systemd_234.bb | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/meta/recipes-core/systemd/systemd_234.bb 
b/meta/recipes-core/systemd/systemd_234.bb
index 778b868..9a10a31 100644
--- a/meta/recipes-core/systemd/systemd_234.bb
+++ b/meta/recipes-core/systemd/systemd_234.bb
@@ -183,9 +183,6 @@ EXTRA_OECONF = " \
 # per the systemd README, define VALGRIND=1 to run under valgrind
 CFLAGS .= "${@bb.utils.contains('PACKAGECONFIG', 'valgrind', ' -DVALGRIND=1', 
'', d)}"
 
-# disable problematic GCC 5.2 optimizations [YOCTO #8291]
-FULL_OPTIMIZATION_append_arm = " -fno-schedule-insns -fno-schedule-insns2"
-
 COMPILER_NM ?= "${HOST_PREFIX}gcc-nm"
 COMPILER_AR ?= "${HOST_PREFIX}gcc-ar"
 COMPILER_RANLIB ?= "${HOST_PREFIX}gcc-ranlib"
-- 
1.9.1

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

Re: [OE-core] [PATCH 3/3] runtime/cases/ptest.py: fail when ptests fail on target

[Alexander Kanavin]

On 12/20/2017 07:23 PM, Burton, Ross wrote:
So the context was that so many ptests were failing that the test 
couldn't be done automatically and expected to succeed. Bugs were filed 
and the problem chipped away at, but last I looked it wasn't in a state 
to be enabled.


If a core-image-sato passes with ptests enabled then that's great, but 
I'll be surprised if it does!


It doesn't. In fact, it never finishes, because bluez ptest hangs 
forever. That shouldn't be a problem though, because ptests are not 
included by default in any of the standard images, and so the test is 
simply skipped (see patch 1 of 3). The point of this patch is to 
eliminate misleading passing behaviour when people do include ptests - 
either for everything in their image or for specific packages they 
maintain, and want, for example, to check for regressions on version 
upgrades.


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

Re: [OE-core] [PATCH 3/3] runtime/cases/ptest.py: fail when ptests fail on target

[Burton, Ross]

So the context was that so many ptests were failing that the test couldn't
be done automatically and expected to succeed. Bugs were filed and the
problem chipped away at, but last I looked it wasn't in a state to be
enabled.

If a core-image-sato passes with ptests enabled then that's great, but I'll
be surprised if it does!

Ross

On 20 December 2017 at 15:45, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:

> That's the whole point isn't it? Previously this testcase succeeded
> even if some of the underlying on-target tests failed; the only way
> to find out if anything was wrong was to manually inspect the logs.
>
> Signed-off-by: Alexander Kanavin 
> ---
>  meta/lib/oeqa/runtime/cases/ptest.py | 8 
>  1 file changed, 8 insertions(+)
>
> diff --git a/meta/lib/oeqa/runtime/cases/ptest.py
> b/meta/lib/oeqa/runtime/cases/ptest.py
> index 6669e24f141..c5b8c9cb8fb 100644
> --- a/meta/lib/oeqa/runtime/cases/ptest.py
> +++ b/meta/lib/oeqa/runtime/cases/ptest.py
> @@ -83,3 +83,11 @@ class PtestRunnerTest(OERuntimeTestCase):
>  # Remove the old link to create a new one
>  os.remove(ptest_log_dir_link)
>  os.symlink(os.path.basename(ptest_log_dir), ptest_log_dir_link)
> +
> +failed_tests = {}
> +for section in parse_result.result_dict:
> +failed_testcases = [ test for test, result in
> parse_result.result_dict[section] if result == 'fail' ]
> +if failed_testcases:
> +failed_tests[section] = failed_testcases
> +
> +self.assertFalse(failed_tests, msg = "Failed ptests: %s"
> %(str(failed_tests)))
> --
> 2.15.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] ✗ patchtest: failure for gstreamer: use a patch instead of sed to fix gtk-doc makefiles

[Patchwork]

== Series Details ==

Series: gstreamer: use a patch instead of sed to fix gtk-doc makefiles
Revision: 1
URL   : https://patchwork.openembedded.org/series/10271/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Upstream-Status is Inappropriate, but no reason was 
provided [test_upstream_status_presence_format] 
  Suggested fixInclude a brief reason why gtk-doc-tweaks.patch is 
inappropriate
  Current  Upstream-Status: Inappropriate
  Standard format  Upstream-Status: Inappropriate [reason]



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

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

[OE-core] [PATCH] gstreamer: use a patch instead of sed to fix gtk-doc makefiles

[Ross Burton]

seds can get stale without warning and repeated application can cause problems,
so move the gtk-doc seds into a patch.

Signed-off-by: Ross Burton 
---
 .../gstreamer/files/gtk-doc-tweaks.patch   | 25 ++
 .../gstreamer/gstreamer1.0-plugins.inc | 16 +++---
 .../gstreamer/gstreamer1.0-rtsp-server.inc | 15 +++--
 meta/recipes-multimedia/gstreamer/gstreamer1.0.inc | 15 ++---
 4 files changed, 33 insertions(+), 38 deletions(-)
 create mode 100644 meta/recipes-multimedia/gstreamer/files/gtk-doc-tweaks.patch

diff --git a/meta/recipes-multimedia/gstreamer/files/gtk-doc-tweaks.patch 
b/meta/recipes-multimedia/gstreamer/files/gtk-doc-tweaks.patch
new file mode 100644
index 000..593d5bb043b
--- /dev/null
+++ b/meta/recipes-multimedia/gstreamer/files/gtk-doc-tweaks.patch
@@ -0,0 +1,25 @@
+Patch the gtk-doc makefiles so that the qemu wrapper is used to run transient
+binaries instead of libtool wrapper or running them directly.
+
+Also substitute a bogus plugin scanner, as trying to run the real one is 
causing
+issues during build on x86_64.
+
+Upstream-Status: Inappropriate
+Signed-off-by: Ross Burton 
+
+--- a/common/gtk-doc.mak.orig  2017-12-20 12:43:20.586474397 +
 b/common/gtk-doc.mak   2017-12-20 12:45:20.758874995 +
+@@ -8,3 +8,3 @@
+ GTKDOC_LD = $(LIBTOOL) --tag=CC --mode=link $(CC) $(GTKDOC_DEPS_LIBS) 
$(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS)
+-GTKDOC_RUN = $(LIBTOOL) --mode=execute
++GTKDOC_RUN = $(top_builddir)/gtkdoc-qemuwrapper
+ else
+@@ -12,3 +12,3 @@
+ GTKDOC_LD = $(CC) $(GTKDOC_DEPS_LIBS) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) 
$(LDFLAGS)
+-GTKDOC_RUN =
++GTKDOC_RUN = $(top_builddir)/gtkdoc-qemuwrapper
+ endif
+@@ -99,2 +99,3 @@
+   fi; \
++  
GST_PLUGIN_SCANNER_1_0="$(top_builddir)/libs/gst/helpers/gst-plugin-scanner-dummy"
 \
+   GST_PLUGIN_SYSTEM_PATH_1_0=`cd $(top_builddir) && pwd`  \
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins.inc 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins.inc
index c40d3989119..dab0ea3b1a6 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins.inc
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins.inc
@@ -5,6 +5,8 @@ SECTION = "multimedia"
 
 DEPENDS = "gstreamer1.0 glib-2.0-native"
 
+SRC_URI_append = " file://gtk-doc-tweaks.patch"
+
 inherit autotools pkgconfig upstream-version-is-even gobject-introspection 
gtk-doc
 
 acpaths = "-I ${S}/common/m4 -I ${S}/m4"
@@ -34,19 +36,7 @@ delete_pkg_m4_file() {
rm -f "${S}/common/m4/gtk-doc.m4"
 }
 
-# gstreamer is not using system-wide makefiles (which we patch in gtkdoc 
recipe,
-# but its own custom ones, which we have to patch here
-patch_gtk_doc_makefiles() {
-# Patch the gtk-doc makefiles so that the qemu wrapper is used to run 
transient binaries
-# instead of libtool wrapper or running them directly
-# Also substitute a bogus plugin scanner, as trying to run the real 
one is causing issues during build on x86_64.
-sed -i \
-   -e "s|GTKDOC_RUN =.*|GTKDOC_RUN = 
\$(top_builddir)/gtkdoc-qemuwrapper|" \
-   -e "s|\$(GTKDOC_EXTRA_ENVIRONMENT)|\$(GTKDOC_EXTRA_ENVIRONMENT) 
GST_PLUGIN_SCANNER_1_0=\$(top_builddir)/libs/gst/helpers/gst-plugin-scanner-dummy|"
 \
-   ${S}/common/gtk-doc*mak
-}
-
-do_configure[prefuncs] += " delete_pkg_m4_file patch_gtk_doc_makefiles"
+do_configure[prefuncs] += " delete_pkg_m4_file"
 
 PACKAGES_DYNAMIC = "^${PN}-.*"
 
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc
index 68173ce7d94..a7476c5b8ac 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc
@@ -9,7 +9,8 @@ PNREAL = "gst-rtsp-server"
 
 SRC_URI = 
"http://gstreamer.freedesktop.org/src/${PNREAL}/${PNREAL}-${PV}.tar.xz \

file://0001-Don-t-hardcode-libtool-name-when-using-introspection.patch \
-   
file://0001-introspection.m4-prefix-pkgconfig-paths-with-PKG_CON.patch"
+   
file://0001-introspection.m4-prefix-pkgconfig-paths-with-PKG_CON.patch \
+   file://gtk-doc-tweaks.patch"
 
 S = "${WORKDIR}/${PNREAL}-${PV}"
 
@@ -24,17 +25,7 @@ delete_pkg_m4_file() {
 rm "${S}/common/m4/pkg.m4" || true
 }
 
-# gstreamer is not using system-wide makefiles (which we patch in gtkdoc 
recipe,
-# but its own custom ones, which we have to patch here
-patch_gtk_doc_makefiles() {
-# Patch the gtk-doc makefiles so that the qemu wrapper is used to run 
transient binaries
-# instead of libtool wrapper or running them directly
-sed -i \
-   -e "s|GTKDOC_RUN =.*|GTKDOC_RUN = 
\$(top_builddir)/gtkdoc-qemuwrapper|" \
-   ${S}/common/gtk-doc*mak
-}
-
-do_configure[prefuncs] += " delete_pkg_m4_file 

[OE-core] [PATCH 3/3] runtime/cases/ptest.py: fail when ptests fail on target

[Alexander Kanavin]

That's the whole point isn't it? Previously this testcase succeeded
even if some of the underlying on-target tests failed; the only way
to find out if anything was wrong was to manually inspect the logs.

Signed-off-by: Alexander Kanavin 
---
 meta/lib/oeqa/runtime/cases/ptest.py | 8 
 1 file changed, 8 insertions(+)

diff --git a/meta/lib/oeqa/runtime/cases/ptest.py 
b/meta/lib/oeqa/runtime/cases/ptest.py
index 6669e24f141..c5b8c9cb8fb 100644
--- a/meta/lib/oeqa/runtime/cases/ptest.py
+++ b/meta/lib/oeqa/runtime/cases/ptest.py
@@ -83,3 +83,11 @@ class PtestRunnerTest(OERuntimeTestCase):
 # Remove the old link to create a new one
 os.remove(ptest_log_dir_link)
 os.symlink(os.path.basename(ptest_log_dir), ptest_log_dir_link)
+
+failed_tests = {}
+for section in parse_result.result_dict:
+failed_testcases = [ test for test, result in 
parse_result.result_dict[section] if result == 'fail' ]
+if failed_testcases:
+failed_tests[section] = failed_testcases
+
+self.assertFalse(failed_tests, msg = "Failed ptests: %s" 
%(str(failed_tests)))
-- 
2.15.1

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

[OE-core] [PATCH 2/3] testimage.bbclass: add ptest to the list of runtime tests whenever possible

[Alexander Kanavin]

If no ptest packages are installed in the image, the test does nothing;
if ptest packages are installed in the image, then they should be
run without user having to enable that manually.

Signed-off-by: Alexander Kanavin 
---
 meta/classes/testimage.bbclass | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
index 7260ad4517a..3acccbb8fdb 100644
--- a/meta/classes/testimage.bbclass
+++ b/meta/classes/testimage.bbclass
@@ -44,16 +44,16 @@ DEVTESTSUITE = "gcc kernelmodule ldd"
 DEFAULT_TEST_SUITES = "${MINTESTSUITE} auto"
 DEFAULT_TEST_SUITES_pn-core-image-minimal = "${MINTESTSUITE}"
 DEFAULT_TEST_SUITES_pn-core-image-minimal-dev = "${MINTESTSUITE}"
-DEFAULT_TEST_SUITES_pn-core-image-full-cmdline = "${NETTESTSUITE} perl python 
logrotate"
+DEFAULT_TEST_SUITES_pn-core-image-full-cmdline = "${NETTESTSUITE} perl python 
logrotate ptest"
 DEFAULT_TEST_SUITES_pn-core-image-x11 = "${MINTESTSUITE}"
-DEFAULT_TEST_SUITES_pn-core-image-lsb = "${NETTESTSUITE} pam parselogs 
${RPMTESTSUITE}"
+DEFAULT_TEST_SUITES_pn-core-image-lsb = "${NETTESTSUITE} pam parselogs 
${RPMTESTSUITE} ptest"
 DEFAULT_TEST_SUITES_pn-core-image-sato = "${NETTESTSUITE} connman xorg 
parselogs ${RPMTESTSUITE} \
-${@bb.utils.contains('IMAGE_PKGTYPE', 'rpm', 'python', '', d)}"
+${@bb.utils.contains('IMAGE_PKGTYPE', 'rpm', 'python', '', d)} ptest"
 DEFAULT_TEST_SUITES_pn-core-image-sato-sdk = "${NETTESTSUITE} buildcpio 
buildlzip buildgalculator \
-connman ${DEVTESTSUITE} logrotate perl parselogs python ${RPMTESTSUITE} 
xorg"
-DEFAULT_TEST_SUITES_pn-core-image-lsb-dev = "${NETTESTSUITE} pam perl python 
parselogs ${RPMTESTSUITE}"
+connman ${DEVTESTSUITE} logrotate perl parselogs python ${RPMTESTSUITE} 
xorg ptest"
+DEFAULT_TEST_SUITES_pn-core-image-lsb-dev = "${NETTESTSUITE} pam perl python 
parselogs ${RPMTESTSUITE} ptest"
 DEFAULT_TEST_SUITES_pn-core-image-lsb-sdk = "${NETTESTSUITE} buildcpio 
buildlzip buildgalculator \
-connman ${DEVTESTSUITE} logrotate pam parselogs perl python 
${RPMTESTSUITE}"
+connman ${DEVTESTSUITE} logrotate pam parselogs perl python 
${RPMTESTSUITE} ptest"
 DEFAULT_TEST_SUITES_pn-meta-toolchain = "auto"
 
 # aarch64 has no graphics
-- 
2.15.1

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

[OE-core] [PATCH 1/3] runtime/cases/ptest.py: do not require ptest-pkgs in IMAGE_FEATURES

[Alexander Kanavin]

Doing so means that all available ptests for packages in the image
will be installed and run; some of them may be broken, never finish,
take a very long time or simply irrelevant to the user who wants to
check ptests of only a few specific packages, and does so by listing
them explicitly via IMAGE_INSTALL_append or similar.

Conversely, do not run the test if there are no ptests available.

Signed-off-by: Alexander Kanavin 
---
 meta/lib/oeqa/runtime/cases/ptest.py | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/runtime/cases/ptest.py 
b/meta/lib/oeqa/runtime/cases/ptest.py
index ec8c038a566..6669e24f141 100644
--- a/meta/lib/oeqa/runtime/cases/ptest.py
+++ b/meta/lib/oeqa/runtime/cases/ptest.py
@@ -48,9 +48,12 @@ class PtestRunnerTest(OERuntimeTestCase):
 
 @OETestID(1600)
 @skipIfNotFeature('ptest', 'Test requires ptest to be in DISTRO_FEATURES')
-@skipIfNotFeature('ptest-pkgs', 'Test requires ptest-pkgs to be in 
IMAGE_FEATURES')
 @OETestDepends(['ssh.SSHTest.test_ssh'])
 def test_ptestrunner(self):
+status, output = self.target.run('find /usr -name ptest', 0)
+if len(output) == 0:
+self.skipTest("No -ptest packages are installed in the image")
+
 import datetime
 
 test_log_dir = self.td.get('TEST_LOG_DIR', '')
-- 
2.15.1

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

Re: [OE-core] [PATCH 00/49] Consolidated pull

[Bruce Ashfield]

On Tue, Dec 19, 2017 at 8:52 PM, ChenQi  wrote:
> On 12/19/2017 10:33 PM, Bruce Ashfield wrote:
>>
>> On Tue, Dec 19, 2017 at 12:23 AM, ChenQi  wrote:
>>>
>>> On 12/19/2017 12:45 PM, Bruce Ashfield wrote:

 On Mon, Dec 18, 2017 at 11:03 AM, Ross Burton 
 wrote:
>
> Hi,
>
> Another batch of patches from the list which have passed autobuilder
> testing and
> review.
>
> Ross
>
> The following changes since commit
> d6b6508e0be4452eb285495403b73fa9fcf51e3e:
>
> temp disable inode checking on sstate (2017-12-13 14:02:02 +)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib ross/mut
>
> for you to fetch changes up to
> f64e867d1ff5e559a96f44fac8a2434ad2643502:
>
> meta-selftest: wic: Add test for --use-uuid / --fsuuid (2017-12-16
> 00:21:42 +)
>
> 
> Alejandro Hernandez (4):
> busybox: Add mkfs.EXT2 support on poky-tiny
> linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.9
> linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.12
> linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.4
>
> Alexander Kanavin (9):
> gobject-introspection: update to 1.54.1
> webkitgtk: update to 2.18.3
> psmisc: update to 23.0
> ffmpeg: update to 3.4
> devtool: add a 'latest-version' command
> devtool: provide useful defaults for version/commit when
> upgrading
> recipes
> devtool: add license checksum change handling to 'devtool
> upgrade'
> maintainers.inc: add an entry for dwarfsrcfiles
> maintainers.inc: add an entry for pkgconf
>
> Chang Rebecca Swee Fun (1):
> recipetool: create: fix conflict between SRCREV and tag
>
> Chen Qi (4):
> coreutils: upgrade to 8.28
> coreutils: add PACKAGECONFIG for single-binary
> dbus: upgrade to 1.12.2
> dbus-test: upgrade to 1.12.2


 Anyone else seeing dbus blow up during configure after this update ?

 
 Initialising tasks: 100%


 ||
 Time: 0:00:00

 NOTE: Executing SetScene Tasks

 NOTE: Executing RunQueue Tasks

 ERROR: dbus-native-1.12.2-r0 do_configure: autoreconf execution failed.

 ERROR: dbus-native-1.12.2-r0 do_configure: Function failed:
 do_configure (log file is located at


 /home/bruce/poky/build/tmp/work/x86_64-linux/dbus-native/1.12.2-r0/temp/log.do_configure.30425)

 ERROR: Logfile of failure stored in:


 /home/bruce/poky/build/tmp/work/x86_64-linux/dbus-native/1.12.2-r0/temp/log.do_configure.30425

 Log data follows:

 | DEBUG: Executing shell function autotools_preconfigure

 | DEBUG: Shell function autotools_preconfigure finished

 | DEBUG: Executing python function autotools_aclocals

 | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
 'bit-64', 'x86_64-linux', 'common']

 | DEBUG: Python function autotools_aclocals finished

 | DEBUG: Executing shell function do_configure

 | automake (GNU automake) 1.15.1

 | Copyright (C) 2017 Free Software Foundation, Inc.

 | License GPLv2+: GNU GPL version 2 or later
 

 | This is free software: you are free to change and redistribute it.

 | There is NO WARRANTY, to the extent permitted by law.

 |

 | Written by Tom Tromey 

 |and Alexandre Duret-Lutz .


 

 | autoreconf: running:


 /home/bruce/poky/build/tmp/work/x86_64-linux/dbus-native/1.12.2-r0/recipe-sysroot-native/usr/bin/autoconf


 --include=/home/bruce/poky/build/tmp/work/x86_64-linux/dbus-native/1.12.2-r0/dbus-1.12.2/m4/
 --force

 | configure.ac:95: error: Unexpanded AX_ macro found. Please install
 GNU autoconf-archive

 |   If this token and others are legitimate, please use
 m4_pattern_allow.

 |   See the Autoconf documentation.

 | configure.ac:374: error: Unexpanded AX_ macro found. Please install
 GNU autoconf-archive

 | autoreconf:

 /home/bruce/poky/build/tmp/work/x86_64-linux/dbus-native/1.12.2-r0/recipe-sysroot-native/usr/bin/autoconf
 failed with exit status: 1

 | ERROR: autoreconf execution failed.

 | WARNING: exit code 1 from a shell command.

 | 

Re: [OE-core] [PATCH RFC 00/18] EFI boot partition improvements

[Alexander Kanavin]

On 12/20/2017 12:58 AM, California Sullivan wrote:

Currently, the boot partition of an EFI system is entirely controlled by
image creation. Either done entirely through wic, or one of the
bootloader bbclasses. This is rather bad since it makes it very
difficult to add additional items to the boot partition, such as
alternative kernels, bootloaders, or other utilities, and since its not
package controlled its hard to update.


How are you planning to have this documented? You probably need to 
review the yocto manuals and see what needs to be changed or newly written.


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

Re: [OE-core] [PATCH 5/5] lib/oe/package.py: is_elf: Make it less prone to false positives

[Olof Johansson]

On 17-12-18 12:00 +, Burton, Ross wrote:
> Just pushed ross/elf with this change.  The next obvious step is to turn
> lib/oe/qa.py into a new lib/oe/elf.py which has a better API and includes
> the stripped function.

Great; I've adapted my changes on top of yours and tested it a
bit. I've published what I have on github for now, if you want to
take a look. Is this along the lines of what you want?

 https://github.com/olof/poky-contrib/compare/olof/elf
 https://github.com/olof/poky-contrib/compare/ross/elf...olof/elf

(Let me know if you prefer me to send it as draft patches to the
list instead.)

(Btw, I didn't know about Kaitai before, but I like the idea of
declarative binary parsing a lot :))

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

Re: [OE-core] [PATCHv2] cmake: Avoid passing empty prefix to os.path.relpath

[Mike Crowe]

On Monday 11 December 2017 at 13:45:26 +, Burton, Ross wrote:
> It was implicated in some build failures.  I'll re-add it and try again.

Thanks. Are the new results in? I had a poke about on autobuilder.yocto.io
but couldn't work out how to tell which builds this commit was included in.
Build 719 did not appear to include it.

Thanks.

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

Re: [OE-core] [PATCH] image_types: preserve rootfs if mkext234fs() fails

[Robert Yang]

On 12/20/2017 05:51 PM, Richard Purdie wrote:

On Tue, 2017-12-19 at 15:54 -0500, Tom Rini wrote:

On Tue, Dec 19, 2017 at 12:11:48PM -0800, Saul Wold wrote:


We have seen more failures, but have not been able to directly
reproduce
it maybe svaing the rootfs and it contains some content that is
tripping
up the e2fsprogs mkfs.ext4 populate_rootfs() function

Signed-off-by: Saul Wold 
---
  meta/classes/image_types.bbclass | 7 ++-
  1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/classes/image_types.bbclass
b/meta/classes/image_types.bbclass
index 9188bed4197..6b4f39ed274 100644
--- a/meta/classes/image_types.bbclass
+++ b/meta/classes/image_types.bbclass
@@ -86,9 +86,14 @@ oe_mkext234fs () {
    bbdebug 1 Executing "dd if=/dev/zero
of=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype
seek=$ROOTFS_SIZE count=$COUNT bs=1024"
    dd if=/dev/zero
of=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype
seek=$ROOTFS_SIZE count=$COUNT bs=1024
    bbdebug 1 "Actual Rootfs size:  `du -s ${IMAGE_ROOTFS}`"
-   bbdebug 1 "Actual Partion size: `ls -s
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype`"
+   bbdebug 1 "Actual Partion size: `ls -l
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype`"
    bbdebug 1 Executing "mkfs.$fstype -F $extra_imagecmd
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype -d
${IMAGE_ROOTFS}"
    mkfs.$fstype -F $extra_imagecmd
${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype -d
${IMAGE_ROOTFS}
+   if [ $? -ne 0 ]; then
+   tmp_saved_rootfs=`mktemp -d -p /tmp
saved_rootfs.X`
+   cp -r ${IMAGE_ROOTFS} $tmp_saved_rootfs
+   fi

Wouldn't it be better to just fail on error here, rather than dump
stuff to /tmp ?


We have a problem with a recurring issue where the image generation
code is failing in the eSDK selftests. The eSDK selftests run a
completely separate build which then gets cleaned up. I'm not entirely
sure the best way to handle this but that is why Saul is proposing
this.

It may be an idea to detect the failing selftest and then stop the
cleanup in that case. That is going to be fairly invasive on the


+1 on this, the cleanup makes the debug very hard when error happens.

// Robert


selftest code though

I may just pull this into master-next (but not master) so at least if
it fails there we have better debugging. We are struggling to get to
the bottom of the issue :(.

Cheers,

Richard



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

Re: [OE-core] [PATCH] image_types: preserve rootfs if mkext234fs() fails

[Richard Purdie]

On Tue, 2017-12-19 at 15:54 -0500, Tom Rini wrote:
> On Tue, Dec 19, 2017 at 12:11:48PM -0800, Saul Wold wrote:
> > 
> > We have seen more failures, but have not been able to directly
> > reproduce
> > it maybe svaing the rootfs and it contains some content that is
> > tripping
> > up the e2fsprogs mkfs.ext4 populate_rootfs() function
> > 
> > Signed-off-by: Saul Wold 
> > ---
> >  meta/classes/image_types.bbclass | 7 ++-
> >  1 file changed, 6 insertions(+), 1 deletion(-)
> > 
> > diff --git a/meta/classes/image_types.bbclass
> > b/meta/classes/image_types.bbclass
> > index 9188bed4197..6b4f39ed274 100644
> > --- a/meta/classes/image_types.bbclass
> > +++ b/meta/classes/image_types.bbclass
> > @@ -86,9 +86,14 @@ oe_mkext234fs () {
> >     bbdebug 1 Executing "dd if=/dev/zero
> > of=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype
> > seek=$ROOTFS_SIZE count=$COUNT bs=1024"
> >     dd if=/dev/zero
> > of=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype
> > seek=$ROOTFS_SIZE count=$COUNT bs=1024
> >     bbdebug 1 "Actual Rootfs size:  `du -s ${IMAGE_ROOTFS}`"
> > -   bbdebug 1 "Actual Partion size: `ls -s
> > ${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype`"
> > +   bbdebug 1 "Actual Partion size: `ls -l
> > ${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype`"
> >     bbdebug 1 Executing "mkfs.$fstype -F $extra_imagecmd
> > ${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype -d
> > ${IMAGE_ROOTFS}"
> >     mkfs.$fstype -F $extra_imagecmd
> > ${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.$fstype -d
> > ${IMAGE_ROOTFS}
> > +   if [ $? -ne 0 ]; then
> > +   tmp_saved_rootfs=`mktemp -d -p /tmp
> > saved_rootfs.X`
> > +   cp -r ${IMAGE_ROOTFS} $tmp_saved_rootfs
> > +   fi
> Wouldn't it be better to just fail on error here, rather than dump
> stuff to /tmp ?

We have a problem with a recurring issue where the image generation
code is failing in the eSDK selftests. The eSDK selftests run a
completely separate build which then gets cleaned up. I'm not entirely
sure the best way to handle this but that is why Saul is proposing
this.

It may be an idea to detect the failing selftest and then stop the
cleanup in that case. That is going to be fairly invasive on the
selftest code though.

I may just pull this into master-next (but not master) so at least if
it fails there we have better debugging. We are struggling to get to
the bottom of the issue :(.

Cheers,

Richard

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

[OE-core] [PATCH v2] sudo: provide sudo paths through EXTRA_OECONF

[Nikolay Merinov]

Configure script for a sudo utility trying to figure out "vardir",
"iologdir", "rundir" and "logpath" from directory structure on build
machine. If none of a standart paths present on a build machine then
variables will be set to empty string and sudo build will fail with
"Installed but not shipped" error.

Signed-off-by: Nikolay Merinov 
---
 meta/recipes-extended/sudo/sudo_1.8.21p2.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-extended/sudo/sudo_1.8.21p2.bb 
b/meta/recipes-extended/sudo/sudo_1.8.21p2.bb
index acd0025abc..cb1646359e 100644
--- a/meta/recipes-extended/sudo/sudo_1.8.21p2.bb
+++ b/meta/recipes-extended/sudo/sudo_1.8.21p2.bb
@@ -17,6 +17,10 @@ EXTRA_OECONF += " \
  ac_cv_type_rsize_t=no \
  ${@bb.utils.contains('DISTRO_FEATURES', 'pam', '--with-pam', 
'--without-pam', d)} \
  ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 
'--enable-tmpfiles.d=${libdir}/tmpfiles.d', '--disable-tmpfiles.d', d)} \
+--with-vardir=${localstatedir}/lib/sudo \
+--with-iologdir=${localstatedir}/log/sudo-io \
+--with-rundir=${localstatedir}/run/sudo \
+--with-logpath=${localstatedir}/log/sudo.log \
  "
 
 do_install_append () {
-- 
2.14.1

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

[OE-core] ✗ patchtest: failure for glibc:CVE-2017-17426

[Patchwork]

== Series Details ==

Series: glibc:CVE-2017-17426
Revision: 1
URL   : https://patchwork.openembedded.org/series/10268/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Series cannot be parsed correctly due to malformed diff 
lines [test_mbox_format] 
  Suggested fixCreate the series again using git-format-patch and ensure it 
can be applied using git am
  Diff linediff --git a/meta/recipes-core/glibc/glibc_2.26.bb 
b/meta/recipes-core/glibc/glibc_2.26.bb


* Issue Series does not apply on top of target branch 
[test_series_merge_on_head] 
  Suggested fixRebase your series on top of targeted branch
  Targeted branch  master (currently at 978472c586)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

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

[OE-core] [PATCH] glibc:CVE-2017-17426

[Huang Qiyu]

Fix the CVE-2017-17426.

Signed-off-by: Huang Qiyu 
---
 ...-overflow-in-malloc-when-tcache-is-enable.patch | 52 ++
 meta/recipes-core/glibc/glibc_2.26.bb  |  1 +
 2 files changed, 53 insertions(+)
 create mode 100644 
meta/recipes-core/glibc/glibc/0029-Fix-integer-overflow-in-malloc-when-tcache-is-enable.patch

diff --git 
a/meta/recipes-core/glibc/glibc/0029-Fix-integer-overflow-in-malloc-when-tcache-is-enable.patch
 
b/meta/recipes-core/glibc/glibc/0029-Fix-integer-overflow-in-malloc-when-tcache-is-enable.patch
new file mode 100644
index 000..623bed7
--- /dev/null
+++ 
b/meta/recipes-core/glibc/glibc/0029-Fix-integer-overflow-in-malloc-when-tcache-is-enable.patch
@@ -0,0 +1,52 @@
+From 34697694e8a93b325b18f25f7dcded55d6baeaf6 Mon Sep 17 00:00:00 2001
+From: Arjun Shankar 
+Date: Thu, 30 Nov 2017 13:31:45 +0100
+Subject: [PATCH] Fix integer overflow in malloc when tcache is enabled [BZ
+ #22375]
+
+When the per-thread cache is enabled, __libc_malloc uses request2size (which
+does not perform an overflow check) to calculate the chunk size from the
+requested allocation size. This leads to an integer overflow causing malloc
+to incorrectly return the last successfully allocated block when called with
+a very large size argument (close to SIZE_MAX).
+
+This commit uses checked_request2size instead, removing the overflow.
+
+Upstream-status: Backport
+---
+ ChangeLog   | 6 ++
+ malloc/malloc.c | 3 ++-
+ 2 files changed, 8 insertions(+), 1 deletion(-)
+
+diff --git a/ChangeLog b/ChangeLog
+index b55ed22..888f9fb 100644
+--- a/ChangeLog
 b/ChangeLog
+@@ -1,3 +1,9 @@
++2017-11-30  Arjun Shankar  
++
++  [BZ #22375]
++  * malloc/malloc.c (__libc_malloc): Use checked_request2size
++  instead of request2size.
++
+ 2017-08-02  Siddhesh Poyarekar  
+ 
+   * sysdeps/sparc/sparc32/sparcv9/fpu/multiarch/s_llrint.S
+diff --git a/malloc/malloc.c b/malloc/malloc.c
+index 79f0e9e..0c9e074 100644
+--- a/malloc/malloc.c
 b/malloc/malloc.c
+@@ -3050,7 +3050,8 @@ __libc_malloc (size_t bytes)
+ return (*hook)(bytes, RETURN_ADDRESS (0));
+ #if USE_TCACHE
+   /* int_free also calls request2size, be careful to not pad twice.  */
+-  size_t tbytes = request2size (bytes);
++  size_t tbytes;
++  checked_request2size (bytes, tbytes);
+   size_t tc_idx = csize2tidx (tbytes);
+ 
+   MAYBE_INIT_TCACHE ();
+-- 
+2.7.4
+
diff --git a/meta/recipes-core/glibc/glibc_2.26.bb 
b/meta/recipes-core/glibc/glibc_2.26.bb
index 135ec4f..36b2004 100644
--- a/meta/recipes-core/glibc/glibc_2.26.bb
+++ b/meta/recipes-core/glibc/glibc_2.26.bb
@@ -43,6 +43,7 @@ SRC_URI = "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \

file://0026-assert-Suppress-pedantic-warning-caused-by-statement.patch \
file://0027-glibc-reset-dl-load-write-lock-after-forking.patch \
file://0028-Bug-4578-add-ld.so-lock-while-fork.patch \
+   
file://0029-Fix-integer-overflow-in-malloc-when-tcache-is-enable.patch \
 "
 
 NATIVESDKFIXES ?= ""
-- 
2.7.4



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

Re: [OE-core] [PATCH RFC 01/18] fs-uuid.bbclass: rewrite get_fs_uuid function

[Martin Hundebøll]

Hi,

On 2017-12-19 23:58, California Sullivan wrote:

I couldn't find anywhere it was being used, and in trying to use it it
just spit out an error.

It now generates a random UUID and puts it in the deploy dir for
consumption.

Also use DISK_SIGNATURE_UUID for the replacement function, since that
is user-overridable.

Signed-off-by: California Sullivan 
---
  meta/classes/fs-uuid.bbclass | 32 ++--
  1 file changed, 22 insertions(+), 10 deletions(-)

diff --git a/meta/classes/fs-uuid.bbclass b/meta/classes/fs-uuid.bbclass
index 9b53dfba7ab..5a96054294e 100644
--- a/meta/classes/fs-uuid.bbclass
+++ b/meta/classes/fs-uuid.bbclass
@@ -1,16 +1,26 @@
+inherit deploy
+
  # Extract UUID from ${ROOTFS}, which must have been built
  # by the time that this function gets called. Only works
  # on ext file systems and depends on tune2fs.
  def get_rootfs_uuid(d):
-import subprocess
-rootfs = d.getVar('ROOTFS')
-output = subprocess.check_output(['tune2fs', '-l', rootfs])
-for line in output.split('\n'):
-if line.startswith('Filesystem UUID:'):
-uuid = line.split()[-1]
-bb.note('UUID of %s: %s' % (rootfs, uuid))
-return uuid
-bb.fatal('Could not determine filesystem UUID of %s' % rootfs)
+import os
+import uuid
+deploydir = d.getVar('DEPLOY_DIR_IMAGE')
+bootfs_uuid_file = deploydir + "/bootfs-uuid"


Maybe use a default assigned class variable here instead of the 
hard-coded "bootfs-uuid". The class is named "get_rootfs_uuid", so I 
would expect it to handle multiple cases.



+uuid_str = "deadbeef-dead-beef-dead-beefdeadbeef"
+if d.getVar('BUILD_REPRODUCIBLE_BINARIES', True) != "1":
+if os.path.exists(bootfs_uuid_file):
+with open(bootfs_uuid_file, "r+") as file:
+uuid_str = file.read()
+else:
+# deploydir might not exist yet...creating it here could be bad?
+if not os.path.exists(deploydir):
+os.makedirs(deploydir)
+uuid_str = str(uuid.uuid4())
+with open(bootfs_uuid_file, "w") as file:
+file.write(uuid_str)
+return uuid_str
  
  # Replace the special <> inside a string (like the

  # root= APPEND string in a syslinux.cfg or systemd-boot entry) with the
@@ -19,6 +29,8 @@ def get_rootfs_uuid(d):
  def replace_rootfs_uuid(d, string):
  UUID_PLACEHOLDER = '<>'
  if UUID_PLACEHOLDER in string:
-uuid = get_rootfs_uuid(d)
+uuid = d.getVar('DISK_SIGNATURE_UUID', True)
  string = string.replace(UUID_PLACEHOLDER, uuid)
  return string
+
+DISK_SIGNATURE_UUID ?= "${@get_rootfs_uuid(d)}"



--
MARTIN HUNDEBØLL, Prevas A/S
Software Developer

Hedeager 3, DK-8200 Aarhus N
Phone +45 87438070
Mobile +45 25562438
martin.hundeb...@prevas.dk
www.prevas.com
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core