Re: [OE-core] [PATCH v2 1/2] devtool: rework source extraction so that dependencies are handled

2017-09-13 Thread Paul Eggleton
On Thursday, 14 September 2017 4:15:11 PM NZST Paul Eggleton wrote:
> * Since we are creating (or modifying) a bbappend on the fly after the
>   initial cache load has taken place, we need to ensure that this gets
>   noticed otherwise it won't have any effect. In order to do this
>   properly with the way cooker currently works, we have to be able to
>   set its parsecache_valid flag to False. A new invalidateParseCache
>   command on the bitbake side makes this possible.

Whoops, this should have been dropped from the commit message in v2. I've 
fixed it in the branch.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH v2 2/2] devtool: ensure recipes devtool is working on are unlocked within the eSDK

2017-09-13 Thread Paul Eggleton
Alongside reworking the way devtool extracts source, we now need to
ensure that within the extensible SDK where task signatures are locked,
the signatures of the tasks for the recipes being worked on get unlocked
at the right time or otherwise we'll now get taskhash mismatches when
running devtool modify on a recipe that was included in the eSDK such as
the kernel (due to a separate bug). The existing mechanism for
auto-unlocking recipes was a little weak and was happening too late, so
I've reimplemented it so that:
(a) it gets triggered immediately when the recipe/append is created
(b) we avoid writing to the unlocked signatures file unnecessarily
(since it's a global configuration file) and
(c) within the eSDK configuration we whitelist SIGGEN_UNLOCKED_RECIPES
to avoid unnecessary reparses every time we perform one of the
devtool operations that does need to change this list.

Fixes [YOCTO #11883] (not the underlying cause, but this manifestation
of the issue).

Signed-off-by: Paul Eggleton 
---
 meta/classes/populate_sdk_ext.bbclass |  3 +++
 scripts/devtool   | 20 --
 scripts/lib/devtool/__init__.py   | 40 +++
 scripts/lib/devtool/standard.py   | 18 +---
 scripts/lib/devtool/upgrade.py|  9 +---
 5 files changed, 59 insertions(+), 31 deletions(-)

diff --git a/meta/classes/populate_sdk_ext.bbclass 
b/meta/classes/populate_sdk_ext.bbclass
index 6620445..3620995 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -346,6 +346,9 @@ python copy_buildsystem () {
 # the sig computed from the metadata.
 f.write('SIGGEN_LOCKEDSIGS_TASKSIG_CHECK = "warn"\n\n')
 
+# We want to be able to set this without a full reparse
+f.write('BB_HASHCONFIG_WHITELIST_append = " 
SIGGEN_UNLOCKED_RECIPES"\n\n')
+
 # Set up whitelist for run on install
 f.write('BB_SETSCENE_ENFORCE_WHITELIST = "%:* *:do_shared_workdir 
*:do_rm_work wic-tools:* *:do_addto_recipe_sysroot"\n\n')
 
diff --git a/scripts/devtool b/scripts/devtool
index c9ad9dd..5292f18 100755
--- a/scripts/devtool
+++ b/scripts/devtool
@@ -130,25 +130,6 @@ def read_workspace():
  'recipefile': recipefile}
 logger.debug('Found recipe %s' % workspace[pn])
 
-def create_unlockedsigs():
-""" This function will make unlocked-sigs.inc match the recipes in the
-workspace. This runs on every run of devtool, but it lets us ensure
-the unlocked items are in sync with the workspace. """
-
-confdir = os.path.join(basepath, 'conf')
-unlockedsigs = os.path.join(confdir, 'unlocked-sigs.inc')
-bb.utils.mkdirhier(confdir)
-with open(os.path.join(confdir, 'unlocked-sigs.inc'), 'w') as f:
-f.write("# DO NOT MODIFY! YOUR CHANGES WILL BE LOST.\n" +
-"# This layer was created by the OpenEmbedded devtool" +
-" utility in order to\n" +
-"# contain recipes that are unlocked.\n")
-
-f.write('SIGGEN_UNLOCKED_RECIPES += "\\\n')
-for pn in workspace:
-f.write('' + pn)
-f.write('"')
-
 def create_workspace(args, config, basepath, workspace):
 if args.layerpath:
 workspacedir = os.path.abspath(args.layerpath)
@@ -332,7 +313,6 @@ def main():
 
 if not getattr(args, 'no_workspace', False):
 read_workspace()
-create_unlockedsigs()
 
 try:
 ret = args.func(args, config, basepath, workspace)
diff --git a/scripts/lib/devtool/__init__.py b/scripts/lib/devtool/__init__.py
index 14170cb..94e3d7d 100644
--- a/scripts/lib/devtool/__init__.py
+++ b/scripts/lib/devtool/__init__.py
@@ -297,3 +297,43 @@ def replace_from_file(path, old, new):
 except ValueError:
 pass
 write_file(path, "\n".join(new_contents))
+
+
+def update_unlockedsigs(basepath, workspace, fixed_setup, extra=None):
+""" This function will make unlocked-sigs.inc match the recipes in the
+workspace plus any extras we want unlocked. """
+
+if not fixed_setup:
+# Only need to write this out within the eSDK
+return
+
+if not extra:
+extra = []
+
+confdir = os.path.join(basepath, 'conf')
+unlockedsigs = os.path.join(confdir, 'unlocked-sigs.inc')
+
+# Get current unlocked list if any
+values = {}
+def get_unlockedsigs_varfunc(varname, origvalue, op, newlines):
+values[varname] = origvalue
+return origvalue, None, 0, True
+if os.path.exists(unlockedsigs):
+with open(unlockedsigs, 'r') as f:
+bb.utils.edit_metadata(f, ['SIGGEN_UNLOCKED_RECIPES'], 
get_unlockedsigs_varfunc)
+unlocked = sorted(values.get('SIGGEN_UNLOCKED_RECIPES', []))
+
+# If the new list is different to the current list, write it out
+newunlocked = sorted(list(workspace.keys()) + extra)
+if unlocked != newu

[OE-core] [PATCH v2 1/2] devtool: rework source extraction so that dependencies are handled

2017-09-13 Thread Paul Eggleton
Since it was first implemented, devtool's source extraction (as used by
the devtool modify, extract and upgrade subcommands) ignored other recipe
dependencies - so for example if you ran devtool modify on a recipe that
fetches from svn or is compressed using xz then it would fail if those
dependencies hadn't been built first. Now that we can execute tasks in
the normal way (i.e. tinfoil.build_targets()) then we can rework it to
use that. This is slightly tricky in that the source extraction needs to
insert some logic in between tasks; luckily we can use a helper class
that conditionally adds prefuncs to make that possible.

Some side-effects / aspects of this change worth noting:
* Operations are a little slower because we have to go through the task
  dependency graph generation and other startup processing. There's not
  really any way to avoid this though.
* devtool extract didn't used to require a workspace, now it does
  because it needs to create a temporary bbappend for the recipe. (As
  with other commands the workspace be created on the fly if it doesn't
  already exist.)
* Since we are creating (or modifying) a bbappend on the fly after the
  initial cache load has taken place, we need to ensure that this gets
  noticed otherwise it won't have any effect. In order to do this
  properly with the way cooker currently works, we have to be able to
  set its parsecache_valid flag to False. A new invalidateParseCache
  command on the bitbake side makes this possible.
* I want any existing sysroot files and stamps to be left alone during
  extraction since we are running the tasks off to the side, and
  especially devtool extract should be able to be used without touching
  these. However, this was hampered by the automatic removal process in
  sstate.bbclass triggered by bb.event.ReachableStamps when the task
  signatures change, thus I had to introduce a way to disable this
  removal on a per-recipe basis (we still want it to function for any
  dependencies that we aren't working on). To implement this I elected
  to use a file written to tmp/sstate-control which gets deleted
  automatically after reading so that there's less chance of stale files
  affecting future sessions. I could have used a variable but this would
  have needed to be whitelisted and I'd have to have poked its value in
  using the setVariable command.

Fixes [YOCTO #11198].

Signed-off-by: Paul Eggleton 
---
 meta/classes/devtool-source.bbclass | 165 +
 meta/classes/sstate.bbclass |   9 +-
 meta/lib/oeqa/selftest/cases/devtool.py |  10 +-
 scripts/lib/devtool/standard.py | 209 ++--
 scripts/lib/devtool/upgrade.py  |   2 +-
 5 files changed, 242 insertions(+), 153 deletions(-)
 create mode 100644 meta/classes/devtool-source.bbclass

diff --git a/meta/classes/devtool-source.bbclass 
b/meta/classes/devtool-source.bbclass
new file mode 100644
index 000..8f5bc86
--- /dev/null
+++ b/meta/classes/devtool-source.bbclass
@@ -0,0 +1,165 @@
+# Development tool - source extraction helper class
+#
+# NOTE: this class is intended for use by devtool and should not be
+# inherited manually.
+#
+# Copyright (C) 2014-2017 Intel Corporation
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+
+DEVTOOL_TEMPDIR ?= ""
+DEVTOOL_PATCH_SRCDIR = "${DEVTOOL_TEMPDIR}/patchworkdir"
+
+
+python() {
+tempdir = d.getVar('DEVTOOL_TEMPDIR')
+
+if not tempdir:
+bb.fatal('devtool-source class is for internal use by devtool only')
+
+# Make a subdir so we guard against WORKDIR==S
+workdir = os.path.join(tempdir, 'workdir')
+d.setVar('WORKDIR', workdir)
+if not d.getVar('S').startswith(workdir):
+# Usually a shared workdir recipe (kernel, gcc)
+# Try to set a reasonable default
+if bb.data.inherits_class('kernel', d):
+d.setVar('S', '${WORKDIR}/source')
+else:
+d.setVar('S', '${WORKDIR}/%s' % os.path.basename(d.getVar('S')))
+if bb.data.inherits_class('kernel', d):
+# We don't want to move the source to STAGING_KERNEL_DIR here
+d.setVar('STAGING_KERNEL_DIR', '${S}')
+
+d.setVar('STAMPS_DIR', os.path.join(tempdir, 'stamps'))
+d.setVar('T', os.path.join(tempdir, 'temp'))
+
+# Hook in pre/postfuncs
+is_kernel_yocto = bb.data.inherits_class('kernel-yocto', d)
+if is

[OE-core] [PATCH v2 0/2] A couple of devtool fixes

2017-09-13 Thread Paul Eggleton
A fix for devtool modify and other source extracting subcommands to
handle dependencies, and a fix for devtool modify within the eSDK.

NOTE: the patch I just sent to the bitbake list to fix a bug in the way
empty directory notifications should be merged prior to merging this
series.

Changes since v1:
* Drop the invalidateParseCache command call since I have sent a fix
  for the bug that caused it to be required.


The following changes since commit 2ebbeb61114e4b847e9164c621ac87b5cf03a299:

  staging: gracefully abort if two recipes conflict in the sysroot (2017-09-11 
17:30:15 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/devtool30-oe
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/devtool30-oe

Paul Eggleton (2):
  devtool: rework source extraction so that dependencies are handled
  devtool: ensure recipes devtool is working on are unlocked within the eSDK

 meta/classes/devtool-source.bbclass | 165 
 meta/classes/populate_sdk_ext.bbclass   |   3 +
 meta/classes/sstate.bbclass |   9 +-
 meta/lib/oeqa/selftest/cases/devtool.py |  10 +-
 scripts/devtool |  20 ---
 scripts/lib/devtool/__init__.py |  40 ++
 scripts/lib/devtool/standard.py | 217 ++--
 scripts/lib/devtool/upgrade.py  |   9 +-
 8 files changed, 295 insertions(+), 178 deletions(-)
 create mode 100644 meta/classes/devtool-source.bbclass

-- 
2.9.5

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


Re: [OE-core] [PATCH 1/2] devtool: rework source extraction so that dependencies are handled

2017-09-13 Thread Paul Eggleton
On Tuesday, 12 September 2017 10:18:38 PM NZST Paul Eggleton wrote:
> +tinfoil.run_command('invalidateParseCache')

This was only needed due to a bitbake bug that I have sent a fix for, so I'm
about to send a v2 for this series that omits this call.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] ✗ patchtest: failure for at-spi2-atk: Add HOMEPAGE info into recipe file. (rev5)

2017-09-13 Thread Patchwork
== Series Details ==

Series: at-spi2-atk: Add HOMEPAGE info into recipe file. (rev5)
Revision: 5
URL   : https://patchwork.openembedded.org/series/8840/
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 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 583dca290c)



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] -> ...).

---
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] ✗ patchtest: failure for at-spi2-atk: Add HOMEPAGE info into recipe file. (rev4)

2017-09-13 Thread Patchwork
== Series Details ==

Series: at-spi2-atk: Add HOMEPAGE info into recipe file. (rev4)
Revision: 4
URL   : https://patchwork.openembedded.org/series/8840/
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 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 583dca290c)



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] -> ...).

---
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] at-spi2-atk: Add HOMEPAGE info into recipe file.

2017-09-13 Thread Huang Qiyu
Signed-off-by: Huang Qiyu 
---
 meta/recipes-support/atk/at-spi2-atk_2.24.1.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/atk/at-spi2-atk_2.24.1.bb 
b/meta/recipes-support/atk/at-spi2-atk_2.24.1.bb
index ac55081..4a0e411 100644
--- a/meta/recipes-support/atk/at-spi2-atk_2.24.1.bb
+++ b/meta/recipes-support/atk/at-spi2-atk_2.24.1.bb
@@ -1,4 +1,5 @@
 SUMMARY = "AT-SPI 2 Toolkit Bridge"
+HOMEPAGE = "https://wiki.linuxfoundation.org/accessibility/d-bus";
 LICENSE = "LGPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=e9f288ba982d60518f375b5898283886"
 
-- 
2.7.4



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


[OE-core] [PATCH] blktrace: Add HOMEPAGE info into recipe file.

2017-09-13 Thread Huang Qiyu
Signed-off-by: Huang Qiyu 
---
 meta/recipes-kernel/blktrace/blktrace_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-kernel/blktrace/blktrace_git.bb 
b/meta/recipes-kernel/blktrace/blktrace_git.bb
index 957cb70..770575f 100644
--- a/meta/recipes-kernel/blktrace/blktrace_git.bb
+++ b/meta/recipes-kernel/blktrace/blktrace_git.bb
@@ -1,4 +1,5 @@
 SUMMARY = "Generates traces of I/O traffic on block devices"
+HOMEPAGE = "http://brick.kernel.dk/snaps/";
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
 
-- 
2.7.4



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


[OE-core] [PATCH] at-spi2-core: Add HOMEPAGE info into recipe file.

2017-09-13 Thread Huang Qiyu
Signed-off-by: Huang Qiyu 
---
 meta/recipes-support/atk/at-spi2-core_2.24.1.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/atk/at-spi2-core_2.24.1.bb 
b/meta/recipes-support/atk/at-spi2-core_2.24.1.bb
index b5b71e7..1687ae3 100644
--- a/meta/recipes-support/atk/at-spi2-core_2.24.1.bb
+++ b/meta/recipes-support/atk/at-spi2-core_2.24.1.bb
@@ -1,4 +1,5 @@
 SUMMARY = "Assistive Technology Service Provider Interface (dbus core)"
+HOMEPAGE = "https://wiki.linuxfoundation.org/accessibility/d-bus";
 LICENSE = "LGPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=e9f288ba982d60518f375b5898283886"
 
-- 
2.7.4



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


[OE-core] [PATCH] libgudev: Add HOMEPAGE info into recipe file.

2017-09-13 Thread Huang Qiyu
Signed-off-by: Huang Qiyu 
---
 meta/recipes-gnome/libgudev/libgudev_231.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-gnome/libgudev/libgudev_231.bb 
b/meta/recipes-gnome/libgudev/libgudev_231.bb
index ae0f1c7..ad67926 100644
--- a/meta/recipes-gnome/libgudev/libgudev_231.bb
+++ b/meta/recipes-gnome/libgudev/libgudev_231.bb
@@ -1,5 +1,5 @@
 SUMMARY = "GObject wrapper for libudev"
-
+HOMEPAGE = "https://wiki.gnome.org/Projects/libgudev";
 SRC_URI[archive.md5sum] = "916c10c51ec61131e244c3936bbb2e0c"
 SRC_URI[archive.sha256sum] = 
"3b1ef99d4a8984c35044103d8ddfc3cc52c80035c36abab2bcc5e3532e063f96"
 
-- 
2.7.4



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


[OE-core] ✗ patchtest: failure for kexec-tools: Update to 2.0.15

2017-09-13 Thread Patchwork
== Series Details ==

Series: kexec-tools: Update to 2.0.15
Revision: 1
URL   : https://patchwork.openembedded.org/series/8885/
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 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 583dca290c)



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] -> ...).

---
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] kexec-tools: Update to 2.0.15

2017-09-13 Thread Megha Dey
Starting with 4.12 kernels, kexec-tools cannot load a crash kernel
because ELF core parsing fails with errors like:

  Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type.
  Please report this as bug. Using RANGE_RESERVED now.
  ...
  ELF core (kcore) parse failed
  Cannot load /vmlinuz

The issue is fixed upstream in kexec-tools 2.0.15.

This patch updates to the latest version of the kexec-tools and
removes patches which are already merged upstream.

Signed-off-by: Megha Dey 
---
 ...nd-the-semantics-of-kexec_iomem_for_each_.patch |  78 --
 .../0001-vmcore-dmesg-Define-_GNU_SOURCE.patch |  31 -
 ...01-x86-x86_64-Fix-format-warning-with-die.patch |  78 --
 ...eneralize-and-rename-get_kernel_stext_sym.patch | 194 -
 .../0002-ppc-Fix-format-warning-with-die.patch |  43 --
 ...0003-arm64-identify-PHYS_OFFSET-correctly.patch |  76 --
 .../0004-arm64-kdump-identify-memory-regions.patch | 202 --
 ...5-arm64-kdump-add-elf-core-header-segment.patch | 191 -
 ...6-arm64-kdump-set-up-kernel-image-segment.patch | 137 
 .../0007-arm64-kdump-set-up-other-segments.patch   |  35 -
 ...-add-DT-properties-to-crash-dump-kernel-s.patch | 150 
 ...-kdump-Add-support-for-binary-image-files.patch |  52 --
 .../kexec/kexec-tools/kexec-aarch64.patch  | 801 -
 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb|  48 --
 meta/recipes-kernel/kexec/kexec-tools_2.0.15.bb|  36 +
 15 files changed, 36 insertions(+), 2116 deletions(-)
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0001-vmcore-dmesg-Define-_GNU_SOURCE.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0001-x86-x86_64-Fix-format-warning-with-die.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0002-ppc-Fix-format-warning-with-die.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch
 delete mode 100644 
meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch
 delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/kexec-aarch64.patch
 delete mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb
 create mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.15.bb

diff --git 
a/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
 
b/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
deleted file mode 100644
index 822f28c..000
--- 
a/meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
+++ /dev/null
@@ -1,78 +0,0 @@
-From 02eed0f8f2748fd7579f69e5373445b52b2b8754 Mon Sep 17 00:00:00 2001
-From: AKASHI Takahiro 
-Date: Mon, 17 Oct 2016 13:56:58 +0900
-Subject: [PATCH 1/9] kexec: exntend the semantics of kexec_iomem_for_each_line
-
-The current kexec_iomem_for_each_line() counts up all the lines for which
-a callback function returns zero(0) or positive, and otherwise it stops
-further scanning.
-This behavior is incovenient in some cases. For instance, on arm64, we want
-to count up "System RAM" entries, but need to skip "reserved" entries.
-
-So this patch extends the semantics so that we will continue to scan
-succeeding entries but not count lines for which a callback function
-returns positive.
-
-The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
-be affected by this change because
-* arm
-  The callback function only returns -1 or 0, and the return value of
-  kexec_iomem_for_each_line() will never be used.
-* sh, x86
-  The callback function may return (-1 for sh,) 0 or 1, but always returns
-  1 once we have reached the maximum number of entries allowed.
-  Even so the current kexec_iomem_for_each_line() counts them up.
-  This change actually fixes this bug.
-
-Upstream-Status: Backport 
[https://git.linaro.org/people/takahiro.akashi/kexec-tools.git]
-
-Signed-off-by: AKASHI Takahiro 
-Signed-off-by: He Zhe 

- kexec/kexec-iomem.c | 15 ++-
- 1 file changed, 10 insertions(+), 5 deletions(-)
-
-diff --git a/kexec/kexec-iomem.c b/kexec/kexec-iomem.c
-index 485a2e8..0a0277a 100644
---

[OE-core] [PATCH v2] linux-firmware: bump to latest linux-firmware git revision

2017-09-13 Thread California Sullivan
From: Stefan Agner 

This requires MD5 sum updates for
- LICENSE.QualcommAtheros_ath10k: year change
- WHENCE: various version updates and addition of new firmwares

The new firmware for Qualcom Venus causes a QA error:
  QA Issue: linux-firmware: Recipe inherits the allarch class, but has packaged 
architecture-specific binaries

Since firmware typically do not run on the CPU, the architecture of
the firmware file is independent from the CPU architecture the image
will be running on. Disable the QA check for the linux-firmware
package by default.

Signed-off-by: Stefan Agner 
Signed-off-by: California Sullivan 
---
Hi Stefan,
In interest of getting this into 2.4 (freezes Monday, and it turns out
we also need this latest bump), I went ahead and fixed it up as per
Ross' suggestion. Ross was quick and already added the required
functionality to INSANE_SKIP.

If this isn't acceptable please let me know.

Thanks,
Cal

 meta/recipes-kernel/linux-firmware/linux-firmware_git.bb | 11 ++-
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb 
b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
index 20d140c..6798ace 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
@@ -98,7 +98,7 @@ LIC_FILES_CHKSUM = "\
 file://LICENCE.qla1280;md5=d6895732e622d950609093223a2c4f5d \
 file://LICENCE.qla2xxx;md5=505855e921b75f1be4a437ad9b79dff0 \
 file://LICENSE.QualcommAtheros_ar3k;md5=b5fe244fb2b532311de1472a3bc06da5 \
-file://LICENSE.QualcommAtheros_ath10k;md5=b5fe244fb2b532311de1472a3bc06da5 
\
+file://LICENSE.QualcommAtheros_ath10k;md5=cb42b686ee5f5cb890275e4321db60a8 
\
 file://LICENCE.r8a779x_usb3;md5=4c1671656153025d7076105a5da7e498 \
 file://LICENSE.radeon;md5=68ec28bacb3613200bca44f404c69b16 \
 
file://LICENCE.ralink_a_mediatek_company_firmware;md5=728f1a85fd53fd67fa8d7afb080bc435
 \
@@ -114,7 +114,7 @@ LIC_FILES_CHKSUM = "\
 file://LICENCE.xc4000;md5=0ff51d2dc49fce04814c9155081092f0 \
 file://LICENCE.xc5000;md5=1e170c13175323c32c7f4d0998d53f66 \
 file://LICENCE.xc5000c;md5=12b02efa3049db65d524aeb418dd87ca \
-file://WHENCE;md5=ad12d0618287e8c10ae3da05fa0edcfb \
+file://WHENCE;md5=08f6d4371353cac5f6fc271d5407c63e \
 "
 
 # These are not common licenses, set NO_GENERIC_LICENSE for them
@@ -175,7 +175,7 @@ NO_GENERIC_LICENSE[Firmware-xc5000] = "LICENCE.xc5000"
 NO_GENERIC_LICENSE[Firmware-xc5000c] = "LICENCE.xc5000c"
 NO_GENERIC_LICENSE[WHENCE] = "WHENCE"
 
-SRCREV = "b14134583c2a15d4404695f72cb523daedb877ab"
+SRCREV = "a61ac5cf8374edbfe692d12f805a1b194f7fead2"
 PE = "1"
 PV = "0.0+git${SRCPV}"
 
@@ -744,5 +744,6 @@ python populate_packages_prepend () {
 d.appendVar('RDEPENDS_linux-firmware-ibt', ' ' + ' '.join(ibt_pkgs))
 }
 
-# Netronome binaries has ELF headers and therefore triggers an arch-specific 
error.
-INSANE_SKIP_${PN}-netronome = "arch"
+# Firmware files are generally not ran on the CPU, so they can be
+# allarch despite being architecture specific
+INSANE_SKIP = "arch"
-- 
2.9.5

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


Re: [OE-core] [PATCH v2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES

2017-09-13 Thread Mark Hatle
On 9/13/17 5:40 PM, Mark Hatle wrote:
> If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the
> packages.bbclass.  This made it difficult for a recipe or layer to 'append'
> to the default.
> 
> Copy the default into the bitbake.conf, allowing future _append and += style
> actions.
> 
> Default was remove from package.bbclass.  If a value is not set, only the
> built-in per fixes will be used.

per should have been 'perms' above.  I can send a v3 if needed.

--Mark

> Signed-off-by: Mark Hatle 
> ---
>  meta/classes/package.bbclass | 4 +---
>  meta/conf/bitbake.conf   | 8 
>  2 files changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> index 7a62181..2053d46 100644
> --- a/meta/classes/package.bbclass
> +++ b/meta/classes/package.bbclass
> @@ -737,9 +737,7 @@ python fixup_perms () {
>  def get_fs_perms_list(d):
>  str = ""
>  bbpath = d.getVar('BBPATH')
> -fs_perms_tables = d.getVar('FILESYSTEM_PERMS_TABLES')
> -if not fs_perms_tables:
> -fs_perms_tables = 'files/fs-perms.txt' if 
> oe.types.boolean(d.getVar('VOLATILE_LOG_DIR', True)) else 
> 'files/fs-perms-persistent-log.txt'
> +fs_perms_tables = d.getVar('FILESYSTEM_PERMS_TABLES') or ""
>  for conf_file in fs_perms_tables.split():
>  str += " %s" % bb.utils.which(bbpath, conf_file)
>  return str
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 444c53f..8fb596e 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -330,6 +330,14 @@ FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE', 
> False))}"
>  # This default was only used for checking
>  FILESEXTRAPATHS ?= "__default:"
>  
> +# The default list of fs-perms files to process.  If the list is empty only
> +# the builtin definitions will be used.  Builtin definitions included:
> +#  base_prefix, prefix, exec_prefix, base_bindir, base_sbindir, base_libdir,
> +#  datadir, sysconfdir, servicedir, sharedstatedir, localstatedir, infodir,
> +#  mandir, docdir, bindir, sbindir, libexecdir, libdir, includedir and
> +#  oldincludedir
> +FILESYSTEM_PERMS_TABLES ?= "${@'files/fs-perms.txt' if 
> oe.types.boolean(d.getVar('VOLATILE_LOG_DIR', True)) else 
> 'files/fs-perms-persistent-log.txt'}"
> +
>  ##
>  # General work and output directories for the build system.
>  ##
> 

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


[OE-core] [PATCH v2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES

2017-09-13 Thread Mark Hatle
If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the
packages.bbclass.  This made it difficult for a recipe or layer to 'append'
to the default.

Copy the default into the bitbake.conf, allowing future _append and += style
actions.

Default was remove from package.bbclass.  If a value is not set, only the
built-in per fixes will be used.

Signed-off-by: Mark Hatle 
---
 meta/classes/package.bbclass | 4 +---
 meta/conf/bitbake.conf   | 8 
 2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 7a62181..2053d46 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -737,9 +737,7 @@ python fixup_perms () {
 def get_fs_perms_list(d):
 str = ""
 bbpath = d.getVar('BBPATH')
-fs_perms_tables = d.getVar('FILESYSTEM_PERMS_TABLES')
-if not fs_perms_tables:
-fs_perms_tables = 'files/fs-perms.txt' if 
oe.types.boolean(d.getVar('VOLATILE_LOG_DIR', True)) else 
'files/fs-perms-persistent-log.txt'
+fs_perms_tables = d.getVar('FILESYSTEM_PERMS_TABLES') or ""
 for conf_file in fs_perms_tables.split():
 str += " %s" % bb.utils.which(bbpath, conf_file)
 return str
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 444c53f..8fb596e 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -330,6 +330,14 @@ FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE', 
False))}"
 # This default was only used for checking
 FILESEXTRAPATHS ?= "__default:"
 
+# The default list of fs-perms files to process.  If the list is empty only
+# the builtin definitions will be used.  Builtin definitions included:
+#  base_prefix, prefix, exec_prefix, base_bindir, base_sbindir, base_libdir,
+#  datadir, sysconfdir, servicedir, sharedstatedir, localstatedir, infodir,
+#  mandir, docdir, bindir, sbindir, libexecdir, libdir, includedir and
+#  oldincludedir
+FILESYSTEM_PERMS_TABLES ?= "${@'files/fs-perms.txt' if 
oe.types.boolean(d.getVar('VOLATILE_LOG_DIR', True)) else 
'files/fs-perms-persistent-log.txt'}"
+
 ##
 # General work and output directories for the build system.
 ##
-- 
1.8.3.1

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


Re: [OE-core] [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log

2017-09-13 Thread Martin Jansa
OK, thanks.

Any insights to the first issue described in commit message? That we know
that is an Actual Problem, but hard to reproduce it.

I'm rebuilding one component over and over again and with pseudo 1.8.1 I
got this issue in 5 rebuilds from 1000, now in the same build with latest
pseudo 1.8.2 backported from oe-core/master I got this issue only 2 times
in 1000 iterations.

Hopefully this insane check will help discover similar issues even without
triggering the QA host-user-contamination check, so that we can detect such
issues even without really trying (it's now included in my regular "bitbake
world" builds which quite often trigger this QA host-user-contamination
issue in glibc-locale. And now we can correlate that with pseudo.log more
easily.

On Thu, Sep 14, 2017 at 12:08 AM, Seebs  wrote:

> On Wed, 13 Sep 2017 22:50:32 +0200
> Martin Jansa  wrote:
>
> > inode mismatch:
> > '/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/
> systemd/1_234-r0/recipe-sysroot/etc/group'
> > ino 29361846 in db, 29361904 in request.
>
> Just to be clear about this:
>
> This is at least potentially an Actual Problem. It's probably not a
> good idea to habitually ignore these. A thing like this happening means
> that, at some point:
>
> 1. Something created etc/group, and it got inode 29361846 recorded in
> the database.
> 2. Something deleted etc/group, and did NOT record this to the database.
> 3. Something created etc/group, with inode 29361904.
>
> It's possible that the thing creating etc/group didn't record it to the
> database, and something else just referred to it later (like a stat
> call), or that this was generated by the request creating the entry.
>
> Either way, it means changes were made to a pseudo-managed hunk of
> filesystem without pseudo knowing about it, and that is generally bad.
>
> -s
> --
> ___
> 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] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log

2017-09-13 Thread Seebs
On Wed, 13 Sep 2017 22:50:32 +0200
Martin Jansa  wrote:

> inode mismatch:
> '/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot/etc/group'
> ino 29361846 in db, 29361904 in request.

Just to be clear about this:

This is at least potentially an Actual Problem. It's probably not a
good idea to habitually ignore these. A thing like this happening means
that, at some point:

1. Something created etc/group, and it got inode 29361846 recorded in
the database.
2. Something deleted etc/group, and did NOT record this to the database.
3. Something created etc/group, with inode 29361904.

It's possible that the thing creating etc/group didn't record it to the
database, and something else just referred to it later (like a stat
call), or that this was generated by the request creating the entry.

Either way, it means changes were made to a pseudo-managed hunk of
filesystem without pseudo knowing about it, and that is generally bad.

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


Re: [OE-core] [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log

2017-09-13 Thread Seebs
On Wed, 13 Sep 2017 22:46:59 +0200
Martin Jansa  wrote:

>   And some-other-unrelated-file is really some different file, not
> just hardlink to the same file from some different directory (like
> between WORKDIR and sysroot other "path mismatch" entries show).

To clarify a thing: In practice, "path mismatch" with links > 1 is
probably harmless. I think I had a patch floating around to stop
alerting about it except when being paranoid.

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


Re: [OE-core] [PATCH] systemd: Fix rootfs transaction error when PACKAGECONFIG has polkit

2017-09-13 Thread Martin Jansa
Yes, you're right it shouldn't use passwd/group from host.

I've tried to reproduce it in different build directory and now I see that
it properly adds polkitd user in do_prepare_recipe_sysroot task already:
OE @ ~ $ tail -n 15
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/temp/log.do_prepare_recipe_sysroot
DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
'bit-64', 'x86_64-linux', 'common']
DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
'bit-64', 'x86_64-linux', 'common']
DEBUG: Executing shell function useradd_sysroot
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot-native/usr/sbin/useradd
Running groupadd commands...
NOTE: systemd: Performing groupadd with [--root
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot
-r lock]
NOTE: systemd: Performing groupadd with [--root
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot
-r systemd-journal]
Running useradd commands...
NOTE: systemd: Performing useradd with [--root
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot
   --system -d / -M --shell /bin/nologin systemd-timesync]
NOTE: systemd: Performing useradd with [--root
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot
--system -d / -M --shell /bin/nologin systemd-network]
NOTE: systemd: Performing useradd with [--root
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot
 --system -d / -M --shell /bin/nologin systemd-resolve]
NOTE: systemd: Performing useradd with [--root
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot
--system --no-create-home --user-group --home-dir /etc/polkit-1 polkitd]
NOTE: systemd: Performing useradd with [--root
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot
 --system -d / -M --shell /bin/nologin systemd-bus-proxy]
DEBUG: Shell function useradd_sysroot finished
DEBUG: Python function useradd_sysroot_sstate finished

tomorrow I'll try to reproduce it in the directory where it failed before,
my guess is that in that build do_prepare_recipe_sysroot wasn't re-executed
correctly and unlike here:
OE @ ~ $ grep -R polkitd
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot/etc
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot/etc/group:polkitd:!:994:
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot/etc/group-:polkitd:!:994:
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot/etc/passwd-:polkitd:!:996:994::/etc/polkit-1:
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd/1_234-r0/recipe-sysroot/etc/passwd:polkitd:!:996:994::/etc/polkit-1:

or there might be another issue in pseudo or something like that.

Thanks


On Wed, Sep 13, 2017 at 2:40 PM, Jason Wessel 
wrote:

> It should work because it has nothing to do with that particular passwd
> file.   This is builds successfully on a ubuntu 16.04 host which has no
> polkitd user.
>
> Also with the user add stanza in the patch it should be adding the user
> that is required when PACKAGECONFIG has the polkitd added to the psuedo
> passwd file.   We have quite a few configurations building properly.  Where
> I have seen transient failures before is when the -native sysroot does not
> get rebuilt but that is typically with other recipes.
>
> Is this still a problem?
>
>
> Jason.
>
>
> On 09/06/2017 01:35 PM, Martin Jansa wrote:
>
> Does this work on hosts without polkitd user?
>
> Here it failed with:
>
> | chown: invalid user: ‘polkitd:root’
>
>
>
>
>
>
> On Tue, Aug 15, 2017 at 8:55 PM, Jason Wessel 
> wrote:
>
>> The systemd 234 added some files to the polkit directory and the
>> directory the files live in must be owned by the polkitd user, else
>> you will receive the following error when the rootfs is being
>> assembled:
>>
>> Error: Transaction check error:
>>   file /usr/share/polkit-1/rules.d conflicts between attempted installs
>> of polkit-0.113-r0.15.core2_64 and systemd-1:234-r0.0.core2_64
>>
>> The fix similar to other packages such as libvirt where the user must
>> exist and the directory must be created with the proper attributes.
>>
>> Signed-off-by: Jason Wessel 
>> ---
>>  meta/recipes-core/systemd/systemd_234.bb | 9 +
>>  1 file changed, 9 insertions(+)
>>
>> diff --git a/meta/recipes-core/systemd/systemd_234.bb
>> b/meta/recipes-core/systemd/systemd_234.bb
>> index ad7fc99b90..4560cf4175 100644
>> --- a/meta/recipes-core/systemd/systemd_234.bb
>> +++ b/meta/recipes-core/systemd/systemd_234.bb
>> @@ -245,6 +245,14 @@ do_install() {
>> ln -s ../run/systemd/resolve/resolv.conf
>> ${D}${sysconfdir}/resolv-conf.systemd
>> fi
>> install -Dm 0755 ${S}/src/systemctl/systemd-sysv-install.SKELETON
>> ${D}${systemd_unitdir}/systemd-sysv-insta

Re: [OE-core] [PATCH] glib-2.0: recommend shared-mime-info

2017-09-13 Thread Richard Purdie
On Wed, 2017-09-13 at 14:12 -0700, Alistair Francis wrote:
> On Wed, Sep 13, 2017 at 2:09 PM, Richard Purdie
>  wrote:
> > 
> > On Wed, 2017-09-13 at 13:55 -0700, Alistair Francis wrote:
> > > 
> > > On Wed, Sep 13, 2017 at 1:42 PM, Burton, Ross  > > com>
> > > wrote:
> > > > 
> > > > 
> > > > Can you share a log showing that?
> > > This is the full log, so it's not just OpenSSL:
> > I suspect the new dependency means other things get built on mingw
> > which have never been needed until now. We may need to remove the
> > dependency for mingw to avoid this..
> Yeah, that is what I suspected. I tried the BAD_RECOMMENDATIONS in
> the
> mingw machine-sdk conf, but that didn't seem to work.

You want something like:

RRECOMMENDS_${PN}_remove_mingw32_pn-glib-2.0 = "shared-mime-info"

(I don't remember the exact mingw override offhand)

Cheers,

Richard

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


Re: [OE-core] [PATCH] glib-2.0: recommend shared-mime-info

2017-09-13 Thread Alistair Francis
On Wed, Sep 13, 2017 at 2:09 PM, Richard Purdie
 wrote:
> On Wed, 2017-09-13 at 13:55 -0700, Alistair Francis wrote:
>> On Wed, Sep 13, 2017 at 1:42 PM, Burton, Ross 
>> wrote:
>> >
>> > Can you share a log showing that?
>> This is the full log, so it's not just OpenSSL:
>
> I suspect the new dependency means other things get built on mingw
> which have never been needed until now. We may need to remove the
> dependency for mingw to avoid this..

Yeah, that is what I suspected. I tried the BAD_RECOMMENDATIONS in the
mingw machine-sdk conf, but that didn't seem to work.

Thanks,
Alistair

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


Re: [OE-core] [PATCH] glib-2.0: recommend shared-mime-info

2017-09-13 Thread Richard Purdie
On Wed, 2017-09-13 at 13:55 -0700, Alistair Francis wrote:
> On Wed, Sep 13, 2017 at 1:42 PM, Burton, Ross 
> wrote:
> > 
> > Can you share a log showing that?
> This is the full log, so it's not just OpenSSL:

I suspect the new dependency means other things get built on mingw
which have never been needed until now. We may need to remove the
dependency for mingw to avoid this...

Cheers,

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


Re: [OE-core] [RFC][PATCH] WIP: qemu: enable sdl2 virglrenderer gtk+ spice

2017-09-13 Thread Martin Jansa
On Wed, Sep 13, 2017 at 10:48:05PM +0200, Martin Jansa wrote:
> On Wed, Sep 13, 2017 at 10:46:47PM +0200, Martin Jansa wrote:
> > * this is only for test
> > * it should be enabled in some distro layer which prefers extra
> >   native dependencies for virglrenderer and enables meta-pyton
> >   for spice
> > * cannot enable gtk+ for native builds, because there is no gtk+3-native
> 
> ignore this one, sending last patch but from wrong branch.

[Patchwork-Status: Rejected]

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


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


Re: [OE-core] [U-Boot] [PATCH] u-boot: Upgrade to 2017.09

2017-09-13 Thread Otavio Salvador
Marek,

On Wed, Sep 13, 2017 at 5:20 PM, Marek Vasut  wrote:
> On 09/13/2017 10:11 PM, Otavio Salvador wrote:
>> On Wed, Sep 13, 2017 at 5:05 PM, Marek Vasut  wrote:
>> ...
>>> What is the status of those dangling patches ? They were apparently
>>> posted, but didn't make it into the last two (?) releases.
>>
>> I am confused. Are you asking for U-Boot community or OE community?
>
> How does that matter ? I am asking about the status of those patches and
> why they didn't make it upstream yet. Something should be done about that.
>
> Automated update of the U-Boot recipe version is great and all, but
> that's not all that should be done when new version is released . The
> outstanding patches need to be rechecked every now and then too so they
> get upstream and don't start piling up in OE core.

You are the maintainer, so step up and do it. I did the upgrade as I
had it here for testing so I thought it would be good to send it.

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


[OE-core] ✗ patchtest: failure for WIP: qemu: enable sdl2 virglrenderer gtk+ spice

2017-09-13 Thread Patchwork
== Series Details ==

Series: WIP: qemu: enable sdl2 virglrenderer gtk+ spice
Revision: 1
URL   : https://patchwork.openembedded.org/series/8880/
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 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 de70799af1)



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] -> ...).

---
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 1/1] oe-selftest: devtool: fix test_devtool_add hanging on some machines

2017-09-13 Thread Paul Eggleton
The code in scriptutils which implements the logic for running the
editor used by devtool edit-recipe looks at the VISUAL environment
variable before EDITOR, and thus if VISUAL is set in the environment it
will override the EDITOR value we are setting here, the editor (usually
vim) launches and there's nothing to stop it running forever short of
manually killing it. Set VISUAL instead to fix this.

Apparently VISUAL is in fact the variable we should really be preferring
here - I don't think I knew that but somehow I got it right in the code,
just not in the test. Here are the details for the curious:

  
https://unix.stackexchange.com/questions/4859/visual-vs-editor-whats-the-difference

Fixes [YOCTO #12074].

Signed-off-by: Paul Eggleton 
---
 meta/lib/oeqa/selftest/cases/devtool.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/cases/devtool.py 
b/meta/lib/oeqa/selftest/cases/devtool.py
index d5d0918..1dfef59 100644
--- a/meta/lib/oeqa/selftest/cases/devtool.py
+++ b/meta/lib/oeqa/selftest/cases/devtool.py
@@ -216,7 +216,7 @@ class DevtoolTests(DevtoolBase):
 result = runCmd('devtool -q find-recipe %s' % pn)
 self.assertEqual(recipepath, result.output.strip())
 # Test devtool edit-recipe
-result = runCmd('EDITOR="echo 123" devtool -q edit-recipe %s' % pn)
+result = runCmd('VISUAL="echo 123" devtool -q edit-recipe %s' % pn)
 self.assertEqual('123 %s' % recipepath, result.output.strip())
 # Clean up anything in the workdir/sysroot/sstate cache (have to do 
this *after* devtool add since the recipe only exists then)
 bitbake('%s -c cleansstate' % pn)
-- 
2.9.5

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


[OE-core] [PATCH 0/1] oe-selftest: devtool: fix test_devtool_add hanging on some machines

2017-09-13 Thread Paul Eggleton
The following changes since commit de70799af1a8bfe2fac22b90401053275d4714ba:

  image_types: support lz4 compressed squashfs (2017-09-12 23:54:43 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib 
paule/devtool-edit-recipe-selftest-fix
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/devtool-edit-recipe-selftest-fix

Paul Eggleton (1):
  oe-selftest: devtool: fix test_devtool_add hanging on some machines

 meta/lib/oeqa/selftest/cases/devtool.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.9.5

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


Re: [OE-core] [PATCH 2/2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES

2017-09-13 Thread Richard Purdie
On Wed, 2017-09-13 at 13:42 -0500, Mark Hatle wrote:
> On 9/13/17 12:57 PM, Otavio Salvador wrote:
> > 
> > On Wed, Sep 13, 2017 at 12:15 PM, Mark Hatle  > 
> > Couldn't package.bbclass one to be dropped?
> > 
> > 
> Yes, I didn't do it at present because I was worried it could affect
> someone and
> it's after feature freeze.
> 
> If RP is not concerned about this, I can create a V2 that also
> removes the piece
> of package.bbclass.

I'm ok with this.

Cheers,

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


Re: [OE-core] [PATCH] glib-2.0: recommend shared-mime-info

2017-09-13 Thread Alistair Francis
On Wed, Sep 13, 2017 at 1:42 PM, Burton, Ross  wrote:
> Can you share a log showing that?

This is the full log, so it's not just OpenSSL:

alistai@xsjalistai50:/scratch/alistai/yocto/oe-master/build (master)*$
SDKMACHINE="x86_64-mingw32" bitbake buildtools-tarball
Loading cache: 100%
|###|
Time: 0:00:00
Loaded 2759 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.35.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "ubuntu-17.04"
TARGET_SYS= "i586-oe-linux"
MACHINE   = "qemux86"
DISTRO= "nodistro"
DISTRO_VERSION= "nodistro.0"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta  = "master:de70799af1a8bfe2fac22b90401053275d4714ba"
meta-xilinx   = "master:74a0d90e52cca346d05a69bbd628c6ec9e49fbcb"
meta-oe
meta-python
meta-networking   = "master:8b991640f19f1d19b17db141c31bc56e26695a23"
meta-virtualization = "master:ba35378ce5e24f2bfcb85caa806774b873983d9f"
meta-mingw= "master:52515d8bee445d728d5fe63bfcbca79b5d8ea250"

Initialising tasks: 100%
|##|
Time: 0:00:01
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: nativesdk-openssl-1.0.2l-r0 do_configure: Function failed:
do_configure (log file is located at
/scratch/alistai/yocto/oe-master/build/tmp-glibc/work/x86_64-nativesdk-mingw32-oesdk-mingw32/nativesdk-openssl/1.0.2l-r0/temp/log.do_configure.14481)
ERROR: Logfile of failure stored in:
/scratch/alistai/yocto/oe-master/build/tmp-glibc/work/x86_64-nativesdk-mingw32-oesdk-mingw32/nativesdk-openssl/1.0.2l-r0/temp/log.do_configure.14481
Log data follows:
| DEBUG: Executing shell function do_configure
| Usage: Configure [no- ...] [enable- ...]
[experimental- ...] [-Dxxx] [-lxxx] [-Lxxx] [-fxxx] [-Kxxx]
[no-hw-xxx|no-hw] [[no-]threads] [[no-]shared]
[[no-]zlib|zlib-dynamic] [no-asm] [no-dso] [no-krb5] [sctp] [386]
[--prefix=DIR] [--openssldir=OPENSSLDIR] [--with-xxx[=vvv]]
[--test-sanity] os/compiler[:flags]
|
| pick os/compiler from:
| BC-32 BS2000-OSD BSD-generic32 BSD-generic64 BSD-ia64 BSD-sparc64 BSD-sparcv8
| BSD-x86 BSD-x86-elf BSD-x86_64 Cygwin Cygwin-x86_64 DJGPP MPE/iX-gcc OS2-EMX
| OS390-Unix QNX6 QNX6-i386 ReliantUNIX SINIX SINIX-N UWIN VC-CE VC-WIN32
| VC-WIN64A VC-WIN64I aix-cc aix-gcc aix3-cc aix64-cc aix64-gcc android
| android-armv7 android-mips android-x86 aux3-gcc beos-x86-bone beos-x86-r5
| bsdi-elf-gcc cc cray-j90 cray-t3e darwin-i386-cc darwin-ppc-cc darwin64-ppc-cc
| darwin64-x86_64-cc debian-alpha debian-alpha-ev4 debian-alpha-ev5 debian-amd64
| debian-arm64 debian-armel debian-armhf debian-avr32 debian-hppa
| debian-hurd-i386 debian-i386 debian-i386-i486 debian-i386-i586
| debian-i386-i686/cmov debian-ia64 debian-kfreebsd-amd64 debian-kfreebsd-i386
| debian-m32r debian-m68k debian-mips debian-mips64 debian-mips64el
| debian-mipsel debian-mipsn32 debian-mipsn32el debian-netbsd-i386
| debian-netbsd-m68k debian-netbsd-sparc debian-openbsd-alpha
| debian-openbsd-i386 debian-openbsd-mips debian-or1k debian-powerpc
| debian-powerpcspe debian-ppc64 debian-ppc64el debian-s390 debian-s390x
| debian-sh3 debian-sh3eb debian-sh4 debian-sh4eb debian-sparc debian-sparc-v8
| debian-sparc-v9 debian-sparc64 debian-x32 dgux-R3-gcc dgux-R4-gcc
| dgux-R4-x86-gcc dist gcc hpux-cc hpux-gcc hpux-ia64-cc hpux-ia64-gcc
| hpux-parisc-cc hpux-parisc-cc-o4 hpux-parisc-gcc hpux-parisc1_1-cc
| hpux-parisc1_1-gcc hpux-parisc2-cc hpux-parisc2-gcc hpux64-ia64-cc
| hpux64-ia64-gcc hpux64-parisc2-cc hpux64-parisc2-gcc hurd-x86 iphoneos-cross
| irix-cc irix-gcc irix-mips3-cc irix-mips3-gcc irix64-mips4-cc irix64-mips4-gcc
| linux-aarch64 linux-alpha+bwx-ccc linux-alpha+bwx-gcc linux-alpha-ccc
| linux-alpha-gcc linux-aout linux-armv4 linux-avr32 linux-elf linux-elf-arm
| linux-elf-armeb linux-generic32 linux-generic64 linux-gnueabi-arm
| linux-gnueabi-armeb linux-ia32-icc linux-ia64 linux-ia64-icc linux-mips
| linux-mips32 linux-mips64 linux-mips64el linux-mipsel linux-musleabi-arm
| linux-musleabi-armeb linux-ppc linux-ppc64 linux-ppc64le linux-sparcv8
| linux-sparcv9 linux-x32 linux-x86_64 linux-x86_64-clang linux-x86_64-icc
| linux32-s390x linux64-mips64 linux64-s390x linux64-sparcv9 mingw mingw64
| ncr-scde netware-clib netware-clib-bsdsock netware-clib-bsdsock-gcc
| netware-clib-gcc netware-libc netware-libc-bsdsock netware-libc-bsdsock-gcc
| netware-libc-gcc newsos4-gcc nextstep nextstep3.3 osf1-alpha-cc osf1-alpha-gcc
| purify qnx4 rhapsody-ppc-cc sco5-cc sco5-gcc solaris-sparcv7-cc
| solaris-sparcv7-gcc solaris-sparcv8-cc solaris-sparcv8-gcc solaris-sparcv9-cc
| solaris-sparcv9-gcc solaris-x86-cc solaris-x86-gcc solaris64-sparcv9-cc
| solaris64-sparcv9-gcc solaris64-x86_64-cc solaris64-x86_64-gcc sunos-gcc
| tandem-c89 tru64-alpha-cc uClinux-dist uClinux-dist64 ultrix

Re: [OE-core] [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log

2017-09-13 Thread Martin Jansa
On Wed, Sep 13, 2017 at 10:46:59PM +0200, Martin Jansa wrote:
> * we often see QA warnings like:
>   glibc-locale-2.26: glibc-locale: 
> /glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT is owned 
> by uid 3004, which is the same as the user running bitbake. This may be due 
> to host contamination [host-user-contaminated]
>   glibc-locale-2.26: glibc-locale: 
> /glibc-binary-localedata-nn-no.iso-8859-1/usr/lib/locale/nn_NO.ISO-8859-1/LC_MEASUREMENT
>  is owned by uid 3004, which is the same as the user running bitbake. This 
> may be due to host contamination [host-user-contaminated]
>   but we don't know the root cause of it.
> * the only theory we currently have is that it's a bug in pseudo when
>   inode is being reused for different files, which is supported by
>   pseudo.log entries:
> 
>   Good build:
>   pseudo$ grep -v "^path mismatch" pseudo.log
>   debug_logfile: fd 2
>   pid 7975 [parent 7974], doing new pid setup and server start
>   Setup complete, sending SIGUSR1 to pid 7974.
>   db cleanup for server shutdown, 17:33:58.787
>   memory-to-file backup complete, 17:33:58.787.
>   db cleanup finished, 17:33:58.787
> 
>   Build with QA host-user-contaminated issue:
>   ERROR: foo-1.0.0-r0 do_package_qa: QA Issue: foo: file-with-wrong-UID is 
> owned
>   by uid 2001, which is the same as the user running bitbake. This may be due 
> to
>   host contamination [host-user-contaminated]
> 
>   pseudo$ grep "file-with-wrong-UID" pseudo.log
>   inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in 
> request.
>   creat ignored for existing file 'file-with-wrong-UID'.
>   inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in 
> request.
>   inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in 
> request.
>   inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in 
> request.
>   inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in 
> request.
>   inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in 
> request.
>   inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in 
> request.
>   path mismatch [1 link]: ino 13242270 db 'file-with-wrong-UID' req 
> 'some-other-unrelated-file'.
>   creat for 'some-other-unrelated-file' replaces existing 13242270 
> ['file-with-wrong-UID'].
>   db cleanup for server shutdown, 02:16:23.685
>   memory-to-file backup complete, 02:16:23.685.
>   db cleanup finished, 02:16:23.685
> 
>   And some-other-unrelated-file is really some different file, not just 
> hardlink
>   to the same file from some different directory (like between WORKDIR and 
> sysroot
>   other "path mismatch" entries show).
> 
> Signed-off-by: Martin Jansa 
> ---
>  meta/classes/insane.bbclass | 40 
>  1 file changed, 40 insertions(+)
> 
> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
> index 78b41caf99..617bf7011d 100644
> --- a/meta/classes/insane.bbclass
> +++ b/meta/classes/insane.bbclass
> @@ -1237,6 +1237,41 @@ python do_qa_unpack() {
>  bb.warn('%s: the directory %s (%s) pointed to by the S variable 
> doesn\'t exist - please set S within the recipe to point to where the source 
> has been unpacked to' % (d.getVar('PN'), d.getVar('S', False), s_dir))
>  }
>  
> +python do_qa_pseudo() {
> +
> ###
> +# Check pseudo.log for unexpected errors
> +#
> +# Typical pseudo.log contains many "^path mismatch" lines for all the 
> hardlinked files
> +# e.g. in some smaller component I see 231/237 lines to be "^path 
> mismatch" other 6
> +# lines are setup and cleanup lines like this:
> +# debug_logfile: fd 2
> +# pid 7975 [parent 7974], doing new pid setup and server start
> +# Setup complete, sending SIGUSR1 to pid 7974.
> +# db cleanup for server shutdown, 17:33:58.787
> +# memory-to-file backup complete, 17:33:58.787.
> +# db cleanup finished, 17:33:58.787
> +#
> +# but if there is one of:
> +# "^inode mismatch"
> +# "^creat ignored for existing file"
> +# "^creat for.*replaces existing"
> +# then there might be some bigger issue which sometimes results in 
> host-user-contaminated QA warnings
> +
> ###
> +
> +import subprocess
> +
> +pseudodir = d.getVar('PSEUDO_LOCALSTATEDIR')
> +bb.note("Checking pseudo.log for common errors")
> +pseudolog = os.path.join(pseudodir, "pseudo.log")
> +statement = "grep" \
> +" -e '^inode mismatch'" \
> +" -e '^creat ignored for existing file'" \
> +" -e '^creat for.*replaces existing'" \
> +" %s" % pseudolog
> +if subprocess.call("%s -q" % statement, shell=True) == 0:
> +bb.fatal("This %s indicates errors, see %s or grep -v '^path 
> mismatch' %s" % (pseudolog, statement, pseudolog))
> +}
> +
>  # 

Re: [OE-core] [RFC][PATCH] WIP: qemu: enable sdl2 virglrenderer gtk+ spice

2017-09-13 Thread Martin Jansa
On Wed, Sep 13, 2017 at 10:46:47PM +0200, Martin Jansa wrote:
> * this is only for test
> * it should be enabled in some distro layer which prefers extra
>   native dependencies for virglrenderer and enables meta-pyton
>   for spice
> * cannot enable gtk+ for native builds, because there is no gtk+3-native

ignore this one, sending last patch but from wrong branch.

> Signed-off-by: Martin Jansa 
> ---
>  meta/recipes-devtools/qemu/qemu.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-devtools/qemu/qemu.inc 
> b/meta/recipes-devtools/qemu/qemu.inc
> index e0b8647e88..ddf4c63edd 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -75,10 +75,10 @@ do_install_append() {
>  # END of qemu-mips workaround
>  
>  PACKAGECONFIG ??= " \
> - fdt sdl kvm \
> + fdt sdl sdl2 virglrenderer kvm \
>   ${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
>   "
> -PACKAGECONFIG_class-native ??= "fdt alsa kvm"
> +PACKAGECONFIG_class-native ??= "fdt alsa kvm sdl sdl2 virglrenderer"
>  PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
>  
>  # Handle distros such as CentOS 5 32-bit that do not have kvm support
> -- 
> 2.14.1
> 

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


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


[OE-core] [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log

2017-09-13 Thread Martin Jansa
* we often see QA warnings like:
  glibc-locale-2.26: glibc-locale: 
/glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT is owned by 
uid 3004, which is the same as the user running bitbake. This may be due to 
host contamination [host-user-contaminated]
  glibc-locale-2.26: glibc-locale: 
/glibc-binary-localedata-nn-no.iso-8859-1/usr/lib/locale/nn_NO.ISO-8859-1/LC_MEASUREMENT
 is owned by uid 3004, which is the same as the user running bitbake. This may 
be due to host contamination [host-user-contaminated]
  but we don't know the root cause of it.
* the only theory we currently have is that it's a bug in pseudo when
  inode is being reused for different files, which is supported by
  pseudo.log entries:

  Good build:
  pseudo$ grep -v "^path mismatch" pseudo.log
  debug_logfile: fd 2
  pid 7975 [parent 7974], doing new pid setup and server start
  Setup complete, sending SIGUSR1 to pid 7974.
  db cleanup for server shutdown, 17:33:58.787
  memory-to-file backup complete, 17:33:58.787.
  db cleanup finished, 17:33:58.787

  Build with QA host-user-contaminated issue:
  ERROR: foo-1.0.0-r0 do_package_qa: QA Issue: foo: file-with-wrong-UID is owned
  by uid 2001, which is the same as the user running bitbake. This may be due to
  host contamination [host-user-contaminated]

  pseudo$ grep "file-with-wrong-UID" pseudo.log
  inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
  creat ignored for existing file 'file-with-wrong-UID'.
  inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
  inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
  inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
  inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
  inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
  inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
  path mismatch [1 link]: ino 13242270 db 'file-with-wrong-UID' req 
'some-other-unrelated-file'.
  creat for 'some-other-unrelated-file' replaces existing 13242270 
['file-with-wrong-UID'].
  db cleanup for server shutdown, 02:16:23.685
  memory-to-file backup complete, 02:16:23.685.
  db cleanup finished, 02:16:23.685

  And some-other-unrelated-file is really some different file, not just hardlink
  to the same file from some different directory (like between WORKDIR and 
sysroot
  other "path mismatch" entries show).

Signed-off-by: Martin Jansa 
---
 meta/classes/insane.bbclass | 40 
 1 file changed, 40 insertions(+)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index 78b41caf99..617bf7011d 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -1237,6 +1237,41 @@ python do_qa_unpack() {
 bb.warn('%s: the directory %s (%s) pointed to by the S variable 
doesn\'t exist - please set S within the recipe to point to where the source 
has been unpacked to' % (d.getVar('PN'), d.getVar('S', False), s_dir))
 }
 
+python do_qa_pseudo() {
+###
+# Check pseudo.log for unexpected errors
+#
+# Typical pseudo.log contains many "^path mismatch" lines for all the 
hardlinked files
+# e.g. in some smaller component I see 231/237 lines to be "^path 
mismatch" other 6
+# lines are setup and cleanup lines like this:
+# debug_logfile: fd 2
+# pid 7975 [parent 7974], doing new pid setup and server start
+# Setup complete, sending SIGUSR1 to pid 7974.
+# db cleanup for server shutdown, 17:33:58.787
+# memory-to-file backup complete, 17:33:58.787.
+# db cleanup finished, 17:33:58.787
+#
+# but if there is one of:
+# "^inode mismatch"
+# "^creat ignored for existing file"
+# "^creat for.*replaces existing"
+# then there might be some bigger issue which sometimes results in 
host-user-contaminated QA warnings
+###
+
+import subprocess
+
+pseudodir = d.getVar('PSEUDO_LOCALSTATEDIR')
+bb.note("Checking pseudo.log for common errors")
+pseudolog = os.path.join(pseudodir, "pseudo.log")
+statement = "grep" \
+" -e '^inode mismatch'" \
+" -e '^creat ignored for existing file'" \
+" -e '^creat for.*replaces existing'" \
+" %s" % pseudolog
+if subprocess.call("%s -q" % statement, shell=True) == 0:
+bb.fatal("This %s indicates errors, see %s or grep -v '^path mismatch' 
%s" % (pseudolog, statement, pseudolog))
+}
+
 # The Staging Func, to check all staging
 #addtask qa_staging after do_populate_sysroot before do_build
 do_populate_sysroot[postfuncs] += "do_qa_staging "
@@ -1249,6 +1284,11 @@ do_configure[postfuncs] += "do_qa_configure "
 # Check does S exist.
 do_unpack[postfuncs] += "do_qa_unpack"
 
+# Check pseudo.log 

[OE-core] [RFC][PATCH] WIP: qemu: enable sdl2 virglrenderer gtk+ spice

2017-09-13 Thread Martin Jansa
* this is only for test
* it should be enabled in some distro layer which prefers extra
  native dependencies for virglrenderer and enables meta-pyton
  for spice
* cannot enable gtk+ for native builds, because there is no gtk+3-native

Signed-off-by: Martin Jansa 
---
 meta/recipes-devtools/qemu/qemu.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index e0b8647e88..ddf4c63edd 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -75,10 +75,10 @@ do_install_append() {
 # END of qemu-mips workaround
 
 PACKAGECONFIG ??= " \
-   fdt sdl kvm \
+   fdt sdl sdl2 virglrenderer kvm \
${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
"
-PACKAGECONFIG_class-native ??= "fdt alsa kvm"
+PACKAGECONFIG_class-native ??= "fdt alsa kvm sdl sdl2 virglrenderer"
 PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
 
 # Handle distros such as CentOS 5 32-bit that do not have kvm support
-- 
2.14.1

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


Re: [OE-core] [PATCH] glib-2.0: recommend shared-mime-info

2017-09-13 Thread Burton, Ross
Can you share a log showing that?

On 13 September 2017 at 21:07, Alistair Francis 
wrote:

> On Tue, Sep 5, 2017 at 8:08 AM, Ross Burton  wrote:
> > Large portions of GIO are not that useful without the MIME database.
> Add a
> > recommends to shared-mime-info so that GIO works out of the box, but can
> be
> > removed (using BAD_RECOMMENDATIONS) if shared-mime-info is too large and
> isn't
> > required.
> >
> > [ YOCTO #11792 ]
> >
> > Signed-off-by: Ross Burton 
>
> This patch breaks openSSL compilation when cross compiling with MinGW.
>
> Investigating the issue more at the moment.
>
> Thanks,
> Alistair
>
> > ---
> >  meta/recipes-core/glib-2.0/glib.inc | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-core/glib-2.0/glib.inc
> b/meta/recipes-core/glib-2.0/glib.inc
> > index d6ef4dfc0b0..ce15ccefc39 100644
> > --- a/meta/recipes-core/glib-2.0/glib.inc
> > +++ b/meta/recipes-core/glib-2.0/glib.inc
> > @@ -73,6 +73,8 @@ FILES_${PN}-codegen = "${datadir}/glib-2.0/codegen/*.py
> \
> > ${bindir}/gdbus-codegen"
> >  FILES_${PN}-utils = "${bindir}/*"
> >
> > +RRECOMMENDS_${PN} += "shared-mime-info"
> > +
> >  ARM_INSTRUCTION_SET_armv4 = "arm"
> >  ARM_INSTRUCTION_SET_armv5 = "arm"
> >  # Valgrind runtime detection works using hand-written assembly, which
> > --
> > 2.11.0
> >
> > --
> > ___
> > 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] [U-Boot] [PATCH] u-boot: Upgrade to 2017.09

2017-09-13 Thread Otavio Salvador
On Wed, Sep 13, 2017 at 5:05 PM, Marek Vasut  wrote:
...
> What is the status of those dangling patches ? They were apparently
> posted, but didn't make it into the last two (?) releases.

I am confused. Are you asking for U-Boot community or OE community?

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


Re: [OE-core] [PATCH] qemu: upgrade to version 2.10.0

2017-09-13 Thread Martin Jansa
BTW: I've just noticed that this upgrade goes backwards again as QA
warnings show:

qemu-2.10.0: Package version for package qemu-dbg went backwards which
would break package feeds from (0:2.10.0-rc2-r0.0 to 0:2.10.0-r0.0)
[version-going-backwards]
qemu-2.10.0: Package version for package qemu-dbg went backwards which
would break package feeds from (0:2.10.0-rc2-r0.1 to 0:2.10.0-r0.0)
[version-going-backwards]
qemu-2.10.0: Package version for package qemu-dev went backwards which
would break package feeds from (0:2.10.0-rc2-r0.0 to 0:2.10.0-r0.0)
[version-going-backwards]
qemu-2.10.0: Package version for package qemu-dev went backwards which
would break package feeds from (0:2.10.0-rc2-r0.1 to 0:2.10.0-r0.0)
[version-going-backwards]
qemu-2.10.0: Package version for package qemu-doc went backwards which
would break package feeds from (0:2.10.0-rc2-r0.0 to 0:2.10.0-r0.0)
[version-going-backwards]
qemu-2.10.0: Package version for package qemu-doc went backwards which
would break package feeds from (0:2.10.0-rc2-r0.1 to 0:2.10.0-r0.0)
[version-going-backwards]
qemu-2.10.0: Package version for package qemu-locale went backwards
which would break package feeds from (0:2.10.0-rc2-r0.0 to
0:2.10.0-r0.0) [version-going-backwards]
qemu-2.10.0: Package version for package qemu-locale went backwards
which would break package feeds from (0:2.10.0-rc2-r0.1 to
0:2.10.0-r0.0) [version-going-backwards]
qemu-2.10.0: Package version for package qemu-ptest went backwards
which would break package feeds from (0:2.10.0-rc2-r0.0 to
0:2.10.0-r0.0) [version-going-backwards]
qemu-2.10.0: Package version for package qemu-ptest went backwards
which would break package feeds from (0:2.10.0-rc2-r0.1 to
0:2.10.0-r0.0) [version-going-backwards]
qemu-2.10.0: Package version for package qemu-staticdev went backwards
which would break package feeds from (0:2.10.0-rc2-r0.0 to
0:2.10.0-r0.0) [version-going-backwards]
qemu-2.10.0: Package version for package qemu-staticdev went backwards
which would break package feeds from (0:2.10.0-rc2-r0.1 to
0:2.10.0-r0.0) [version-going-backwards]
qemu-2.10.0: Package version for package qemu went backwards which
would break package feeds from (0:2.10.0-rc2-r0.0 to 0:2.10.0-r0.0)
[version-going-backwards]
qemu-2.10.0: Package version for package qemu went backwards which
would break package feeds from (0:2.10.0-rc2-r0.1 to 0:2.10.0-r0.0)
[version-going-backwards]



On Wed, Sep 13, 2017 at 4:15 PM, Burton, Ross  wrote:

> On 13 September 2017 at 15:12, Martin Jansa 
> wrote:
>
>> On Fri, Sep 01, 2017 at 01:44:56PM +0200, Martin Jansa wrote:
>> > I don't know how accelerated GL will be in the end, but this commit:
>> > https://git.qemu.org/?p=qemu.git;a=commitdiff;h=474114b7305c
>> c1be7c2ee8ba5267be159a9d56e3
>> > made it possible.
>> >
>> > I've built qemu with my Gentoo host with virgl and spice support, and I
>> > plan to try how fast it goes.
>>
>> I've some WIP changes to build qemu-native with virglrenderer enabled in:
>> http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu
>>
>> and few more to enable spice as well in:
>> http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/spice
>
>
> Awesome. Can't wait to see how it performs.
>
> Ross
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] glib-2.0: recommend shared-mime-info

2017-09-13 Thread Alistair Francis
On Tue, Sep 5, 2017 at 8:08 AM, Ross Burton  wrote:
> Large portions of GIO are not that useful without the MIME database.  Add a
> recommends to shared-mime-info so that GIO works out of the box, but can be
> removed (using BAD_RECOMMENDATIONS) if shared-mime-info is too large and isn't
> required.
>
> [ YOCTO #11792 ]
>
> Signed-off-by: Ross Burton 

This patch breaks openSSL compilation when cross compiling with MinGW.

Investigating the issue more at the moment.

Thanks,
Alistair

> ---
>  meta/recipes-core/glib-2.0/glib.inc | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-core/glib-2.0/glib.inc 
> b/meta/recipes-core/glib-2.0/glib.inc
> index d6ef4dfc0b0..ce15ccefc39 100644
> --- a/meta/recipes-core/glib-2.0/glib.inc
> +++ b/meta/recipes-core/glib-2.0/glib.inc
> @@ -73,6 +73,8 @@ FILES_${PN}-codegen = "${datadir}/glib-2.0/codegen/*.py \
> ${bindir}/gdbus-codegen"
>  FILES_${PN}-utils = "${bindir}/*"
>
> +RRECOMMENDS_${PN} += "shared-mime-info"
> +
>  ARM_INSTRUCTION_SET_armv4 = "arm"
>  ARM_INSTRUCTION_SET_armv5 = "arm"
>  # Valgrind runtime detection works using hand-written assembly, which
> --
> 2.11.0
>
> --
> ___
> 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] [morty][PATCH] kernel.bbclass: fix KERNEL_IMAGETYPE(S) for Image.gz

2017-09-13 Thread Nicolas Dechesne
KERNEL_IMAGETYPES lists all the kernel images that we want to build. in
cb17b6c2a7 (kernel.bbclass: support kernel image type of vmlinux.gz), some logic
was added to support vmlinux.gz which is not a target built by kernel
makefiles (only vmlinux). It is clear that the goal of this logic is only to
support vmlinux.gz and not others compressed format (such as Image.gz) which are
valid target for kernel makefiles.

For Image.gz we should rely on the kernel makefiles and not do the compression
in kernel class.

This patch updates the logic used to filter out non supported kernel target from
KERNEL_IMAGETYPES, and make vmlinux.gz a 'special case', instead of *.gz. If
more special cases are needed in the future, we could add them in a similar way.

This patch should be a no-op for anyone using vmlinux or vmlinux.gz, and on top
of that it is fixing the build for Image.gz which was not working until now.

Signed-off-by: Nicolas Dechesne 
Signed-off-by: Richard Purdie 
(cherry picked from commit cfc0c897656fe67e81a6a5dcd936dff785529f41)
Signed-off-by: Nicolas Dechesne 
---
 meta/classes/kernel.bbclass | 18 +-
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index eefe574a60..f8318b83a1 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -28,7 +28,6 @@ KERNEL_VERSION_PKG_NAME = 
"${@legitimize_package_name(d.getVar('KERNEL_VERSION',
 KERNEL_VERSION_PKG_NAME[vardepvalue] = "${LINUX_VERSION}"
 
 python __anonymous () {
-import re
 
 # Merge KERNEL_IMAGETYPE and KERNEL_ALT_IMAGETYPE into KERNEL_IMAGETYPES
 type = d.getVar('KERNEL_IMAGETYPE', True) or ""
@@ -40,7 +39,10 @@ python __anonymous () {
 types = (alttype + ' ' + types).strip()
 d.setVar('KERNEL_IMAGETYPES', types)
 
-typeformake = re.sub(r'\.gz', '', types)
+# some commonly used kernel images aren't generated by the kernel build 
system, such as vmlinux.gz
+# typeformake lists only valid kernel make targets, and post processing 
can be done after the kernel
+# is built (such as using gzip to compress vmlinux)
+typeformake = types.replace('vmlinux.gz', 'vmlinux')
 d.setVar('KERNEL_IMAGETYPE_FOR_MAKE', typeformake)
 
 for type in types.split():
@@ -262,14 +264,12 @@ kernel_do_compile() {
fi
for typeformake in ${KERNEL_IMAGETYPE_FOR_MAKE} ; do
oe_runmake ${typeformake} CC="${KERNEL_CC}" LD="${KERNEL_LD}" 
${KERNEL_EXTRA_ARGS} $use_alternate_initrd
-   for type in ${KERNEL_IMAGETYPES} ; do
-   if test "${typeformake}.gz" = "${type}"; then
-   mkdir -p "${KERNEL_OUTPUT_DIR}"
-   gzip -9c < "${typeformake}" > 
"${KERNEL_OUTPUT_DIR}/${type}"
-   break;
-   fi
-   done
done
+   # vmlinux.gz is not built by kernel
+   if (echo "${KERNEL_IMAGETYPES}" | grep -wq "vmlinux\.gz"); then
+   mkdir -p "${KERNEL_OUTPUT_DIR}"
+   gzip -9c < ${B}/vmlinux > "${KERNEL_OUTPUT_DIR}/vmlinux.gz"
+   fi
 }
 
 do_compile_kernelmodules() {
-- 
2.11.0

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


[OE-core] [PATCH] bluez5: fix out-of-bounds access in SDP server (CVE-2017-1000250)

2017-09-13 Thread Ross Burton
All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an
information disclosure vulnerability which allows remote attackers to obtain
sensitive information from the bluetoothd process memory. This vulnerability
lies in the processing of SDP search attribute requests.

Signed-off-by: Ross Burton 
---
 meta/recipes-connectivity/bluez5/bluez5.inc|  1 +
 .../bluez5/bluez5/cve-2017-1000250.patch   | 34 ++
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch

diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc 
b/meta/recipes-connectivity/bluez5/bluez5.inc
index 527e4033fe6..2ae4553d489 100644
--- a/meta/recipes-connectivity/bluez5/bluez5.inc
+++ b/meta/recipes-connectivity/bluez5/bluez5.inc
@@ -50,6 +50,7 @@ SRC_URI = "\
 ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '', 
'file://0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch', d)} \
 file://0001-tests-add-a-target-for-building-tests-without-runnin.patch \
 file://0001-hciattach-bcm43xx-fix-the-delay-timer-for-firmware-d.patch \
+file://cve-2017-1000250.patch \
 "
 S = "${WORKDIR}/bluez-${PV}"
 
diff --git a/meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch 
b/meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch
new file mode 100644
index 000..9fac961bcf6
--- /dev/null
+++ b/meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch
@@ -0,0 +1,34 @@
+All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an
+information disclosure vulnerability which allows remote attackers to obtain
+sensitive information from the bluetoothd process memory. This vulnerability
+lies in the processing of SDP search attribute requests.
+
+CVE: CVE-2017-1000250
+Upstream-Status: Backport
+Signed-off-by: Ross Burton 
+
+From 9e009647b14e810e06626dde7f1bb9ea3c375d09 Mon Sep 17 00:00:00 2001
+From: Luiz Augusto von Dentz 
+Date: Wed, 13 Sep 2017 10:01:40 +0300
+Subject: sdp: Fix Out-of-bounds heap read in service_search_attr_req function
+
+Check if there is enough data to continue otherwise return an error.
+---
+ src/sdpd-request.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/sdpd-request.c b/src/sdpd-request.c
+index 1eefdce..318d044 100644
+--- a/src/sdpd-request.c
 b/src/sdpd-request.c
+@@ -917,7 +917,7 @@ static int service_search_attr_req(sdp_req_t *req, 
sdp_buf_t *buf)
+   } else {
+   /* continuation State exists -> get from cache */
+   sdp_buf_t *pCache = sdp_get_cached_rsp(cstate);
+-  if (pCache) {
++  if (pCache && cstate->cStateValue.maxBytesSent < 
pCache->data_size) {
+   uint16_t sent = MIN(max, pCache->data_size - 
cstate->cStateValue.maxBytesSent);
+   pResponse = pCache->data;
+   memcpy(buf->data, pResponse + 
cstate->cStateValue.maxBytesSent, sent);
+-- 
+cgit v1.1
-- 
2.11.0

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


[OE-core] [PATCH][pyro] bluez5: fix out-of-bounds access in SDP server (CVE-2017-1000250)

2017-09-13 Thread Ross Burton
All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an
information disclosure vulnerability which allows remote attackers to obtain
sensitive information from the bluetoothd process memory. This vulnerability
lies in the processing of SDP search attribute requests.

Signed-off-by: Ross Burton 
---
 meta/recipes-connectivity/bluez5/bluez5.inc|  1 +
 .../bluez5/bluez5/cve-2017-1000250.patch   | 34 ++
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch

diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc 
b/meta/recipes-connectivity/bluez5/bluez5.inc
index ccb10aaad9a..882873a486e 100644
--- a/meta/recipes-connectivity/bluez5/bluez5.inc
+++ b/meta/recipes-connectivity/bluez5/bluez5.inc
@@ -24,6 +24,7 @@ SRC_URI = "\
 file://run-ptest \
 ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '', 
'file://0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch', d)} \
 file://0001-tests-add-a-target-for-building-tests-without-runnin.patch \
+file://cve-2017-1000250.patch \
 "
 S = "${WORKDIR}/bluez-${PV}"
 
diff --git a/meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch 
b/meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch
new file mode 100644
index 000..9fac961bcf6
--- /dev/null
+++ b/meta/recipes-connectivity/bluez5/bluez5/cve-2017-1000250.patch
@@ -0,0 +1,34 @@
+All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an
+information disclosure vulnerability which allows remote attackers to obtain
+sensitive information from the bluetoothd process memory. This vulnerability
+lies in the processing of SDP search attribute requests.
+
+CVE: CVE-2017-1000250
+Upstream-Status: Backport
+Signed-off-by: Ross Burton 
+
+From 9e009647b14e810e06626dde7f1bb9ea3c375d09 Mon Sep 17 00:00:00 2001
+From: Luiz Augusto von Dentz 
+Date: Wed, 13 Sep 2017 10:01:40 +0300
+Subject: sdp: Fix Out-of-bounds heap read in service_search_attr_req function
+
+Check if there is enough data to continue otherwise return an error.
+---
+ src/sdpd-request.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/sdpd-request.c b/src/sdpd-request.c
+index 1eefdce..318d044 100644
+--- a/src/sdpd-request.c
 b/src/sdpd-request.c
+@@ -917,7 +917,7 @@ static int service_search_attr_req(sdp_req_t *req, 
sdp_buf_t *buf)
+   } else {
+   /* continuation State exists -> get from cache */
+   sdp_buf_t *pCache = sdp_get_cached_rsp(cstate);
+-  if (pCache) {
++  if (pCache && cstate->cStateValue.maxBytesSent < 
pCache->data_size) {
+   uint16_t sent = MIN(max, pCache->data_size - 
cstate->cStateValue.maxBytesSent);
+   pResponse = pCache->data;
+   memcpy(buf->data, pResponse + 
cstate->cStateValue.maxBytesSent, sent);
+-- 
+cgit v1.1
-- 
2.11.0

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


Re: [OE-core] [PATCH 2/2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES

2017-09-13 Thread Mark Hatle
On 9/13/17 12:57 PM, Otavio Salvador wrote:
> On Wed, Sep 13, 2017 at 12:15 PM, Mark Hatle  wrote:
>> If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the
>> packages.bbclass.  This made it difficult for a recipe or layer to 'append'
>> to the default.
>>
>> Copy the default into the bitbake.conf, allowing future _append and += style
>> actions.
>>
>> Signed-off-by: Mark Hatle 
> 
> Couldn't package.bbclass one to be dropped?
> 
> 

Yes, I didn't do it at present because I was worried it could affect someone and
it's after feature freeze.

If RP is not concerned about this, I can create a V2 that also removes the piece
of package.bbclass.

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


Re: [OE-core] [PATCH 2/2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES

2017-09-13 Thread Otavio Salvador
On Wed, Sep 13, 2017 at 12:15 PM, Mark Hatle  wrote:
> If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the
> packages.bbclass.  This made it difficult for a recipe or layer to 'append'
> to the default.
>
> Copy the default into the bitbake.conf, allowing future _append and += style
> actions.
>
> Signed-off-by: Mark Hatle 

Couldn't package.bbclass one to be dropped?


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


[OE-core] [PATCH v8 9/9] go: update to go 1.9

2017-09-13 Thread Otavio Salvador
From: Matt Madison 

* Rebased patches
   - dropped armhf-elf patch, should no longer be needed
   - dropped syslog patch which should not have been imported to begin with
   - reworked other patches as needed for the updated code base

* Updated native, cross, cross-canadian .inc files to
  remove some testdata directories that contain .a files
  that strip chokes on during sysroot staging

Signed-off-by: Matt Madison 
Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/recipes-devtools/go/go-1.8.inc| 22 ---
 .../go/go-1.8/armhf-elf-header.patch   | 23 
 .../go/go-1.8/fix-cc-handling.patch| 50 
 .../go/go-1.8/fix-target-cc-for-build.patch| 17 --
 meta/recipes-devtools/go/go-1.8/gotooldir.patch| 30 --
 .../go/go-1.8/make-goroot-precious.patch   | 21 ---
 meta/recipes-devtools/go/go-1.8/syslog.patch   | 62 
 meta/recipes-devtools/go/go-1.9.inc| 18 ++
 .../0001-make.bash-quote-CC_FOR_TARGET.patch   | 32 ++
 ...CC-and-CXX-environment-variable-construct.patch | 67 +
 ...h-better-separate-host-and-target-builds.patch} | 52 +
 ...w-GOTOOLDIR-to-be-overridden-in-the-envir.patch | 68 ++
 ...05-cmd-go-make-GOROOT-precious-by-default.patch | 41 +
 ...d-GOTOOLDIR_BOOTSTRAP-environment-variab.patch} | 26 +++--
 .../0007-ld-add-soname-to-shareable-objects.patch} | 20 ---
 meta/recipes-devtools/go/go-cross-canadian.inc |  1 +
 ...ss-canadian_1.8.bb => go-cross-canadian_1.9.bb} |  0
 meta/recipes-devtools/go/go-cross.inc  |  2 +-
 .../go/{go-cross_1.8.bb => go-cross_1.9.bb}|  0
 .../go/{go-crosssdk_1.8.bb => go-crosssdk_1.9.bb}  |  0
 meta/recipes-devtools/go/go-native.inc |  2 +-
 .../go/{go-native_1.8.bb => go-native_1.9.bb}  |  0
 .../go/{go-runtime_1.8.bb => go-runtime_1.9.bb}|  0
 meta/recipes-devtools/go/{go_1.8.bb => go_1.9.bb}  |  0
 24 files changed, 301 insertions(+), 253 deletions(-)
 delete mode 100644 meta/recipes-devtools/go/go-1.8.inc
 delete mode 100644 meta/recipes-devtools/go/go-1.8/armhf-elf-header.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/fix-cc-handling.patch
 delete mode 100644 
meta/recipes-devtools/go/go-1.8/fix-target-cc-for-build.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/gotooldir.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/make-goroot-precious.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/syslog.patch
 create mode 100644 meta/recipes-devtools/go/go-1.9.inc
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0001-make.bash-quote-CC_FOR_TARGET.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0002-cmd-go-fix-CC-and-CXX-environment-variable-construct.patch
 rename meta/recipes-devtools/go/{go-1.8/split-host-and-target-build.patch => 
go-1.9/0003-make.bash-better-separate-host-and-target-builds.patch} (60%)
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0004-cmd-go-allow-GOTOOLDIR-to-be-overridden-in-the-envir.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0005-cmd-go-make-GOROOT-precious-by-default.patch
 rename meta/recipes-devtools/go/{go-1.8/set-gotooldir-during-bootstrap.patch 
=> go-1.9/0006-make.bash-add-GOTOOLDIR_BOOTSTRAP-environment-variab.patch} (55%)
 rename 
meta/recipes-devtools/go/{go-1.8/0006-linker-add-soname-to-shareable-objects.patch
 => go-1.9/0007-ld-add-soname-to-shareable-objects.patch} (68%)
 rename meta/recipes-devtools/go/{go-cross-canadian_1.8.bb => 
go-cross-canadian_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go-cross_1.8.bb => go-cross_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go-crosssdk_1.8.bb => go-crosssdk_1.9.bb} 
(100%)
 rename meta/recipes-devtools/go/{go-native_1.8.bb => go-native_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go-runtime_1.8.bb => go-runtime_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go_1.8.bb => go_1.9.bb} (100%)

diff --git a/meta/recipes-devtools/go/go-1.8.inc 
b/meta/recipes-devtools/go/go-1.8.inc
deleted file mode 100644
index 8c4b71e428..00
--- a/meta/recipes-devtools/go/go-1.8.inc
+++ /dev/null
@@ -1,22 +0,0 @@
-require go-common.inc
-
-GOMINOR = "3"
-GO_BASEVERSION = "1.8"
-PV .= ".${GOMINOR}"
-FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
-
-LIC_FILES_CHKSUM = "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
-
-SRC_URI += "\
-   file://armhf-elf-header.patch \
-   file://syslog.patch \
-   file://fix-target-cc-for-build.patch \
-   file://fix-cc-handling.patch \
-   file://split-host-and-target-build.patch \
-   file://gotooldir.patch \
-   file://make-goroot-precious.patch \
-   file://set-gotooldir-during-bootstrap.patch \
-   file://0006-linker-add-soname-to-shareable-objects.patch \
-"
-SRC_URI[main.md5sum] = "64e9380e07bba907e26a00cf5fcbe77e"
-SRC_URI[main.sha2

[OE-core] [PATCH v8 4/9] go-runtime: build the Go runtime as a shared library

2017-09-13 Thread Otavio Salvador
From: Matt Madison 

If the target architecture supports, it build the Go
runtime as a shared library in addition to building
the static libraries.

Signed-off-by: Matt Madison 
Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/recipes-devtools/go/go-runtime.inc | 24 ++--
 1 file changed, 22 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/go/go-runtime.inc 
b/meta/recipes-devtools/go/go-runtime.inc
index 3775e86b06..a074238e47 100644
--- a/meta/recipes-devtools/go/go-runtime.inc
+++ b/meta/recipes-devtools/go/go-runtime.inc
@@ -24,6 +24,9 @@ do_compile() {
mkdir ${GOBIN}
cd src
GO_FLAGS="" ./make.bash
+   if [ -n "${GO_DYNLINK}" ]; then
+   GO_FLAGS="-buildmode=shared" GO_LDFLAGS="-extldflags 
\"${LDFLAGS}\"" ./make.bash
+   fi
cd ${B}
 }
 
@@ -49,8 +52,25 @@ sysroot_stage_all_append() {
 }
 
 ALLOW_EMPTY_${PN} = "1"
-FILES_${PN}-dev = "${libdir}/go/src ${libdir}/go/pkg/include"
-FILES_${PN}-staticdev = "${libdir}/go/pkg/${TARGET_GOTUPLE} 
${libdir}/go/pkg/${TARGET_GOTUPLE}"
+FILES_${PN} = "${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*${SOLIBSDEV}"
+FILES_${PN}-dev = "${libdir}/go/src ${libdir}/go/pkg/include \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*.shlibname \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*.shlibname \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*.shlibname \
+   
${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*.shlibname \
+   
${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*/*.shlibname \
+   
${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*/*/*.shlibname \
+   
${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*/*/*/*.shlibname \
+"
+FILES_${PN}-staticdev = "${libdir}/go/pkg/${TARGET_GOTUPLE} \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*.a \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*.a \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*.a \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*.a \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*/*.a \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*/*/*.a \
+   ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink/*/*/*/*/*/*/*.a \
+"
 # The testdata directories in the source tree include some binaries for various
 # architectures, scripts, and .a files
 INSANE_SKIP_${PN}-dev = "staticdev ldflags file-rdeps arch"
-- 
2.14.1

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


[OE-core] [PATCH v8 6/9] go.bbclass: Add "ldflags" to QA skip list

2017-09-13 Thread Otavio Salvador
Currently every Go package will end with GNU_HASH in the ELF binary
however adding it to every recipe is cumbersome so instead we handle
that here.

Signed-off-by: Otavio Salvador 
---

Changes in v9: None

 meta/classes/go.bbclass  | 2 ++
 meta/recipes-devtools/go/go-dep_0.3.0.bb | 2 --
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass
index d805dc2713..4af148e302 100644
--- a/meta/classes/go.bbclass
+++ b/meta/classes/go.bbclass
@@ -109,3 +109,5 @@ EXPORT_FUNCTIONS do_unpack do_configure do_compile 
do_install
 
 FILES_${PN}-dev = "${libdir}/go/src"
 FILES_${PN}-staticdev = "${libdir}/go/pkg"
+
+INSANE_SKIP_${PN} += "ldflags"
diff --git a/meta/recipes-devtools/go/go-dep_0.3.0.bb 
b/meta/recipes-devtools/go/go-dep_0.3.0.bb
index 5e4544a104..abfeb48370 100644
--- a/meta/recipes-devtools/go/go-dep_0.3.0.bb
+++ b/meta/recipes-devtools/go/go-dep_0.3.0.bb
@@ -13,6 +13,4 @@ inherit go
 
 GO_INSTALL = "${GO_IMPORT}/cmd/dep"
 
-INSANE_SKIP_${PN} += "ldflags"
-
 RDEPENDS_${PN}-dev += "bash"
-- 
2.14.1

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


[OE-core] [PATCH v8 8/9] goarch.bbclass: set ARM_INSTRUCTION_SET to "arm"

2017-09-13 Thread Otavio Salvador
From: Matt Madison 

Go does not play well with thumb, so ensure that the
toolchain and any packages use arm, not thumb, instructions.

Signed-off-by: Matt Madison 
Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/classes/goarch.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
index bfba3c9723..8b95c5fe94 100644
--- a/meta/classes/goarch.bbclass
+++ b/meta/classes/goarch.bbclass
@@ -27,6 +27,7 @@ COMPATIBLE_HOST_linux-gnux32 = "null"
 COMPATIBLE_HOST_linux-muslx32 = "null"
 COMPATIBLE_HOST_powerpc = "null"
 COMPATIBLE_HOST_powerpc64 = "null"
+ARM_INSTRUCTION_SET = "arm"
 
 def go_map_arch(a, d):
 import re
-- 
2.14.1

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


[OE-core] [PATCH v8 3/9] go-1.8: add patch for set soname in ELF shared objects

2017-09-13 Thread Otavio Salvador
From: Matt Madison 

The go link tool does not set the soname by default, which
prevents package.bbclass's shlibs processing from seeing
shared libraries built with go.

This patch passes appropriate options to go's linker and
the external linker to set the soname.

Signed-off-by: Matt Madison 
Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/recipes-devtools/go/go-1.8.inc|  1 +
 ...06-linker-add-soname-to-shareable-objects.patch | 44 ++
 2 files changed, 45 insertions(+)
 create mode 100644 
meta/recipes-devtools/go/go-1.8/0006-linker-add-soname-to-shareable-objects.patch

diff --git a/meta/recipes-devtools/go/go-1.8.inc 
b/meta/recipes-devtools/go/go-1.8.inc
index 141c0994c3..8c4b71e428 100644
--- a/meta/recipes-devtools/go/go-1.8.inc
+++ b/meta/recipes-devtools/go/go-1.8.inc
@@ -16,6 +16,7 @@ SRC_URI += "\
file://gotooldir.patch \
file://make-goroot-precious.patch \
file://set-gotooldir-during-bootstrap.patch \
+   file://0006-linker-add-soname-to-shareable-objects.patch \
 "
 SRC_URI[main.md5sum] = "64e9380e07bba907e26a00cf5fcbe77e"
 SRC_URI[main.sha256sum] = 
"5f5dea2447e7dcfdc50fa6b94c512e58bfba5673c039259fd843f68829d99fa6"
diff --git 
a/meta/recipes-devtools/go/go-1.8/0006-linker-add-soname-to-shareable-objects.patch
 
b/meta/recipes-devtools/go/go-1.8/0006-linker-add-soname-to-shareable-objects.patch
new file mode 100644
index 00..74e1f2459e
--- /dev/null
+++ 
b/meta/recipes-devtools/go/go-1.8/0006-linker-add-soname-to-shareable-objects.patch
@@ -0,0 +1,44 @@
+From 81e9e322297d83f57f02548689c71859bfce10ee Mon Sep 17 00:00:00 2001
+From: Matt Madison 
+Date: Sun, 15 Jan 2017 05:24:49 -0800
+Subject: [PATCH 6/6] linker: add soname to shareable objects
+
+Shared library handling in OE builds works better when shared
+libraries are tagged with SONAMEs.
+
+Upstream-Status: Pending
+Signed-off-by: Matt Madison 
+---
+ src/cmd/link/internal/ld/lib.go | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/src/cmd/link/internal/ld/lib.go b/src/cmd/link/internal/ld/lib.go
+index 74d79d3..6d03005 100644
+--- a/src/cmd/link/internal/ld/lib.go
 b/src/cmd/link/internal/ld/lib.go
+@@ -1040,12 +1040,14 @@ func (l *Link) hostlink() {
+   // Pass -z nodelete to mark the shared library as
+   // non-closeable: a dlclose will do nothing.
+   argv = append(argv, "-shared", "-Wl,-z,nodelete")
++  argv = append(argv, fmt.Sprintf("-Wl,-soname,%s", 
filepath.Base(*flagOutfile)))
+   }
+   case BuildmodeShared:
+   if UseRelro() {
+   argv = append(argv, "-Wl,-z,relro")
+   }
+   argv = append(argv, "-shared")
++  argv = append(argv, fmt.Sprintf("-Wl,-soname,%s", 
filepath.Base(*flagOutfile)))
+   case BuildmodePlugin:
+   if Headtype == obj.Hdarwin {
+   argv = append(argv, "-dynamiclib")
+@@ -1054,6 +1056,7 @@ func (l *Link) hostlink() {
+   argv = append(argv, "-Wl,-z,relro")
+   }
+   argv = append(argv, "-shared")
++  argv = append(argv, fmt.Sprintf("-Wl,-soname,%s", 
filepath.Base(*flagOutfile)))
+   }
+   }
+ 
+-- 
+2.7.4
+
-- 
2.14.1

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


[OE-core] [PATCH v8 5/9] go.bbclass: add support linking against shared runtime

2017-09-13 Thread Otavio Salvador
From: Matt Madison 

For architectures that support it, use the -linkshared
build option to build packages against the shared Go
runtime.

Signed-off-by: Matt Madison 
Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/classes/go.bbclass | 11 +--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass
index 8d363e86a2..d805dc2713 100644
--- a/meta/classes/go.bbclass
+++ b/meta/classes/go.bbclass
@@ -31,7 +31,14 @@ DEPENDS_GOLANG_class-nativesdk = 
"virtual/${TARGET_PREFIX}go-crosssdk virtual/${
 
 DEPENDS_append = " ${DEPENDS_GOLANG}"
 
-export GOBUILDFLAGS ?= "-v"
+GO_LINKSHARED ?= "${@'-linkshared' if d.getVar('GO_DYNLINK') else ''}"
+GO_RPATH_LINK = 
"${@'-Wl,-rpath-link=${STAGING_DIR_TARGET}${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink'
 if d.getVar('GO_DYNLINK') else ''}"
+GO_RPATH = "${@'-r ${libdir}/go/pkg/${TARGET_GOTUPLE}_dynlink' if 
d.getVar('GO_DYNLINK') else ''}"
+GO_RPATH_class-native = "${@'-r 
${STAGING_LIBDIR_NATIVE}/go/pkg/${TARGET_GOTUPLE}_dynlink' if 
d.getVar('GO_DYNLINK') else ''}"
+GO_RPATH_LINK_class-native = 
"${@'-Wl,-rpath-link=${STAGING_LIBDIR_NATIVE}/go/pkg/${TARGET_GOTUPLE}_dynlink' 
if d.getVar('GO_DYNLINK') else ''}"
+GO_EXTLDFLAGS ?= "${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS} ${GO_RPATH_LINK} 
${LDFLAGS}"
+GO_LDFLAGS ?= '-ldflags="${GO_RPATH} -extldflags '${GO_EXTLDFLAGS}'"'
+export GOBUILDFLAGS ?= "-v ${GO_LDFLAGS}"
 GOBUILDFLAGS_prepend_task-compile = "${GO_PARALLEL_BUILD} "
 
 export GO = "${HOST_PREFIX}go"
@@ -81,7 +88,7 @@ go_do_configure() {
 go_do_compile() {
${GO} env
if [ -n "${GO_INSTALL}" ]; then
-   ${GO} install ${GOBUILDFLAGS} `go_list_packages`
+   ${GO} install ${GO_LINKSHARED} ${GOBUILDFLAGS} 
`go_list_packages`
fi
 }
 do_compile[cleandirs] = "${B}/bin ${B}/pkg"
-- 
2.14.1

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


[OE-core] [PATCH v8 7/9] go.bbclass: Add ptest support

2017-09-13 Thread Otavio Salvador
This adds ptest support for Go packages so its unittest content is
packaged and integrated onto the test framework.

Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/classes/go.bbclass | 62 +++--
 1 file changed, 60 insertions(+), 2 deletions(-)

diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass
index 4af148e302..33502bf722 100644
--- a/meta/classes/go.bbclass
+++ b/meta/classes/go.bbclass
@@ -1,4 +1,4 @@
-inherit goarch
+inherit goarch ptest
 
 def get_go_parallel_make(d):
 pm = (d.getVar('PARALLEL_MAKE') or '').split()
@@ -39,6 +39,8 @@ GO_RPATH_LINK_class-native = 
"${@'-Wl,-rpath-link=${STAGING_LIBDIR_NATIVE}/go/pk
 GO_EXTLDFLAGS ?= "${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS} ${GO_RPATH_LINK} 
${LDFLAGS}"
 GO_LDFLAGS ?= '-ldflags="${GO_RPATH} -extldflags '${GO_EXTLDFLAGS}'"'
 export GOBUILDFLAGS ?= "-v ${GO_LDFLAGS}"
+export GOPTESTBUILDFLAGS ?= "${GOBUILDFLAGS} -c"
+export GOPTESTFLAGS ?= "-test.v"
 GOBUILDFLAGS_prepend_task-compile = "${GO_PARALLEL_BUILD} "
 
 export GO = "${HOST_PREFIX}go"
@@ -81,6 +83,13 @@ go_list_packages() {
egrep -v '${GO_INSTALL_FILTEROUT}'
 }
 
+go_list_package_tests() {
+${GO} list -f '{{.ImportPath}} {{.TestGoFiles}}' ${GOBUILDFLAGS} 
${GO_INSTALL} | \
+   grep -v '\[\]$' | \
+   egrep -v '${GO_INSTALL_FILTEROUT}' | \
+   awk '{ print $1 }'
+}
+
 go_do_configure() {
ln -snf ${S}/src ${B}/
 }
@@ -93,9 +102,19 @@ go_do_compile() {
 }
 do_compile[cleandirs] = "${B}/bin ${B}/pkg"
 
+do_compile_ptest() {
+rm -f ${B}/.go_compiled_tests.list
+   go_list_package_tests | while read pkg; do
+   cd ${B}/src/$pkg
+   ${GO} test ${GOPTESTBUILDFLAGS} $pkg
+   find . -mindepth 1 -maxdepth 1 -type f -name '*.test' -exec 
echo $pkg/{} \; | \
+   sed -e's,/\./,/,'>> ${B}/.go_compiled_tests.list
+   done
+}
+
 go_do_install() {
install -d ${D}${libdir}/go/src/${GO_IMPORT}
-   tar -C ${S}/src/${GO_IMPORT} -cf - --exclude-vcs . | \
+   tar -C ${S}/src/${GO_IMPORT} -cf - --exclude-vcs --exclude '*.test' . | 
\
tar -C ${D}${libdir}/go/src/${GO_IMPORT} --no-same-owner -xf -
tar -C ${B} -cf - pkg | tar -C ${D}${libdir}/go --no-same-owner -xf -
 
@@ -105,9 +124,48 @@ go_do_install() {
fi
 }
 
+do_install_ptest_base() {
+set -x
+test -f "${B}/.go_compiled_tests.list" || exit 0
+tests=""
+while read test; do
+tests="$tests${tests:+ }${test%.test}"
+testdir=`dirname $test`
+install -d ${D}${PTEST_PATH}/$testdir
+install -m 0755 ${B}/src/$test ${D}${PTEST_PATH}/$test
+if [ -d "${B}/src/$testdir/testdata" ]; then
+cp --preserve=mode,timestamps -R "${B}/src/$testdir/testdata" 
${D}${PTEST_PATH}/$testdir
+fi
+done < ${B}/.go_compiled_tests.list
+if [ -n "$tests" ]; then
+install -d ${D}${PTEST_PATH}
+cat >${D}${PTEST_PATH}/run-ptest <&1; then
+ANYFAILED=1
+fi
+done
+if [ \$ANYFAILED -ne 0 ]; then
+echo "FAIL: ${PN}"
+exit 1
+fi
+echo "PASS: ${PN}"
+exit 0
+EOF
+chmod +x ${D}${PTEST_PATH}/run-ptest
+else
+rm -rf ${D}${PTEST_PATH}
+fi
+set +x
+}
+
 EXPORT_FUNCTIONS do_unpack do_configure do_compile do_install
 
 FILES_${PN}-dev = "${libdir}/go/src"
 FILES_${PN}-staticdev = "${libdir}/go/pkg"
 
 INSANE_SKIP_${PN} += "ldflags"
+INSANE_SKIP_${PN}-ptest += "ldflags"
-- 
2.14.1

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


[OE-core] [PATCH v8 2/9] goarch.bbclass: identify archs with Go dynamic linking support

2017-09-13 Thread Otavio Salvador
From: Matt Madison 

Go only supports shared libraries for some architectures, so
add a variable for use elsewhere that gets a non-null value
only for those architectures.

Signed-off-by: Matt Madison 
Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/classes/goarch.bbclass | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
index 0c22f80518..bfba3c9723 100644
--- a/meta/classes/goarch.bbclass
+++ b/meta/classes/goarch.bbclass
@@ -11,6 +11,16 @@ TARGET_GOARM = "${@go_map_arm(d.getVar('TARGET_ARCH'), 
d.getVar('TUNE_FEATURES')
 TARGET_GOTUPLE = "${TARGET_GOOS}_${TARGET_GOARCH}"
 GO_BUILD_BINDIR = "${@['bin/${HOST_GOTUPLE}','bin'][d.getVar('BUILD_GOTUPLE') 
== d.getVar('HOST_GOTUPLE')]}"
 
+# Go supports dynamic linking on a limited set of architectures.
+# See the supportsDynlink function in go/src/cmd/compile/internal/gc/main.go
+GO_DYNLINK = ""
+GO_DYNLINK_arm = "1"
+GO_DYNLINK_aarch64 = "1"
+GO_DYNLINK_x86 = "1"
+GO_DYNLINK_x86-64 = "1"
+GO_DYNLINK_powerpc64 = "1"
+GO_DYNLINK_class-native = ""
+
 # define here because everybody inherits this class
 #
 COMPATIBLE_HOST_linux-gnux32 = "null"
-- 
2.14.1

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


[OE-core] [PATCH v8 1/9] go-runtime: extend to nativesdk builds

2017-09-13 Thread Otavio Salvador
From: Matt Madison 

Missed this when addding SDK support.

Signed-off-by: Matt Madison 
Signed-off-by: Otavio Salvador 
---

Changes in v9:
- new patch

 meta/recipes-devtools/go/go-runtime.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/go/go-runtime.inc 
b/meta/recipes-devtools/go/go-runtime.inc
index e3eddda837..3775e86b06 100644
--- a/meta/recipes-devtools/go/go-runtime.inc
+++ b/meta/recipes-devtools/go/go-runtime.inc
@@ -1,4 +1,5 @@
 DEPENDS = "virtual/${TARGET_PREFIX}go go-native"
+DEPENDS_class-nativesdk = "virtual/${TARGET_PREFIX}go-crosssdk"
 PROVIDES = "virtual/${TARGET_PREFIX}go-runtime"
 
 export GOHOSTOS = "${BUILD_GOOS}"
@@ -56,3 +57,5 @@ INSANE_SKIP_${PN}-dev = "staticdev ldflags file-rdeps arch"
 
 INHIBIT_PACKAGE_STRIP = "1"
 INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
+
+BBCLASSEXTEND = "nativesdk"
-- 
2.14.1

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


[OE-core] [PATCH v8 0/9] Revamp the Go support

2017-09-13 Thread Otavio Salvador
This improves the Go support on OE-Core.

We are trying to port as much as possible work done by Matt on
meta-golang back to OE-Core and also to avoid carrying old releases as
there is no need to support more versions of Go toolchain.

This fixes issues in existing support as well as add support for SDK
generation which supports Go.

Changes in v9:
- new patch
- new patch
- new patch
- new patch
- new patch
- new patch
- new patch
- new patch

Matt Madison (7):
  go-runtime: extend to nativesdk builds
  goarch.bbclass: identify archs with Go dynamic linking support
  go-1.8: add patch for set soname in ELF shared objects
  go-runtime: build the Go runtime as a shared library
  go.bbclass: add support linking against shared runtime
  goarch.bbclass: set ARM_INSTRUCTION_SET to "arm"
  go: update to go 1.9

Otavio Salvador (2):
  go.bbclass: Add "ldflags" to QA skip list
  go.bbclass: Add ptest support

 meta/classes/go.bbclass| 75 --
 meta/classes/goarch.bbclass| 11 
 meta/recipes-devtools/go/go-1.8.inc| 21 --
 .../go/go-1.8/armhf-elf-header.patch   | 23 ---
 .../go/go-1.8/fix-cc-handling.patch| 50 ---
 .../go/go-1.8/fix-target-cc-for-build.patch| 17 -
 meta/recipes-devtools/go/go-1.8/gotooldir.patch| 30 -
 .../go/go-1.8/make-goroot-precious.patch   | 21 --
 meta/recipes-devtools/go/go-1.8/syslog.patch   | 62 --
 meta/recipes-devtools/go/go-1.9.inc| 18 ++
 .../0001-make.bash-quote-CC_FOR_TARGET.patch   | 32 +
 ...CC-and-CXX-environment-variable-construct.patch | 67 +++
 ...h-better-separate-host-and-target-builds.patch} | 52 +++
 ...w-GOTOOLDIR-to-be-overridden-in-the-envir.patch | 68 
 ...05-cmd-go-make-GOROOT-precious-by-default.patch | 41 
 ...d-GOTOOLDIR_BOOTSTRAP-environment-variab.patch} | 26 ++--
 .../0007-ld-add-soname-to-shareable-objects.patch  | 46 +
 meta/recipes-devtools/go/go-cross-canadian.inc |  1 +
 ...ss-canadian_1.8.bb => go-cross-canadian_1.9.bb} |  0
 meta/recipes-devtools/go/go-cross.inc  |  2 +-
 .../go/{go-cross_1.8.bb => go-cross_1.9.bb}|  0
 .../go/{go-crosssdk_1.8.bb => go-crosssdk_1.9.bb}  |  0
 meta/recipes-devtools/go/go-dep_0.3.0.bb   |  2 -
 meta/recipes-devtools/go/go-native.inc |  2 +-
 .../go/{go-native_1.8.bb => go-native_1.9.bb}  |  0
 meta/recipes-devtools/go/go-runtime.inc| 27 +++-
 .../go/{go-runtime_1.8.bb => go-runtime_1.9.bb}|  0
 meta/recipes-devtools/go/{go_1.8.bb => go_1.9.bb}  |  0
 28 files changed, 443 insertions(+), 251 deletions(-)
 delete mode 100644 meta/recipes-devtools/go/go-1.8.inc
 delete mode 100644 meta/recipes-devtools/go/go-1.8/armhf-elf-header.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/fix-cc-handling.patch
 delete mode 100644 
meta/recipes-devtools/go/go-1.8/fix-target-cc-for-build.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/gotooldir.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/make-goroot-precious.patch
 delete mode 100644 meta/recipes-devtools/go/go-1.8/syslog.patch
 create mode 100644 meta/recipes-devtools/go/go-1.9.inc
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0001-make.bash-quote-CC_FOR_TARGET.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0002-cmd-go-fix-CC-and-CXX-environment-variable-construct.patch
 rename meta/recipes-devtools/go/{go-1.8/split-host-and-target-build.patch => 
go-1.9/0003-make.bash-better-separate-host-and-target-builds.patch} (60%)
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0004-cmd-go-allow-GOTOOLDIR-to-be-overridden-in-the-envir.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0005-cmd-go-make-GOROOT-precious-by-default.patch
 rename meta/recipes-devtools/go/{go-1.8/set-gotooldir-during-bootstrap.patch 
=> go-1.9/0006-make.bash-add-GOTOOLDIR_BOOTSTRAP-environment-variab.patch} (55%)
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0007-ld-add-soname-to-shareable-objects.patch
 rename meta/recipes-devtools/go/{go-cross-canadian_1.8.bb => 
go-cross-canadian_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go-cross_1.8.bb => go-cross_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go-crosssdk_1.8.bb => go-crosssdk_1.9.bb} 
(100%)
 rename meta/recipes-devtools/go/{go-native_1.8.bb => go-native_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go-runtime_1.8.bb => go-runtime_1.9.bb} (100%)
 rename meta/recipes-devtools/go/{go_1.8.bb => go_1.9.bb} (100%)

-- 
2.14.1

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


Re: [OE-core] OpenEmbedded Developer Meeting Oct 22, 2017 in Prague (before ELCE)

2017-09-13 Thread Philip Balister
On 09/13/2017 08:40 AM, Ruslan Bilovol wrote:
> On Thu, Aug 24, 2017 at 9:37 PM, Philip Balister  wrote:
>> Once again we will have a developer meeting in Prague the Sunday before
>> ELCE.
>>
>> Please go to https://www.openembedded.org/wiki/OEDEM_2017 and add
>> yourself if you are attending and ideas for topics.
>>
>> Although it is called a developer meeting, we invite members of the
>> larger community to attend. The core developers are always interested in
>> hearing how OpenEmbedded is used, and what we can do to make it better
>> for building the embedded devices of the future.
> 
> Is it free to attend, anything else required except of
> self-registration on wiki?

Self registration on the wiki is fine. See you in October.

Philip

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


[OE-core] [pyro][PATCH 0/2] Backports for pyro

2017-09-13 Thread Martin Jansa
2 cherry-picks from master:
http://git.openembedded.org/openembedded-core/commit/?id=c7ba7e9e7a7ca2caf453106112dc5a3c855b21d3
http://git.openembedded.org/openembedded-core/commit/?id=2d2b4d7383c93174fe8eeb72440e81345df71295

The following changes since commit 7b3584ace93d45ac4078019a7ef185c6e190c51f:

  Revert "expat: Don't use getrandom() in the -native case" (2017-09-11 
23:50:55 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib jansa/pyro-backports
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=jansa/pyro-backports

Martin Jansa (2):
  glibc-locale: add runtime dependency on glibc
  bitbake.conf: add bzr to HOSTTOOLS_NONFATAL

 meta/conf/bitbake.conf   | 3 +++
 meta/recipes-core/glibc/glibc-locale.inc | 4 
 2 files changed, 7 insertions(+)

-- 
2.14.1

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


[OE-core] [pyro][PATCH 2/2] bitbake.conf: add bzr to HOSTTOOLS_NONFATAL

2017-09-13 Thread Martin Jansa
From: Martin Jansa 

* it's used by bzr fetcher:
  meta/conf/bitbake.conf:FETCHCMD_bzr = "/usr/bin/env bzr"
  and when it isn't available in PATH do_fetch tasks fail with:
  /usr/bin/env: ‘bzr’: No such file or directory
* it was also added in:
  https://patchwork.openembedded.org/patch/140107/
  but this change wasn't merged (nor rejected AFAIS)

* cherry-picked from master c7ba7e9e7a7ca2caf453106112dc5a3c855b21d3

Signed-off-by: Richard Purdie 
Signed-off-by: Martin Jansa 
---
 meta/conf/bitbake.conf | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 8e4f4bbb56..2dac3a1481 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -477,6 +477,9 @@ HOSTTOOLS_NONFATAL += "aws ccache gcc-ar gpg ld.bfd ld.gold 
nc sftp socat sudo"
 # Temporary add few more detected in bitbake world
 HOSTTOOLS_NONFATAL += "join nl size yes zcat"
 
+# Used by bzr fetcher
+HOSTTOOLS_NONFATAL += "bzr"
+
 CCACHE ??= ""
 # Disable ccache explicitly if CCACHE is null since gcc may be a symlink
 # of ccache some distributions (e.g., Fedora 17).
-- 
2.14.1

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


[OE-core] [morty][PATCH 1/1] glibc-locale: add runtime dependency on glibc

2017-09-13 Thread Martin Jansa
* the libc.so.6 dependency is detected always:
  $ grep FILERDEPENDS BUILD-*/pkgdata/qemux86/runtime/localedef
  BUILD-bad/pkgdata/qemux86/runtime/localedef:FILERDEPENDSFLIST_localedef: 
/usr/bin/localedef
  
BUILD-bad/pkgdata/qemux86/runtime/localedef:FILERDEPENDS_/usr/bin/localedef_localedef:
 libc.so.6(GLIBC_2.15) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.2) 
libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.0) libc.so.6
  BUILD-ok/pkgdata/qemux86/runtime/localedef:FILERDEPENDSFLIST_localedef: 
/usr/bin/localedef
  
BUILD-ok/pkgdata/qemux86/runtime/localedef:FILERDEPENDS_/usr/bin/localedef_localedef:
 libc.so.6(GLIBC_2.15) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.2) 
libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.0) libc.so.6

* but in some builds the glibc dependency isn't built soon enough:
  $ diff -uNr BUILD-*/pkgdata/qemux86/runtime/localedef
  --- BUILD-bad/pkgdata/qemux86/runtime/localedef 2017-09-02 21:17:50.0 
+
  +++ BUILD-ok/pkgdata/qemux86/runtime/localedef  2017-09-11 10:15:49.954381592 
+
  @@ -6,6 +6,7 @@
   LICENSE: GPLv2 & LGPLv2.1
   DESCRIPTION_localedef: glibc: compile locale definition files
   SUMMARY: Locale data from glibc
  +RDEPENDS_localedef: glibc (>= 2.26)
   SECTION: base
   PKG_localedef: localedef
   FILES_localedef: /usr/bin/localedef
  and the build fails with QA issues:
  http://errors.yoctoproject.org/Errors/Details/155529/

  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.0), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.15), but no providers found in RDEPENDS_localedef? 
[file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.3), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.2), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.1), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6, but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA run found fatal errors. Please consider fixing them.

* reproducible with Yocto 2.2 Morty as well, with slightly different
  error message:
  ERROR: glibc-locale-2.24-r0 do_package_qa: QA Issue: /usr/bin/localedef 
contained in package localedef requires libc.so.6(GLIBC_2.4), but no providers 
found in RDEPENDS_localedef? [file-rdeps]

* cherry-picked from master 2d2b4d7383c93174fe8eeb72440e81345df71295

Signed-off-by: Martin Jansa 
---
 meta/recipes-core/glibc/glibc-locale.inc | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-core/glibc/glibc-locale.inc 
b/meta/recipes-core/glibc/glibc-locale.inc
index 0a7adfcc83..3fecdf996c 100644
--- a/meta/recipes-core/glibc/glibc-locale.inc
+++ b/meta/recipes-core/glibc/glibc-locale.inc
@@ -12,6 +12,10 @@ BINUTILSDEP = 
"virtual/${MLPREFIX}${TARGET_PREFIX}binutils:do_populate_sysroot"
 BINUTILSDEP_class-nativesdk = 
"virtual/${TARGET_PREFIX}binutils-crosssdk:do_populate_sysroot"
 do_package[depends] += "${BINUTILSDEP}"
 
+# localedef links with libc.so and glibc-collateral.incinhibits all default 
deps
+# cannot add virtual/libc to DEPENDS, because it would conflict with 
libc-initial in RSS
+RDEPENDS_localedef += "glibc"
+
 # Binary locales are generated at build time if ENABLE_BINARY_LOCALE_GENERATION
 # is set. The idea is to avoid running localedef on the target (at first boot)
 # to decrease initial boot time and avoid localedef being killed by the OOM
-- 
2.14.1

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


[OE-core] [pyro][PATCH 1/2] glibc-locale: add runtime dependency on glibc

2017-09-13 Thread Martin Jansa
* the libc.so.6 dependency is detected always:
  $ grep FILERDEPENDS BUILD-*/pkgdata/qemux86/runtime/localedef
  BUILD-bad/pkgdata/qemux86/runtime/localedef:FILERDEPENDSFLIST_localedef: 
/usr/bin/localedef
  
BUILD-bad/pkgdata/qemux86/runtime/localedef:FILERDEPENDS_/usr/bin/localedef_localedef:
 libc.so.6(GLIBC_2.15) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.2) 
libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.0) libc.so.6
  BUILD-ok/pkgdata/qemux86/runtime/localedef:FILERDEPENDSFLIST_localedef: 
/usr/bin/localedef
  
BUILD-ok/pkgdata/qemux86/runtime/localedef:FILERDEPENDS_/usr/bin/localedef_localedef:
 libc.so.6(GLIBC_2.15) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.2) 
libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.0) libc.so.6

* but in some builds the glibc dependency isn't built soon enough:
  $ diff -uNr BUILD-*/pkgdata/qemux86/runtime/localedef
  --- BUILD-bad/pkgdata/qemux86/runtime/localedef 2017-09-02 21:17:50.0 
+
  +++ BUILD-ok/pkgdata/qemux86/runtime/localedef  2017-09-11 10:15:49.954381592 
+
  @@ -6,6 +6,7 @@
   LICENSE: GPLv2 & LGPLv2.1
   DESCRIPTION_localedef: glibc: compile locale definition files
   SUMMARY: Locale data from glibc
  +RDEPENDS_localedef: glibc (>= 2.26)
   SECTION: base
   PKG_localedef: localedef
   FILES_localedef: /usr/bin/localedef
  and the build fails with QA issues:
  http://errors.yoctoproject.org/Errors/Details/155529/

  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.0), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.15), but no providers found in RDEPENDS_localedef? 
[file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.3), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.2), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6(GLIBC_2.1), but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA Issue: /usr/bin/localedef contained in package localedef requires 
libc.so.6, but no providers found in RDEPENDS_localedef? [file-rdeps]
  ERROR: QA run found fatal errors. Please consider fixing them.

* reproducible with Yocto 2.2 Morty as well, with slightly different
  error message:
  ERROR: glibc-locale-2.24-r0 do_package_qa: QA Issue: /usr/bin/localedef 
contained in package localedef requires libc.so.6(GLIBC_2.4), but no providers 
found in RDEPENDS_localedef? [file-rdeps]

* cherry-picked from master 2d2b4d7383c93174fe8eeb72440e81345df71295

Signed-off-by: Martin Jansa 
---
 meta/recipes-core/glibc/glibc-locale.inc | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-core/glibc/glibc-locale.inc 
b/meta/recipes-core/glibc/glibc-locale.inc
index 70e2b3a16b..75ababea68 100644
--- a/meta/recipes-core/glibc/glibc-locale.inc
+++ b/meta/recipes-core/glibc/glibc-locale.inc
@@ -12,6 +12,10 @@ BINUTILSDEP = 
"virtual/${MLPREFIX}${TARGET_PREFIX}binutils:do_populate_sysroot"
 BINUTILSDEP_class-nativesdk = 
"virtual/${TARGET_PREFIX}binutils-crosssdk:do_populate_sysroot"
 do_package[depends] += "${BINUTILSDEP}"
 
+# localedef links with libc.so and glibc-collateral.incinhibits all default 
deps
+# cannot add virtual/libc to DEPENDS, because it would conflict with 
libc-initial in RSS
+RDEPENDS_localedef += "glibc"
+
 # Binary locales are generated at build time if ENABLE_BINARY_LOCALE_GENERATION
 # is set. The idea is to avoid running localedef on the target (at first boot)
 # to decrease initial boot time and avoid localedef being killed by the OOM
-- 
2.14.1

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


[OE-core] [morty][PATCH 0/1] Backports for morty

2017-09-13 Thread Martin Jansa
1 cherry-pick from master:
http://git.openembedded.org/openembedded-core/commit/?id=2d2b4d7383c93174fe8eeb72440e81345df71295
pull request for pyro sent at the same time.

The following changes since commit 56eae27b3a7bd938d6959e5b671fc48ea2ab80c7:

  neard: Fix parallel build issue (2017-09-11 10:46:29 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib jansa/morty-backports
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=jansa/morty-backports

Martin Jansa (1):
  glibc-locale: add runtime dependency on glibc

 meta/recipes-core/glibc/glibc-locale.inc | 4 
 1 file changed, 4 insertions(+)

-- 
2.14.1

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


Re: [OE-core] OpenEmbedded Developer Meeting Oct 22, 2017 in Prague (before ELCE)

2017-09-13 Thread Ruslan Bilovol
On Thu, Aug 24, 2017 at 9:37 PM, Philip Balister  wrote:
> Once again we will have a developer meeting in Prague the Sunday before
> ELCE.
>
> Please go to https://www.openembedded.org/wiki/OEDEM_2017 and add
> yourself if you are attending and ideas for topics.
>
> Although it is called a developer meeting, we invite members of the
> larger community to attend. The core developers are always interested in
> hearing how OpenEmbedded is used, and what we can do to make it better
> for building the embedded devices of the future.

Is it free to attend, anything else required except of
self-registration on wiki?

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


Re: [OE-core] [RFC][PATCH] recipes: replace runtime dependency on bash with VIRTUAL-RUNTIME_bash

2017-09-13 Thread Peter Kjellerstedt
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Martin Jansa
> Sent: den 13 september 2017 16:49
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [RFC][PATCH] recipes: replace runtime dependency on
> bash with VIRTUAL-RUNTIME_bash
> 
> * this allows to reliably replace bash with e.g. busybox
> * without this change the QA check can find bash as the provider
>   for /bin/bash if you build bash before some other recipe using
>   bash and then QA issue like this is shown:
>   ERROR: QA Issue: foo rdepends on bash, but it isn't a build dependency
>   , missing bash in DEPENDS or PACKAGECONFIG? [build-deps]
>   even when the distro has bash enabled in busybox defconfig and
>   busybox RPROVIDES bash as well as /bin/bash, this is because the QA
>   check (and to some extend also the package-manager) doesn't know which
>   provider is prefered, so if bash isn't built at all in sysroot, it
>   will happily accept busybox as the provider, but when both are built
>   in sysroot, then bash is found first and QA error is shown.
> * more information in:
>   https://bugzilla.yoctoproject.org/show_bug.cgi?id=9217
> 
> Signed-off-by: Martin Jansa 
> ---
>  meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb | 3 ++-
>  meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb  | 3 ++-
>  meta/recipes-connectivity/openssl/openssl_1.1.0f.bb | 3 ++-
>  meta/recipes-connectivity/resolvconf/resolvconf_1.79.bb | 3 ++-
>  meta/recipes-core/console-tools/console-tools_0.3.2.bb  | 3 ++-
>  meta/recipes-core/dbus/dbus-test_1.10.20.bb | 3 ++-
>  meta/recipes-core/glibc/glibc-scripts.inc   | 3 ++-
>  meta/recipes-core/systemd/systemd_234.bb| 5 +++--
>  meta/recipes-core/util-linux/util-linux.inc | 3 ++-
>  meta/recipes-devtools/apt/apt_1.2.24.bb | 3 ++-
>  meta/recipes-devtools/build-compare/build-compare_git.bb| 3 ++-
>  meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb | 3 ++-
>  meta/recipes-devtools/flex/flex_2.6.0.bb| 3 ++-
>  meta/recipes-devtools/go/go-dep_0.3.0.bb| 3 ++-
>  meta/recipes-devtools/go/go-target.inc  | 3 ++-
>  meta/recipes-devtools/libtool/libtool_2.4.6.bb  | 3 ++-
>  meta/recipes-devtools/pax-utils/pax-utils_1.2.2.bb  | 3 ++-
>  meta/recipes-devtools/qemu/qemu.inc | 3 ++-
>  meta/recipes-devtools/qemu/qemu_2.10.0.bb   | 3 ++-
>  meta/recipes-devtools/quilt/quilt.inc   | 5 +++--
>  meta/recipes-devtools/rpm/rpm_git.bb| 3 ++-
>  meta/recipes-devtools/tcf-agent/tcf-agent_git.bb| 3 ++-
>  meta/recipes-extended/hdparm/hdparm_9.52.bb | 3 ++-
>  meta/recipes-extended/mdadm/mdadm_4.0.bb| 3 ++-
>  meta/recipes-extended/parted/parted_3.2.bb  | 3 ++-
>  meta/recipes-kernel/dtc/dtc.inc | 3 ++-
>  meta/recipes-kernel/lttng/lttng-tools_2.9.5.bb  | 3 ++-
>  meta/recipes-kernel/perf/perf.bb| 9 +
>  meta/recipes-kernel/systemtap/systemtap_git.bb  | 3 ++-
>  meta/recipes-multimedia/alsa/alsa-utils-scripts_1.1.4.bb| 3 ++-
>  meta/recipes-support/apr/apr_1.6.2.bb   | 3 ++-
>  meta/recipes-support/attr/acl_2.2.52.bb | 3 ++-
>  meta/recipes-support/source-highlight/source-highlight_3.1.8.bb | 3 ++-
>  33 files changed, 71 insertions(+), 38 deletions(-)
> 
> diff --git a/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb 
> b/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb
> index cac09101c4..d9dcde1aff 100644
> --- a/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb
> +++ b/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb
> @@ -17,7 +17,8 @@ inherit pkgconfig autotools manpages
> 
>  PACKAGECONFIG[manpages] = "--enable-doc, --disable-doc, libxslt-native 
> xmlto-native"
> 
> -RDEPENDS_${PN} = "grep bash"
> +VIRTUAL-RUNTIME_bash ?= "bash"

Isn't it better to set the default once in 
meta/conf/distro/include/default-providers.inc?

> +RDEPENDS_${PN} = "grep ${VIRTUAL-RUNTIME_bash}"
> 
>  do_configure_prepend () {
>   ( cd ${S}; autoreconf -f -i -s )
> diff --git a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb 
> b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb
> index d917c4d713..b0237a72a0 100644
> --- a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb
> +++ b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb
> @@ -9,7 +9,8 @@ LIC_FILES_CHKSUM =
> "file://COPYING;md5=95f3a93a5c3c7888de623b46ea085a84"
> 
>  # util-linux for libblkid
>  DEPENDS = "libcap libnfsidmap libevent util-linux sqlite3 

[OE-core] [PATCH 2/2] bitbake.conf: Add default FILESYSTEM_PERMS_TABLES

2017-09-13 Thread Mark Hatle
If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the
packages.bbclass.  This made it difficult for a recipe or layer to 'append'
to the default.

Copy the default into the bitbake.conf, allowing future _append and += style
actions.

Signed-off-by: Mark Hatle 
---
 meta/conf/bitbake.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 444c53f..791aee0 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -330,6 +330,10 @@ FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE', 
False))}"
 # This default was only used for checking
 FILESEXTRAPATHS ?= "__default:"
 
+# Following is a duplication of the default defined in packages.bbclass,
+# both should be kept in sync
+FILESYSTEM_PERMS_TABLES ?= "${@'files/fs-perms.txt' if 
oe.types.boolean(d.getVar('VOLATILE_LOG_DIR', True)) else 
'files/fs-perms-persistent-log.txt'}"
+
 ##
 # General work and output directories for the build system.
 ##
-- 
1.8.3.1

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


[OE-core] [PATCH 1/2] meta/conf/layers.conf: Add ca-certificates as ABISAFE

2017-09-13 Thread Mark Hatle
meta-oe was doing this before, but it was triggering a yocto-compat-script
failure during the signature checking.

The ca-certificates changing is ABISAFE, as the certificates themselves do
not modify the compiles behavior of the applications.  This should permit
easier upgrades without as much rebuilding.

The original value was set in meta-oe by commit
ff7a4b13c4efeffc5853a93c6ff7265fa3d6c143.

Signed-off-by: Mark Hatle 
---
 meta/conf/layer.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index df457c2..6be2a57 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -40,6 +40,7 @@ SIGGEN_EXCLUDERECIPES_ABISAFE += " \
   base-passwd \
   opkg-utils \
   gstreamer1.0-meta-base \
+  ca-certificates \
 "
 
 SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \
-- 
1.8.3.1

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


[OE-core] [RFC][PATCH] recipes: replace runtime dependency on bash with VIRTUAL-RUNTIME_bash

2017-09-13 Thread Martin Jansa
* this allows to reliably replace bash with e.g. busybox
* without this change the QA check can find bash as the provider
  for /bin/bash if you build bash before some other recipe using
  bash and then QA issue like this is shown:
  ERROR: QA Issue: foo rdepends on bash, but it isn't a build dependency
  , missing bash in DEPENDS or PACKAGECONFIG? [build-deps]
  even when the distro has bash enabled in busybox defconfig and
  busybox RPROVIDES bash as well as /bin/bash, this is because the QA
  check (and to some extend also the package-manager) doesn't know which
  provider is prefered, so if bash isn't built at all in sysroot, it
  will happily accept busybox as the provider, but when both are built
  in sysroot, then bash is found first and QA error is shown.
* more information in:
  https://bugzilla.yoctoproject.org/show_bug.cgi?id=9217

Signed-off-by: Martin Jansa 
---
 meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb | 3 ++-
 meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb  | 3 ++-
 meta/recipes-connectivity/openssl/openssl_1.1.0f.bb | 3 ++-
 meta/recipes-connectivity/resolvconf/resolvconf_1.79.bb | 3 ++-
 meta/recipes-core/console-tools/console-tools_0.3.2.bb  | 3 ++-
 meta/recipes-core/dbus/dbus-test_1.10.20.bb | 3 ++-
 meta/recipes-core/glibc/glibc-scripts.inc   | 3 ++-
 meta/recipes-core/systemd/systemd_234.bb| 5 +++--
 meta/recipes-core/util-linux/util-linux.inc | 3 ++-
 meta/recipes-devtools/apt/apt_1.2.24.bb | 3 ++-
 meta/recipes-devtools/build-compare/build-compare_git.bb| 3 ++-
 meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb | 3 ++-
 meta/recipes-devtools/flex/flex_2.6.0.bb| 3 ++-
 meta/recipes-devtools/go/go-dep_0.3.0.bb| 3 ++-
 meta/recipes-devtools/go/go-target.inc  | 3 ++-
 meta/recipes-devtools/libtool/libtool_2.4.6.bb  | 3 ++-
 meta/recipes-devtools/pax-utils/pax-utils_1.2.2.bb  | 3 ++-
 meta/recipes-devtools/qemu/qemu.inc | 3 ++-
 meta/recipes-devtools/qemu/qemu_2.10.0.bb   | 3 ++-
 meta/recipes-devtools/quilt/quilt.inc   | 5 +++--
 meta/recipes-devtools/rpm/rpm_git.bb| 3 ++-
 meta/recipes-devtools/tcf-agent/tcf-agent_git.bb| 3 ++-
 meta/recipes-extended/hdparm/hdparm_9.52.bb | 3 ++-
 meta/recipes-extended/mdadm/mdadm_4.0.bb| 3 ++-
 meta/recipes-extended/parted/parted_3.2.bb  | 3 ++-
 meta/recipes-kernel/dtc/dtc.inc | 3 ++-
 meta/recipes-kernel/lttng/lttng-tools_2.9.5.bb  | 3 ++-
 meta/recipes-kernel/perf/perf.bb| 9 +
 meta/recipes-kernel/systemtap/systemtap_git.bb  | 3 ++-
 meta/recipes-multimedia/alsa/alsa-utils-scripts_1.1.4.bb| 3 ++-
 meta/recipes-support/apr/apr_1.6.2.bb   | 3 ++-
 meta/recipes-support/attr/acl_2.2.52.bb | 3 ++-
 meta/recipes-support/source-highlight/source-highlight_3.1.8.bb | 3 ++-
 33 files changed, 71 insertions(+), 38 deletions(-)

diff --git a/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb 
b/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb
index cac09101c4..d9dcde1aff 100644
--- a/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb
+++ b/meta/recipes-bsp/pm-utils/pm-utils_1.4.1.bb
@@ -17,7 +17,8 @@ inherit pkgconfig autotools manpages
 
 PACKAGECONFIG[manpages] = "--enable-doc, --disable-doc, libxslt-native 
xmlto-native"
 
-RDEPENDS_${PN} = "grep bash"
+VIRTUAL-RUNTIME_bash ?= "bash"
+RDEPENDS_${PN} = "grep ${VIRTUAL-RUNTIME_bash}"
 
 do_configure_prepend () {
( cd ${S}; autoreconf -f -i -s )
diff --git a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb 
b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb
index d917c4d713..b0237a72a0 100644
--- a/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb
+++ b/meta/recipes-connectivity/nfs-utils/nfs-utils_2.1.1.bb
@@ -9,7 +9,8 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=95f3a93a5c3c7888de623b46ea085a84"
 
 # util-linux for libblkid
 DEPENDS = "libcap libnfsidmap libevent util-linux sqlite3 libtirpc"
-RDEPENDS_${PN} = "${PN}-client bash"
+VIRTUAL-RUNTIME_bash ?= "bash"
+RDEPENDS_${PN} = "${PN}-client ${VIRTUAL-RUNTIME_bash}"
 RRECOMMENDS_${PN} = "kernel-module-nfsd"
 
 inherit useradd
diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.0f.bb 
b/meta/recipes-connectivity/openssl/openssl_1.1.0f.bb
index 711a95985a..4661d2 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.0f.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.0f.bb
@@ -146,7 +146,8 @@ do_install_ptest() {
 sed -i 's/$target{shared_extension_simple}/".so.ptest"/' 
${D}${PTEST_PATH}/test/recipes/

Re: [OE-core] Yocto Matchbox in 240x320 LCD Display

2017-09-13 Thread Burton, Ross
The default theme, fonts, padding etc all assume the screen has a higher
resolution than you have.  At one point there used to be a qvga theme but
that was dropped several years ago.  Making the font a lot smaller will
solve most of your problems, then you'll have to fix the remaining problems
one by one: as you can see the window decoration theme (the green bar) is
far too big at QVGA.

Ross

On 13 September 2017 at 15:15,  wrote:

> Hi,
>
>   Hope I m at the right place asking a query about matchbox in yocto.
>
>   I am using Yocto 1.8 which is working fine in a 640x480 LCD display
>
>   But I have few issues when the same BSP used in a 240x320 LCD display.
> All the images and fonts are enlarged .
>
>  Attaching few screnschots along with this mail.
>
>  Is there any constraints for matchbox to work on 240x320 display ?
>
>
>
> Awaiting for valuable suggestions.
>
> Thanks & Regards,
>
> Anjali
>
>
> --
> ___
> 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] qemu: upgrade to version 2.10.0

2017-09-13 Thread Burton, Ross
On 13 September 2017 at 15:12, Martin Jansa  wrote:

> On Fri, Sep 01, 2017 at 01:44:56PM +0200, Martin Jansa wrote:
> > I don't know how accelerated GL will be in the end, but this commit:
> > https://git.qemu.org/?p=qemu.git;a=commitdiff;h=
> 474114b7305cc1be7c2ee8ba5267be159a9d56e3
> > made it possible.
> >
> > I've built qemu with my Gentoo host with virgl and spice support, and I
> > plan to try how fast it goes.
>
> I've some WIP changes to build qemu-native with virglrenderer enabled in:
> http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu
>
> and few more to enable spice as well in:
> http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/spice


Awesome. Can't wait to see how it performs.

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


Re: [OE-core] [PATCH] qemu: upgrade to version 2.10.0

2017-09-13 Thread Martin Jansa
On Fri, Sep 01, 2017 at 01:44:56PM +0200, Martin Jansa wrote:
> I don't know how accelerated GL will be in the end, but this commit:
> https://git.qemu.org/?p=qemu.git;a=commitdiff;h=474114b7305cc1be7c2ee8ba5267be159a9d56e3
> made it possible.
> 
> I've built qemu with my Gentoo host with virgl and spice support, and I
> plan to try how fast it goes.

I've some WIP changes to build qemu-native with virglrenderer enabled in:
http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu

and few more to enable spice as well in:
http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/spice

> On Fri, Sep 1, 2017 at 12:09 PM, Burton, Ross  wrote:
> 
> > On 1 September 2017 at 11:03, Martin Jansa  wrote:
> >
> >> Is there any ticket requesting virgl support enabled in qemu-native? It
> >> might depend on providing virglrenderer-native, libsdl2-native,
> >> epoxy-native and maybe even mesa-native.
> >>
> >
> > It's been something that I've been meaning to look at for a long time, but
> > between my build machine being headless and other stuff being more
> > important I've not got around to it.  I've not dug into the details: if you
> > run headless qemu and a spice client, presumably you don't get any real GL
> > acceleration?
> >
> > Patches welcome, as always.  All the extra build dependencies means I
> > expect it will be off by default, but having the option would be great.
> >
> > Ross
> >

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


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


Re: [OE-core] [PATCH 0/7] kernel-yocto: conslidated pull request

2017-09-13 Thread Bruce Ashfield

On 09/05/2017 10:59 AM, Richard Purdie wrote:

On Tue, 2017-09-05 at 10:24 -0400, Bruce Ashfield wrote:

On 09/05/2017 10:13 AM, Richard Purdie wrote:


Hi Bruce,

We had a locked up qemuppc lsb image and I was able to find
backtraces
from the serial console log (/home/pokybuild/yocto-
autobuilder/yocto-
worker/nightly-ppc-lsb/build/build/tmp/work/qemuppc-poky-
linux/core-
image-lsb/1.0-r0/target_logs/dmesg_output.log in case anyone ever
needs
to find that). The log is below, this one is for the 4.9 kernel.

Failure as seen on the AB:
https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/
buil
ds/1189/steps/Running%20Sanity%20Tests/logs/stdio

Not sure what it means, perhaps you can make more sense of it? :)

Very interesting.

I'm (un)fortunately familiar with RCU issues, and obviously, this is
only happening under load. There's clearly a driver issue as it
interacts with whatever is running in userspace.

  From the log, it looks like this is running over NFS and pinning the
CPU and the qemu ethernet isn't handling it gracefully.


Looking at the logs I've seen I don't think this is over NFS, it should
be over virtio:

"Kernel command line: root=/dev/vda"


But exactly what it is, I can't say from that trace. I'll try and do
a cpu-pinned test on qemuppc (over NFS) and see if I can trigger the
same trace.


I'm also not sure what this might be. I did a bit more staring at the
log and I think the system did come back:

NOTE: core-image-lsb-1.0-r0 do_testimage:   test_dnf_install_from_disk 
(dnf.DnfRepoTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... OK (249.929s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_dnf_install_from_http 
(dnf.DnfRepoTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... OK (212.547s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_dnf_reinstall (dnf.DnfRepoTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... FAIL (1501.682s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_dnf_repoinfo (dnf.DnfRepoTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... FAIL (15.952s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_syslog_running 
(oe_syslog.SyslogTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... FAIL (3.039s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_syslog_logger 
(oe_syslog.SyslogTestConfig)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... SKIP (0.001s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_syslog_restart 
(oe_syslog.SyslogTestConfig)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... SKIP (0.001s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_syslog_startup_config 
(oe_syslog.SyslogTestConfig)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... SKIP (0.001s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_pam (pam.PamBasicTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... FAIL (3.003s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_parselogs 
(parselogs.ParseLogsTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... OK (39.675s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_rpm_help (rpm.RpmBasicTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... OK (2.590s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_rpm_query (rpm.RpmBasicTest)
NOTE: core-image-lsb-1.0-r0 do_testimage:  ... OK (2.295s)
NOTE: core-image-lsb-1.0-r0 do_testimage:   test_rpm_instal

So for a while there the system "locked up":

AssertionError: 255 != 0 : dnf 
--repofrompath=oe-testimage-repo-noarch,http://192.168.7.1:38838/noarch 
--repofrompath=oe-testimage-repo-qemuppc,http://192.168.7.1:38838/qemuppc 
--repofrompath=oe-testimage-repo-ppc7400,http://192.168.7.1:38838/ppc7400 
--nogpgcheck reinstall -y run-postinsts-dev

Process killed - no output for 1500 seconds. Total running time: 1501 seconds.

AssertionError: 255 != 0 : dnf 
--repofrompath=oe-testimage-repo-noarch,http://192.168.7.1:38838/noarch 
--repofrompath=oe-testimage-repo-qemuppc,http://192.168.7.1:38838/qemuppc 
--repofrompath=oe-testimage-repo-ppc7400,http://192.168.7.1:38838/ppc7400 
--nogpgcheck repoinfo
ssh: connect to host 192.168.7.2 port 22: No route to host

self.assertEqual(status, 1, msg = msg)
AssertionError: 255 != 1 : login command does not work as expected. Status and 
output:255 and ssh: connect to host 192.168.7.2 port 22: No route to host

then the system seems to have come back. All very odd...


I'm still trying to get a solid reproducer for this, but I'm now
going down the route of isolating different parts of the system.

I was looking at:

https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/475/steps/Running%20Sanity%20Tests/logs/stdio

And I thought that this was related to the switch of the cdrom to
be virtio backed, but looking at the command line:

tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-ppc 
-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-autobuilder/yocto-worker/nightly-ppc-lsb/build/build/tmp/deploy/images/qemuppc/core

Re: [OE-core] [PATCH] systemd: Fix rootfs transaction error when PACKAGECONFIG has polkit

2017-09-13 Thread Jason Wessel

It should work because it has nothing to do with that particular passwd file.   
This is builds successfully on a ubuntu 16.04 host which has no polkitd user.

Also with the user add stanza in the patch it should be adding the user that is 
required when PACKAGECONFIG has the polkitd added to the psuedo passwd file.   
We have quite a few configurations building properly.  Where I have seen 
transient failures before is when the -native sysroot does not get rebuilt but 
that is typically with other recipes.

Is this still a problem?


Jason.


On 09/06/2017 01:35 PM, Martin Jansa wrote:

Does this work on hosts without polkitd user?

Here it failed with:

| chown: invalid user: ‘polkitd:root’






On Tue, Aug 15, 2017 at 8:55 PM, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:

The systemd 234 added some files to the polkit directory and the
directory the files live in must be owned by the polkitd user, else
you will receive the following error when the rootfs is being
assembled:

Error: Transaction check error:
  file /usr/share/polkit-1/rules.d conflicts between attempted installs of 
polkit-0.113-r0.15.core2_64 and systemd-1:234-r0.0.core2_64

The fix similar to other packages such as libvirt where the user must
exist and the directory must be created with the proper attributes.

Signed-off-by: Jason Wessel mailto:jason.wes...@windriver.com>>
---
 meta/recipes-core/systemd/systemd_234.bb  | 9 
+
 1 file changed, 9 insertions(+)

diff --git a/meta/recipes-core/systemd/systemd_234.bb  
b/meta/recipes-core/systemd/systemd_234.bb 
index ad7fc99b90..4560cf4175 100644
--- a/meta/recipes-core/systemd/systemd_234.bb 
+++ b/meta/recipes-core/systemd/systemd_234.bb 
@@ -245,6 +245,14 @@ do_install() {
ln -s ../run/systemd/resolve/resolv.conf 
${D}${sysconfdir}/resolv-conf.systemd
fi
install -Dm 0755 ${S}/src/systemctl/systemd-sysv-install.SKELETON 
${D}${systemd_unitdir}/systemd-sysv-install
+
+   # If polkit is setup fixup permissions and ownership
+   if [ "${@bb.utils.contains('PACKAGECONFIG', 'polkit', 'polkit', '', d)}" = 
"polkit" ] ; then
+   if [ -d ${D}${datadir}/polkit-1/rules.d ] ; then
+   chmod 700 ${D}${datadir}/polkit-1/rules.d
+   chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+   fi
+   fi
 }

 do_install_ptest () {
@@ -308,6 +316,7 @@ USERADD_PARAM_${PN} += 
"${@bb.utils.contains('PACKAGECONFIG', 'timesyncd', '--sy
 USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'networkd', 
'--system -d / -M --shell /bin/nologin systemd-network;', '', d)}"
 USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'coredump', 
'--system -d / -M --shell /bin/nologin systemd-coredump;', '', d)}"
 USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'resolved', 
'--system -d / -M --shell /bin/nologin systemd-resolve;', '', d)}"
+USERADD_PARAM_${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'polkit', 
'--system --no-create-home --user-group --home-dir ${sysconfdir}/polkit-1 polkitd;', '', 
d)}"
 GROUPADD_PARAM_${PN} = "-r lock; -r systemd-journal"
 USERADD_PARAM_${PN}-extra-utils += "--system -d / -M --shell /bin/nologin 
systemd-bus-proxy;"

--
2.11.0

--
___
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 v8 3/3] kernel-devicetree.bbclass: Add support to generate append to kernel

2017-09-13 Thread Otavio Salvador
On Wed, Sep 13, 2017 at 5:15 AM, André Draszik  wrote:
> On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
...
> AFAICS, zImage is specific to x86 and arm, all other arches, including MIPS
> have no zImage Makefile target, so we'll never get here.

Do you know which types we can use here?

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


Re: [OE-core] [oe-commits] [openembedded-core] branch master updated (cc319b6 -> 2ebbeb6)

2017-09-13 Thread Bruce Ashfield

On 09/13/2017 02:23 AM, Andrea Galbusera wrote:

Hi!

On Tue, Sep 12, 2017 at 12:58 PM, Martin Jansa > wrote:


Hi,

I don't see any obvious change in this update which should cause
this, but rebuilding my image for raspberrypi3-64 after this update
(the previous image was built without errors) shows:

NOTE: Running task 417 of 6399

(/OE/build/owpb/webos-ports/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:do_validate_branches)
NOTE: recipe linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0:
task do_validate_branches: Started

NOTE: recipe linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0:
task do_validate_branches: Succeeded
NOTE: Running task 434 of 6399

(/OE/build/owpb/webos-ports/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:do_kernel_metadata)
NOTE: recipe linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0:
task do_kernel_metadata: Started
ERROR: linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0
do_kernel_metadata: Could not locate BSP definition for
raspberrypi3-64/standard and no defconfig was provided
NOTE: recipe linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0:
task do_kernel_metadata: Succeeded
...
NOTE: Running task 454 of 6399

(/OE/build/owpb/webos-ports/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:do_patch)
NOTE: recipe linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0:
task do_patch: Started
NOTE: recipe linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0:
task do_patch: Succeeded
NOTE: Running task 491 of 6399

(/OE/build/owpb/webos-ports/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:do_kernel_configme)
NOTE: recipe linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0:
task do_kernel_configme: Started
ERROR: linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0
do_kernel_configme: [ERROR]: no configuration queue found in outdir
(.kernel-meta)

  scc [--help] [--configs] [--force] [-i] [-w] [--cmds ] [-o outdir:] [-D=]
[-I] [-v] infiles

   --help:  This message
   --force: force overwrite output file if it already exists
   --cmds:  list of supported commands. If not passed, all
found commands are loaded,
valid commands are: patch, kconf, branch, define
   --configs:   Output the list of compiled configuration
fragments (if available), -o  is
used to locate the configuration options
   -D:  define  to  which will be available
to sub scripts
   -I:  include path  will be searched for files
   -i:  leave intermediate files on failure
   -w:  only warn on missing files
   -v:  verbose output
   -o:  output directory and artifacts. artifacts follow
the colon and ar a comma
separated list of:
meta:  full meta-series (patches, config,
branches, etc)
cfg:   configure fragment queue
patch: patch queue

   infiles  files to preprocess, and output into outfile or
stdout
ERROR: linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0
do_kernel_configme: Could not find configuration queue
(.kernel-meta/config.queue)
ERROR: linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0
do_kernel_configme: Function failed: do_kernel_configme (log file is
located at

/OE/build/owpb/webos-ports/tmp-glibc/work/raspberrypi3_64-webos-linux/linux-raspberrypi/1_4.9.41+gitAUTOINC+4153f509b4-r0/temp/log.do_kernel_configme.19498)
ERROR: Logfile of failure stored in:

/OE/build/owpb/webos-ports/tmp-glibc/work/raspberrypi3_64-webos-linux/linux-raspberrypi/1_4.9.41+gitAUTOINC+4153f509b4-r0/temp/log.do_kernel_configme.19498
Log data follows:
| DEBUG: Executing shell function do_kernel_configme
| ERROR: [ERROR]: no configuration queue found in outdir (.kernel-meta)
|
|  scc [--help] [--configs] [--force] [-i] [-w] [--cmds ] [-o outdir:] [-D=]
[-I] [-v] infiles
|
|   --help:  This message
|   --force: force overwrite output file if it already exists
|   --cmds:  list of supported commands. If not passed, all
found commands are loaded,
|valid commands are: patch, kconf, branch, define
|   --configs:   Output the list of compiled configuration
fragments (if available), -o  is
|used to locate the configuration options
|   -D:  define  to  which will be available
to sub scripts
|   -I:  include path  will be searched for files
|   -i:  leave intermediate files on failure
|   -w:  only warn on missing files
|   -v:  v

Re: [OE-core] [PATCH v8 06/13] go-dep: Move bash dependency to -dev package

2017-09-13 Thread Otavio Salvador
On Wed, Sep 13, 2017 at 8:09 AM, Matt Madison  wrote:
> On Tue, Sep 12, 2017 at 12:21 PM, Khem Raj  wrote:
>> On Tue, Sep 12, 2017 at 12:20 PM, Otavio Salvador
>>  wrote:
>>> On Tue, Sep 12, 2017 at 3:58 PM, Martin Jansa  
>>> wrote:
 Seems like this version was already picked to master-next, so probably
 better to leave as standalone change now.

 The version currently in master fails to build for arm with thumb enabled:
 http://errors.yoctoproject.org/Errors/Details/155765/

 Is it fixed somewhere in this new patchset?

 # github.com/golang/dep/cmd/dep
 TOPDIR/tmp-glibc/work/armv5te-oe-linux-gnueabi/go-dep/0.3.0-r0/recipe-sysroot-native/usr/lib/arm-oe-linux-gnueabi/go/pkg/tool/linux_amd64/link:
 R_ARM_THM_CALL, are you using -marm?
 WARNING: exit code 2 from a shell command.
 ERROR: Function failed: do_compile (log file is located at
 TOPDIR/tmp-glibc/work/armv5te-oe-linux-gnueabi/go-dep/0.3.0-r0/temp/log.do_compile.13531)
>>>
>>> No, it is not.
>>>
>>> It seems that Go, when using CGO, does not play nice with Thumb. Matt,
>>> do you know if there is a known fix for it?
>>
>> Disable CGO for thumb, we have a variable to select cgo
>
> Yeah, I don't think Go handles Thumb at all. Maybe we should set
> ARM_INSTRUCTION_SET to "arm" in goarch.bbclass?

I think we have a problem with dependencies. It is possibly a solution
but not sure it will work.

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


Re: [OE-core] [PATCH 3/3] wic: apply --extra-space + --overhead to squashfs

2017-09-13 Thread Ed Bartosh
On Tue, Sep 12, 2017 at 03:23:40PM +0200, Enrico Scholz wrote:
> Ed Bartosh  writes:
> 
> > I agree. --size is less suitable for your needs than extra space and
> > overhead factor. I still don't like the idea of using them to reserve
> > non-formatted space.
> 
> Btw, exactly this is done for extX already.
> 

Are you sure?
I don't see where we produce unformatted space on extX partitions.
Can you point me out?

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


Re: [OE-core] [PATCH 2/2] externalsrc.bbclass: Avoid symlink clashes for virtclasses

2017-09-13 Thread Ola x Nilsson

> From: Richard Purdie 
> Sent: Wednesday, September 13, 2017 12:41
>
>On Tue, 2017-09-12 at 11:23 +, Ola x Nilsson wrote:
>> I noticed that the preceding commit has been merged.
>>  Is there some problem with this one?
>
> Its not something I can describe easily, more a gut feeling that is
> shared by some others I've talked to.
>
> Basically externalsrc is turning into an ever more complicated pile of
> corner cases and it worries me a lot. I can't help thinking we really
> want to simplify and streamline this, not add more complexity to it.

Can't argue with that.

/Ola






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


Re: [OE-core] [PATCH v8 06/13] go-dep: Move bash dependency to -dev package

2017-09-13 Thread Matt Madison
On Tue, Sep 12, 2017 at 12:21 PM, Khem Raj  wrote:
> On Tue, Sep 12, 2017 at 12:20 PM, Otavio Salvador
>  wrote:
>> On Tue, Sep 12, 2017 at 3:58 PM, Martin Jansa  wrote:
>>> Seems like this version was already picked to master-next, so probably
>>> better to leave as standalone change now.
>>>
>>> The version currently in master fails to build for arm with thumb enabled:
>>> http://errors.yoctoproject.org/Errors/Details/155765/
>>>
>>> Is it fixed somewhere in this new patchset?
>>>
>>> # github.com/golang/dep/cmd/dep
>>> TOPDIR/tmp-glibc/work/armv5te-oe-linux-gnueabi/go-dep/0.3.0-r0/recipe-sysroot-native/usr/lib/arm-oe-linux-gnueabi/go/pkg/tool/linux_amd64/link:
>>> R_ARM_THM_CALL, are you using -marm?
>>> WARNING: exit code 2 from a shell command.
>>> ERROR: Function failed: do_compile (log file is located at
>>> TOPDIR/tmp-glibc/work/armv5te-oe-linux-gnueabi/go-dep/0.3.0-r0/temp/log.do_compile.13531)
>>
>> No, it is not.
>>
>> It seems that Go, when using CGO, does not play nice with Thumb. Matt,
>> do you know if there is a known fix for it?
>
> Disable CGO for thumb, we have a variable to select cgo

Yeah, I don't think Go handles Thumb at all. Maybe we should set
ARM_INSTRUCTION_SET to "arm" in goarch.bbclass?

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


Re: [OE-core] [PATCH 2/2] externalsrc.bbclass: Avoid symlink clashes for virtclasses

2017-09-13 Thread Richard Purdie
On Tue, 2017-09-12 at 11:23 +, Ola x Nilsson wrote:
> I noticed that the preceding commit has been merged. 
> Is there some problem with this one?

Its not something I can describe easily, more a gut feeling that is
shared by some others I've talked to.

Basically externalsrc is turning into an ever more complicated pile of
corner cases and it worries me a lot. I can't help thinking we really
want to simplify and streamline this, not add more complexity to it.

How exactly we do that I'm not sure, I haven't had the time to spend
looking at the code. I do appreciate you added a test case though.

I guess what might help would be creating standard API in lib/oe to get
things like the remapped name.

I'm actually tempted to throw out he externalsrc symlinks stuff. If our
directory layout is so bad we really should fix that "properly" and
that's something I'm thinking about for the next development cycle...

Cheers,

Richard


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


Re: [OE-core] [PATCH 2/2] linux-firmware: bump to latest linux-firmware git revision

2017-09-13 Thread Burton, Ross
On 13 September 2017 at 01:07, Stefan Agner  wrote:

> +ERROR_QA_remove = "arch"
>

This doesn't remove it from WARN_QA so it will still produce a warning if
it is present.  However the typical way to do this is to set INSANE_SKIP
(which the recipe already does for another package with the same problem).
Of course you can't use INSANE_SKIP without setting a package currently, so
in the interests of scaling I wonder if we should extend insane.bbclass to
support recipe-wide assignments of INSANE_SKIP...

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


[OE-core] State of bitbake world, Failed tasks 2017-09-11

2017-09-13 Thread Martin Jansa
qemux86 shows a bit more failures, because it's built from slightly
older metadata (I've removed some pending changes from master-next after
that build).

Also big chunk of meta-networking changes was finally merged, so the list
of tested changes in next report should be significantly shorter again. Thanks 
Joe.

http://www.openembedded.org/wiki/Bitbake_World_Status

== Number of issues - stats ==
{| class='wikitable'
!|Date   !!colspan='3'|Failed tasks 
!!|Signatures !!colspan='14'|QA !!Comment
|-
||  ||qemuarm   ||qemux86   ||qemux86_64||all   
||already-stripped  ||libdir||textrel   ||build-deps
||file-rdeps||version-going-backwards   ||host-user-contaminated
||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot
||invalid-pkgconfig ||pkgname   ||ldflags   ||compile-host-path 
||  
|-
||2017-09-11||5 ||4 ||5 ||0 ||0 ||0 
||1 ||0 ||0 ||7 ||4 
||0 ||0 ||0 ||0 ||0 
||0 ||0 ||  
|}

== Failed tasks 2017-09-11 ==

INFO: jenkins-job.sh-1.8.28 Complete log available at 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20170912_224314.log

=== common (2) ===
* meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb:do_compile
* 
meta-openembedded/meta-multimedia/recipes-multimedia/musicpd/mpd_0.19.21.bb:do_compile

=== common-x86 (0) ===

=== qemuarm (3) ===
* 
meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc_2.0.2.bb:do_compile
* 
meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb:do_compile
* openembedded-core/meta/recipes-devtools/go/go-dep_0.3.0.bb:do_compile

=== qemux86 (2) ===
* 
meta-openembedded/meta-oe/recipes-devtools/protobuf/protobuf-c_1.2.1.bb:do_compile
* 
meta-openembedded/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.12.3.bb:do_compile

=== qemux86_64 (3) ===
* 
meta-openembedded/meta-initramfs/recipes-devtools/mtd/ubi-utils-klibc_1.5.1.bb:do_compile
* 
meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc_2.0.2.bb:do_configure
* 
virtual:klibc:meta-openembedded/meta-initramfs/recipes-bsp/kexecboot/kexecboot_git.bb:do_configure

=== Number of failed tasks (14) ===
{| class=wikitable
|-
|| qemuarm  || 5 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemuarm.20170911_072424.log/
 || http://errors.yoctoproject.org/Errors/Build/46584/
|-
|| qemux86  || 4 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemux86.20170911_024629.log/
 || http://errors.yoctoproject.org/Errors/Build/46420/
|-
|| qemux86_64   || 5 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemux86-64.20170911_074423.log/
 || http://errors.yoctoproject.org/Errors/Build/46588/
|}

=== PNBLACKLISTs (4) ===

=== QA issues (12) ===
{| class=wikitable
!| Count||Issue
|-
||0 ||already-stripped
|-
||0 ||build-deps
|-
||0 ||compile-host-path
|-
||0 ||file-rdeps
|-
||0 ||installed-vs-shipped
|-
||0 ||invalid-pkgconfig
|-
||0 ||ldflags
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||symlink-to-sysroot
|-
||0 ||unknown-configure-option
|-
||1 ||textrel
|-
||4 ||host-user-contaminated
|-
||7 ||version-going-backwards
|}



=== Incorrect PACKAGE_ARCH or sstate signatures (0) ===

Complete log: 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.signatures.20170911_063504.log/

No issues detected


PNBLACKLISTs:
openembedded-core/:
meta-browser:
meta-openembedded:
meta-filesystems/recipes-filesystems/smbnetfs/smbnetfs_git.bb:PNBLACKLIST[smbnetfs]
 ?= "Fails to build with RSS 
http://errors.yoctoproject.org/Errors/Details/132827/ - the recipe will be 
removed on 2017-09-01 unless the issue is fixed"
meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring_2.32.1.bb:PNBLACKLIST[gnome-keyring]
 ?= "This version conflicts with gcr from oe-core - the recipe will be removed 
on 2017-09-01 unless the issue is fixed"
meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb:PNBLACKLIST[lksctp-tools]
 ?= "${@bb.utils.contains('DISTRO_FEATURES', 'ld-is-gold', "BROKEN: fails to 
link against sctp_connectx symbol", '', d)}"
meta-oe/recipes-support/system-setup-keyboard/system-setup-keyboard_0.8.8.bb:PNBLACKLIST[system-setup-keyboard]
 ?= "Depends on blacklisted system-config-keyboard-native - the recipe will be 
removed on 2017-09-01 unless the issue is fixed"
meta-qt5:
PNBLACKLIST[android-system] = "depends on lxc from meta-virtualiazation which 
isn't included in my world builds"
PNBLACKLIST[bigbuckbunny-1080p] = "big and doesn't really need to be tested so 
much"
PNBLACKLIST[bigbuckbunny-480p] = "big and doesn't really need to be test

Re: [OE-core] [PATCH v8 1/3] kernel: Move Device Tree support to kernel.bbclass

2017-09-13 Thread Richard Purdie
On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
> The Device Tree is commonly used but it is still kept as a .inc file
> instead of a proper class. Instead now we move the Device Tree code
> to
> a kernel-devicetree class and automatically enable it when the
> KERNEL_DEVICETREE variable is set.
> 
> To avoid breakage in existing layers, we kept a linux-dtb.inc file
> which raises a warning telling the user about the change so in next
> release this can be removed.

Still causing breakage:

https://autobuilder.yocto.io/builders/nightly-mips/builds/469/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-arm64/builds/454/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-mips-lsb/builds/464/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-mips64/builds/467/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-multilib/builds/489/steps/BuildImages_5/logs/stdio
https://autobuilder.yocto.io/builders/nightly-ppc/builds/488/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/477/steps/BuildImages/logs/stdio


All look like racing of do_compile_devicetree and do_make_scripts?

https://autobuilder.yocto.io/builders/nightly-arm/builds/537/steps/Buil
ding%20Toolchain%20Images/logs/stdio

"package kernel-devicetree-4.12.10+git0+42965d664f_fd16268214-r0.1.qemuarm does 
not have a compatible architecture"

Cheers,

Richard


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


Re: [OE-core] [PATCH v8 3/3] kernel-devicetree.bbclass: Add support to generate append to kernel

2017-09-13 Thread André Draszik
On Tue, 2017-09-12 at 17:36 -0300, Otavio Salvador wrote:
> The are use cases where the Device Tree appended to the kernel is
> convinient, so we generate the bundle concatenating the kernel (and
> potentionally the initramfs) and the Device Tree binaries.
> 
> To enable it, set KERNEL_DEVICETREE_BUNDLE variable to '1'
> 
> Signed-off-by: Otavio Salvador 
> ---
> 
> Changes in v8:
> - rework append support to support ARM and MIPS (obi)
> 
> Changes in v7:
> - simplified code
> - rename bundle to use .bin extension
> 
> Changes in v6: None
> Changes in v5:
> - add support for initramfs bundle
> 
> Changes in v4:
> - new patch
> 
> Changes in v3: None
> Changes in v2: None
> 
>  meta/classes/kernel-devicetree.bbclass | 62
> +-
>  1 file changed, 61 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/kernel-devicetree.bbclass b/meta/classes/kernel-
> devicetree.bbclass
> index 8723f24212..c618594c96 100644
> --- a/meta/classes/kernel-devicetree.bbclass
> +++ b/meta/classes/kernel-devicetree.bbclass
> @@ -1,6 +1,13 @@
>  # Support for device tree generation
> -PACKAGES_append = " kernel-devicetree"
> +PACKAGES_append = " \
> +kernel-devicetree \
> +${@['kernel-image-zimage-bundle',
> ''][d.getVar('KERNEL_DEVICETREE_BUNDLE') != '1']} \
> +"
>  FILES_kernel-devicetree = "/${KERNEL_IMAGEDEST}/*.dtb
> /${KERNEL_IMAGEDEST}/*.dtbo"
> +FILES_kernel-image-zimage-bundle = "/${KERNEL_IMAGEDEST}/zImage-
> *.dtb.bin"
> +
> +# Generate kernel+devicetree bundle
> +KERNEL_DEVICETREE_BUNDLE ?= "0"
>  
>  normalize_dtb () {
>   DTB="$1"
> @@ -20,6 +27,38 @@ get_real_dtb_path_in_kernel () {
>   echo "${DTB_PATH}"
>  }
>  
> +
> +do_configure_devicetree() {
> + if [ "${KERNEL_DEVICETREE_BUNDLE}" = "1" ]; then
> + if echo ${KERNEL_IMAGETYPE_FOR_MAKE} | grep -q 'zImage';
> then
> + case "${ARCH}" in
> + "arm")
> + config="${B}/.config"
> + if ! grep -q 'CONFIG_ARM_APPENDED_DTB=y'
> $config; then
> + bbwarn 'CONFIG_ARM_APPENDED_DTB
> is NOT enabled in the kernel. Enabling it to allow the kernel to boot with
> the Device Tree appended!'
> + sed -i "/CONFIG_ARM_APPENDED_DTB[
> =]/d" $config
> + echo "CONFIG_ARM_APPENDED_DTB=y"
> >> $config
> + echo "#
> CONFIG_ARM_ATAG_DTB_COMPAT is not set" >> $config
> + fi
> + ;;
> + "mips")

AFAICS, zImage is specific to x86 and arm, all other arches, including MIPS
have no zImage Makefile target, so we'll never get here.


Cheers,
Andre'

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


[OE-core] [PATCH] binutils: bump SRCREV to latest 2.29 branch

2017-09-13 Thread Yi Zhao
Update to the latest commit on the 2.29 branch to fix CVEs:
CVE-2017-12448, CVE-2017-12449. CVE-2017-12451, CVE-2017-12452,
CVE-2017-12454, CVE-2017-12455, CVE-2017-12456, CVE-2017-12457,
CVE-2017-12458, CVE-2017-12459, CVE-2017-12799, CVE-2017-12967,
CVE-2017-13710

References:
https://nvd.nist.gov/vuln/detail/CVE-2017-12448
https://nvd.nist.gov/vuln/detail/CVE-2017-12449
https://nvd.nist.gov/vuln/detail/CVE-2017-12451
https://nvd.nist.gov/vuln/detail/CVE-2017-12452
https://nvd.nist.gov/vuln/detail/CVE-2017-12454
https://nvd.nist.gov/vuln/detail/CVE-2017-12455
https://nvd.nist.gov/vuln/detail/CVE-2017-12456
https://nvd.nist.gov/vuln/detail/CVE-2017-12457
https://nvd.nist.gov/vuln/detail/CVE-2017-12458
https://nvd.nist.gov/vuln/detail/CVE-2017-12459
https://nvd.nist.gov/vuln/detail/CVE-2017-12799
https://nvd.nist.gov/vuln/detail/CVE-2017-12967
https://nvd.nist.gov/vuln/detail/CVE-2017-13710

Signed-off-by: Yi Zhao 
---
 meta/recipes-devtools/binutils/binutils-2.29.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils-2.29.inc 
b/meta/recipes-devtools/binutils/binutils-2.29.inc
index 8e38093..27d46eb 100644
--- a/meta/recipes-devtools/binutils/binutils-2.29.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.29.inc
@@ -18,7 +18,7 @@ BINUPV = "${@binutils_branch_version(d)}"
 
 UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P\d+_(\d_?)*)"
 
-SRCREV = "dd241688aee3712803a917315df089f4c714b5ef"
+SRCREV = "37e991bb143ca2106330bcdc625590d53838b7a1"
 SRC_URI = "\
  
git://sourceware.org/git/binutils-gdb.git;branch=binutils-${BINUPV}-branch;protocol=git
 \
  file://0003-configure-widen-the-regexp-for-SH-architectures.patch \
-- 
2.7.4

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


[OE-core] [PATCH] binutils: bump SRCREV to latest 2.29 branch

2017-09-13 Thread Yi Zhao
There are 47 effecitve commits since last update. All changes are for 
bug fixing, so it is safe to update:

$ git log --oneline dd24168...binutils-2_29-branch | grep -v "Automatic date"
4c73077 Import fix from mainline that fixes buffer overrun errors when parsing 
corrupt DWARF debug information string sections.
38d47c2 PowerPC64 --plt-align
21ac709 x86: Remove restriction on NOTRACK prefix position
bb0216e x86: Check for valid PLT section size
64aa124 Import patches from mainline to fix minor binutils bugs:
5709459 Import patch from mainline to fix memory leak.
81d80fc Import parch from mainline to prevent buffer overrun.
35e0127 Import patch from mainline to improve padding of .eh_frame sections.
d6f8dea Import patch from mainline to fix address violation errors when parsing 
corrupt ELF binaries.
3a6dbb3 Import patch from mainline to allows 16-bit MSP430 absolute branches to 
be relaxed ino 1-bit PC-relative branches.
deeb3d2 Import patch from mainline to fix address violation errors when parsing 
corrupt VMS and MACHO binaries.
a541116 Import patch from mainline to improve reporting of corrupt archives.
7e693dd Import patch from mainline to fix address violations when parsing 
corrupt COFF binaries
353c868 Import patch from mainline to replace an abort when parsing a corrupt 
COFF binary with an error message instead.
4b2b2ee PR22067, x86 check_relocs invalid read
78a6a9c x86-64: Check ELF_COMMON_DEF_P for common symbols
e6d76f0 x86: Correct unwind information for the second PLT
6bdd626 Prevent an address violation parsing corrupt DWARF information by 
fixing the test for an overlong debug line info structure.
d4ea954 Import latest bug fixes for the libiberty sources from GCC mainline.
30326b0 Check for an invalid note size when parsing ELF notes.
aceaeff Fix buffer overrun when parsing an ELF attribute string that is not NUL 
terminated.
c1c56a2 Add updated French translations for opcodes and gprof
31939e5 MIPS/BFD: Correct microMIPS cross-mode BAL to JALX relaxation
012daee MIPS/GAS: Also respect `-mignore-branch-isa' with MIPS16 code
ee5d69b Import from mainline to fix PR gold/21868.
796337a Import patch from mainline to fix address violation issues when parsing 
corrupt binaries.
188f4b1 [GOLD] Symbol flag for PowerPC64 localentry:0 tracking
dbb8f8b ld: Early detection of orphans we know will be discarded
e59c711 Remove pr19161 test hppa xfail
3c08b8d Make undefined symbols in allocate_dynrelocs dynamic
f399679 Make __start/__stop symbols protected visibility
3256967 Collision between NT_GNU_BUILD_ATTRIBUTE_OPEN and NT_PPC_VMX
ee24a27 PR21910, segfault in common symbol override test when hash-style=gnu
bf234c7 Don't fail in elf32_hppa_set_gp
7476906 Add more targets to the list of architectures not supporting format 
changing during linking.  Fix seg-faults triggered when this is attempted.
247a9b4 __tls_get_addr_opt stub eh_frame info
eaaf8fb ppc32 tlsopt tests
ebe412a Fix buffer overrun when parsing a corrupt tekhex binary.
ba07ff6 [AArch64] Skip IFUNC relocations in debug sections
6f0f222 [AArch64] Fix PR18841 ifunc relocation ordering
9bb8332 [Patch AArch64] Turn lr, fp, ip0 and ip1 into proper aliases
ffb6dbf ld: Replace --rpath with -Wl,--rpath,
df41feb ld: Restore linker scripts in PR ld/21884 tests
d9c6cab Fix i686-nacl and x86_64-nacl pr21884 failures
4a1c35c Do not choose a non-ELF format input file to hold the linker created 
GOT sections.
5d8b167 Backport fix for a Darwin x86 assembler bug from the mainline.
cd83295 [ARM] Don't warn on REG_SP when used in CRC32 instructions


Yi Zhao (1):
  binutils: bump SRCREV to latest 2.29 branch

 meta/recipes-devtools/binutils/binutils-2.29.inc | 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