[OE-core] [PATCH] checklayer: remove reference to undefined class

2018-03-14 Thread Anuj Mittal 
LayerError doesn't exist and will lead to an error when this failure
code path is hit.

Signed-off-by: Anuj Mittal 
---
 scripts/lib/checklayer/__init__.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/lib/checklayer/__init__.py 
b/scripts/lib/checklayer/__init__.py
index 6395261..288c457 100644
--- a/scripts/lib/checklayer/__init__.py
+++ b/scripts/lib/checklayer/__init__.py
@@ -42,8 +42,8 @@ def _get_layer_collections(layer_path, lconf=None, data=None):
 ldata.setVar('LAYERDIR', layer_path)
 try:
 ldata = bb.parse.handle(lconf, ldata, include=True)
-except BaseException as exc:
-raise LayerError(exc)
+except:
+raise RuntimeError("Parsing of layer.conf from layer: %s failed" % 
layer_path)
 ldata.expandVarref('LAYERDIR')
 
 collections = (ldata.getVar('BBFILE_COLLECTIONS') or '').split()
-- 
2.7.4

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

[OE-core] [PATCH] python3: add readline to PACKAGECONFIG

2018-03-14 Thread Anuj Mittal 
Provide a way to make readline dependency optional in case someone
might want to use BSD alternative editline instead.

Using editline would need some changes though (python issue13501).

Signed-off-by: Anuj Mittal 
---
 meta/recipes-devtools/python/python3_3.5.4.bb | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3_3.5.4.bb 
b/meta/recipes-devtools/python/python3_3.5.4.bb
index a94d009..9815d50 100644
--- a/meta/recipes-devtools/python/python3_3.5.4.bb
+++ b/meta/recipes-devtools/python/python3_3.5.4.bb
@@ -1,6 +1,6 @@
 require recipes-devtools/python/python.inc
 
-DEPENDS = "python3-native libffi bzip2 gdbm openssl readline sqlite3 zlib 
virtual/libintl xz"
+DEPENDS = "python3-native libffi bzip2 gdbm openssl sqlite3 zlib 
virtual/libintl xz"
 
 PR = "${INC_PR}.0"
 PYTHON_MAJMIN = "3.5"
@@ -76,6 +76,9 @@ export CROSSPYTHONPATH = 
"${STAGING_LIBDIR_NATIVE}/python${PYTHON_MAJMIN}/lib-dy
 # No ctypes option for python 3
 PYTHONLSBOPTS = ""
 
+PACKAGECONFIG ??= "readline"
+PACKAGECONFIG[readline] = ",,readline"
+
 do_configure_append() {
rm -f ${S}/Makefile.orig
autoreconf -Wcross --verbose --install --force --exclude=autopoint 
../Python-${PV}/Modules/_ctypes/libffi
-- 
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 "perf: fix packaging of scripti..." and 1 more (rev2)

2018-03-14 Thread Patchwork 
== Series Details ==

Series: "perf: fix packaging of scripti..." and 1 more (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/11183/
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 073d8d0010)



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

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

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

[OE-core] [PATCH v2] perf: enable support for libaudit

2018-03-14 Thread Anuj Mittal 
perf needs audit-python to be able to show syscall names and for
'perf trace' to work.

Enable dependency on audit-python if present in PACKAGECONFIG. It's
disabled by default since audit as of now is in meta-selinux.

Fixes [YOCTO #3343]
Fixes [YOCTO #3358]

Signed-off-by: Anuj Mittal 
---
 meta/recipes-kernel/perf/perf.bb | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
index d798492..872b5f0 100644
--- a/meta/recipes-kernel/perf/perf.bb
+++ b/meta/recipes-kernel/perf/perf.bb
@@ -22,6 +22,9 @@ PACKAGECONFIG[libnuma] = ",NO_LIBNUMA=1"
 PACKAGECONFIG[systemtap] = ",NO_SDT=1,systemtap"
 PACKAGECONFIG[jvmti] = ",NO_JVMTI=1"
 
+# libaudit support would need scripting to be enabled
+PACKAGECONFIG[audit] = ",NO_LIBAUDIT=1,audit"
+
 DEPENDS = " \
 virtual/${MLPREFIX}libc \
 ${MLPREFIX}elfutils \
@@ -216,7 +219,7 @@ PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl 
${PN}-python"
 RDEPENDS_${PN} += "elfutils bash"
 RDEPENDS_${PN}-doc += "man"
 RDEPENDS_${PN}-archive =+ "bash"
-RDEPENDS_${PN}-python =+ "bash python python-modules"
+RDEPENDS_${PN}-python =+ "bash python python-modules 
${@bb.utils.contains('PACKAGECONFIG', 'audit', 'audit-python', '', d)}"
 RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
 RDEPENDS_${PN}-tests =+ "python"
 
-- 
2.7.4

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

[OE-core] [PATCH] uninative: Add compatiblity version check

2018-03-14 Thread Richard Purdie 
If glibc is newer on the host than in uninative, the failure mode is
pretty nasty for clusters where the sstate is shared, including the Yocto
Project autobuilder.

This check aborts the use of uninative in such scenarios where a newer
glibc version appears and avoids corruption of sstate caches.

We use ldd to check the glibc version since that is included in libc-bin
(or equivalent) which locales use so it should always be present.

Signed-off-by: Richard Purdie 
---
 meta/classes/uninative.bbclass   | 7 +++
 meta/conf/distro/include/yocto-uninative.inc | 2 ++
 2 files changed, 9 insertions(+)

diff --git a/meta/classes/uninative.bbclass b/meta/classes/uninative.bbclass
index 670efa9..1723364 100644
--- a/meta/classes/uninative.bbclass
+++ b/meta/classes/uninative.bbclass
@@ -77,6 +77,11 @@ python uninative_event_fetchloader() {
 except FileExistsError:
 pass
 
+# ldd output is "ldd (Ubuntu GLIBC 2.23-0ubuntu10) 2.23", extract last 
option from first line
+glibcver = subprocess.check_output(["ldd", 
"--version"]).decode('utf-8').split('\n')[0].split()[-1]
+if bb.utils.vercmp_string(d.getVar("UNINATIVE_MAXGLIBCVERSION"), 
glibcver) < 0:
+raise RuntimeError("Your host glibc verson (%s) is newer than that 
in uninative (%s). Disabling uninative so that sstate is not corrupted." % 
(glibcver, d.getVar("UNINATIVE_MAXGLIBCVERSION")))
+
 cmd = d.expand("\
 mkdir -p ${UNINATIVE_STAGING_DIR}-uninative; \
 cd ${UNINATIVE_STAGING_DIR}-uninative; \
@@ -94,6 +99,8 @@ ${UNINATIVE_STAGING_DIR}-uninative/relocate_sdk.py \
 
 enable_uninative(d)
 
+except RuntimeError as e:
+bb.warn(str(e))
 except bb.fetch2.BBFetchException as exc:
 bb.warn("Disabling uninative as unable to fetch uninative tarball: %s" 
% str(exc))
 bb.warn("To build your own uninative loader, please bitbake 
uninative-tarball and set UNINATIVE_TARBALL appropriately.")
diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index b3f8c24..cd5fc0b 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,6 +6,8 @@
 # to the distro running on the build machine.
 #
 
+UNINATIVE_MAXGLIBCVERSION = "2.27"
+
 UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/1.8/";
 UNINATIVE_CHECKSUM[i686] ?= 
"427ce522ec97f65c75fd89587d90ef789e8cbca4a617abc4b5822abb01c2d0ae"
 UNINATIVE_CHECKSUM[x86_64] ?= 
"de4947e98e09e1432d069311cc2093974ecb9138a714fd5466f73524de66a693"
-- 
2.7.4

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

Re: [OE-core] [rocko][PATCH 1/8] Revert "waf.bbclass: explicitly pass bindir and libdir if supported"

2018-03-14 Thread Richard Purdie 
On Wed, 2018-03-14 at 16:28 +0100, Martin Jansa wrote:
> ping, this was in rocko-next for a while and then it disappeared.

I think it was conflicting with some work Armin was doing so please
sync with him and how he plans to sort things.

Cheers,

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

[OE-core] [PATCH] slang: 2.3.1a -> 2.3.2

2018-03-14 Thread Huang Qiyu 
Upgrade slang from 2.3.1a to 2.3.2.

Signed-off-by: Huang Qiyu 
---
 meta/recipes-extended/slang/{slang_2.3.1a.bb => slang_2.3.2.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-extended/slang/{slang_2.3.1a.bb => slang_2.3.2.bb} (95%)

diff --git a/meta/recipes-extended/slang/slang_2.3.1a.bb 
b/meta/recipes-extended/slang/slang_2.3.2.bb
similarity index 95%
rename from meta/recipes-extended/slang/slang_2.3.1a.bb
rename to meta/recipes-extended/slang/slang_2.3.2.bb
index 0585c14..87fd41a 100644
--- a/meta/recipes-extended/slang/slang_2.3.1a.bb
+++ b/meta/recipes-extended/slang/slang_2.3.2.bb
@@ -22,8 +22,8 @@ SRC_URI = 
"http://www.jedsoft.org/releases/${BPN}/${BP}.tar.bz2 \
file://run-ptest \
   "
 
-SRC_URI[md5sum] = "c5235313042ed0e71ec708f7b85ec241"
-SRC_URI[sha256sum] = 
"54f0c3007fde918039c058965dffdfd6c5aec0bad0f4227192cc486021f08c36"
+SRC_URI[md5sum] = "c2d5a7aa0246627da490be4e399c87cb"
+SRC_URI[sha256sum] = 
"fc9e3b0fc4f67c3c1f6d43c90c16a5c42d117b8e28457c5b46831b8b5d3ae31a"
 
 UPSTREAM_CHECK_URI = "http://www.jedsoft.org/releases/slang/";
 PREMIRRORS_append = "\n http://www.jedsoft.org/releases/slang/.* 
http://www.jedsoft.org/releases/slang/old/ \n"
-- 
2.7.4



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

Re: [OE-core] [PATCH] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty

2018-03-14 Thread Khem Raj 
On Wed, Mar 14, 2018 at 6:57 PM Christopher Larson 
wrote:

> On Wed, Mar 14, 2018 at 6:48 PM, Khem Raj  wrote:
>
>> We allow to set LINKER_HASH_STYLE to be empty so this would fail
>> since --with-linker-hash-style needs an argument and cant be empty
>>
>> Signed-off-by: Khem Raj 
>> ---
>>  meta/recipes-devtools/gcc/gcc-7.3.inc | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc
>> b/meta/recipes-devtools/gcc/gcc-7.3.inc
>> index d56d2c5e06..cc428ad3ef 100644
>> --- a/meta/recipes-devtools/gcc/gcc-7.3.inc
>> +++ b/meta/recipes-devtools/gcc/gcc-7.3.inc
>> @@ -100,7 +100,7 @@ EXTRA_OECONF_BASE = "\
>>  --disable-bootstrap \
>>  --disable-libmudflap \
>>  --with-system-zlib \
>> ---with-linker-hash-style=${LINKER_HASH_STYLE} \
>> +
>> ${@['','--with-linker-hash-style=${LINKER_HASH_STYLE}'][d.getVar('LINKER_HASH_STYLE')
>> != '']} \
>>
>
> That syntax was a hack around the fact that python didn’t have inline if
> statements at the time we started the project, but it does now:
>
> ${@‘—with-linker-hash-style=${LINKER_HASH_STYLE}’ if
> ‘${LINKER_HASH_STYLE}’ else ‘'}
>

Yes that looks more elegant I will test it out and send another patch

> --
> Christopher Larson
> kergoth at gmail dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Senior Software Engineer, Mentor Graphics
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 0/3] systemd & systemd-boot: upgrade to 237

2018-03-14 Thread ChenQi 

ping

Is there some problem with this patchset?

Regards,
Chen Qi

On 03/12/2018 04:38 PM, Chen Qi wrote:

Changes in V2:
* Rebase against latest master to resolve conflicts


The following changes since commit 5350ee317740751f2417c1794dd39d3880347dbf:

   yocto-uninative: Upgrade to 1.8 version with glibc 2.27 (2018-03-11 06:27:02 
-0700)

are available in the git repository at:

   git://git.pokylinux.org/poky-contrib ChenQi/systemd-237
   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/systemd-237

Chen Qi (3):
   systemd: upgrade to 237
   systemd: fix build failure for qemux86 and qemuppc with musl
   systemd-boot: upgrade to 237

  .../{systemd-boot_234.bb => systemd-boot_237.bb}   |  31 ++-
  meta/recipes-core/systemd/systemd.inc  |   2 +-
  ...01-Also-check-i386-i586-and-i686-for-ia32.patch |  28 +++
  ...efi_cc-and-efi_ld-correctly-when-cross-co.patch |  62 +
  ...ck-protector-flags-to-workaround-musl-bui.patch |  33 +++
  ...v-when-secure-versions-are-not-available.patch} |  21 +-
  ...te-presets-after-generators-have-run-6526.patch |  69 --
  ...any-initialization-steps-when-running-in-.patch | 163 -
  ...update-header-file-to-detect-memfd_create.patch |  28 ---
  ...t-install-dependency-links-at-install-tim.patch |  81 +++
  ...c-Check-if-memfd_create-is-already-define.patch |  27 ---
  .../systemd/0003-fileio-include-sys-mman.h.patch   |  26 --
  ...pper-instead-of-looking-for-relative-opti.patch |  64 +
  ...004-implment-systemd-sysv-install-for-OE.patch} |   8 +-
  ...t-install-dependency-links-at-install-tim.patch |  74 --
  ...patch => 0005-rules-whitelist-hd-devices.patch} |   9 +-
  ...6-Make-root-s-home-directory-configurable.patch |  78 ++
  ...vert-rules-remove-firmware-loading-rules.patch} |   8 +-
  ...-check-for-missing-canonicalize_file_name.patch |  63 -
  ...pper-instead-of-looking-for-relative-opti.patch |  40 ---
  .../systemd/0008-Do-not-enable-nss-tests.patch |  35 ---
  ...remove-userspace-firmware-loading-suppor.patch} | 204 +---
  ...=> 0009-remove-duplicate-include-uchar.h.patch} |  14 +-
  .../0010-check-for-uchar.h-in-meson.build.patch|  45 
  ...nes-Build-conditionally-when-HAVE_MYHOSTN.patch |  38 ---
  ...l-don-t-fail-if-libc-doesn-t-support-IDN.patch} |  26 +-
  ...es-watch-metadata-changes-in-ide-devices.patch} |   8 +-
  ...3-Make-root-s-home-directory-configurable.patch | 155 
  ...lback-parse_printf_format-implementation.patch} |  86 ---
  ...sic-missing.h-check-for-missing-strndupa.patch} |  96 
  ...f-GLOB_BRACE-and-GLOB_ALTDIRFUNC-is-not-.patch} |  30 +--
  ...ssing.h-check-for-missing-__compar_fn_t-.patch} |  18 +-
  ...patch => 0017-Include-netinet-if_ether.h.patch} |  55 +++--
  ...-check-for-missing-canonicalize_file_name.patch |  47 
  .../0018-check-for-uchar.h-in-configure.patch  |  44 
  ...le-nss-tests-if-nss-systemd-is-not-enable.patch |  29 +++
  ...xdecoct.c-Include-missing.h-for-strndupa.patch} |  15 +-
  ...c-Disable-tests-for-missing-typedefs-in-.patch} |  39 ++-
  ...=> 0022-don-t-use-glibc-specific-qsort_r.patch} |  26 +-
  ...ss-AT_SYMLINK_NOFOLLOW-flag-to-faccessat.patch} |  22 +-
  ...n_t-is-glibc-specific-use-raw-signature-.patch} |  14 +-
  ...ATH_WTMPX-and-_PATH_UTMPX-if-not-defined.patch} |  16 +-
  ...> 0026-Use-uintmax_t-for-handling-rlim_t.patch} |  22 +-
  .../0027-remove-nobody-user-group-checking.patch   |  63 +
  .../0028-add-missing-FTW_-macros-for-musl.patch|  50 
  ...nes-Build-conditionally-when-ENABLE_MYHOS.patch |  43 
  ...-of-__register_atfork-for-non-glibc-build.patch |  45 
  ...-ULONG_LONG_MAX-definition-in-case-of-mus.patch |  30 +++
  meta/recipes-core/systemd/systemd/run-ptest|   6 -
  .../systemd/{systemd_234.bb => systemd_237.bb} | 270 +
  50 files changed, 1211 insertions(+), 1295 deletions(-)
  rename meta/recipes-core/systemd/{systemd-boot_234.bb => systemd-boot_237.bb} 
(58%)
  create mode 100644 
meta/recipes-core/systemd/systemd/0001-Also-check-i386-i586-and-i686-for-ia32.patch
  create mode 100644 
meta/recipes-core/systemd/systemd/0001-Fix-to-run-efi_cc-and-efi_ld-correctly-when-cross-co.patch
  create mode 100644 
meta/recipes-core/systemd/systemd/0001-Remove-fstack-protector-flags-to-workaround-musl-bui.patch
  rename 
meta/recipes-core/systemd/systemd/{0004-Use-getenv-when-secure-versions-are-not-available.patch
 => 0001-Use-getenv-when-secure-versions-are-not-available.patch} (53%)
  delete mode 100644 
meta/recipes-core/systemd/systemd/0001-core-evaluate-presets-after-generators-have-run-6526.patch
  delete mode 100644 
meta/recipes-core/systemd/systemd/0001-main-skip-many-initialization-steps-when-running-in-.patch
  delete mode 100644 
meta/recipes-core/systemd/systemd/0001-meson-update-header-file-to-detect-memfd_create.patch
  create mode 100644 
meta/recipes-core/systemd/systemd/0002-binfmt-Don-t-install-dependency-link

Re: [OE-core] [PATCH] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty

2018-03-14 Thread Christopher Larson 
On Wed, Mar 14, 2018 at 6:48 PM, Khem Raj  wrote:

> We allow to set LINKER_HASH_STYLE to be empty so this would fail
> since --with-linker-hash-style needs an argument and cant be empty
>
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/gcc/gcc-7.3.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc
> b/meta/recipes-devtools/gcc/gcc-7.3.inc
> index d56d2c5e06..cc428ad3ef 100644
> --- a/meta/recipes-devtools/gcc/gcc-7.3.inc
> +++ b/meta/recipes-devtools/gcc/gcc-7.3.inc
> @@ -100,7 +100,7 @@ EXTRA_OECONF_BASE = "\
>  --disable-bootstrap \
>  --disable-libmudflap \
>  --with-system-zlib \
> ---with-linker-hash-style=${LINKER_HASH_STYLE} \
> +
> ${@['','--with-linker-hash-style=${LINKER_HASH_STYLE}'][d.getVar('LINKER_HASH_STYLE')
> != '']} \
>

That syntax was a hack around the fact that python didn’t have inline if
statements at the time we started the project, but it does now:

${@‘—with-linker-hash-style=${LINKER_HASH_STYLE}’ if
‘${LINKER_HASH_STYLE}’ else ‘'}
-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty

2018-03-14 Thread Khem Raj 
We allow to set LINKER_HASH_STYLE to be empty so this would fail
since --with-linker-hash-style needs an argument and cant be empty

Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/gcc/gcc-7.3.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc 
b/meta/recipes-devtools/gcc/gcc-7.3.inc
index d56d2c5e06..cc428ad3ef 100644
--- a/meta/recipes-devtools/gcc/gcc-7.3.inc
+++ b/meta/recipes-devtools/gcc/gcc-7.3.inc
@@ -100,7 +100,7 @@ EXTRA_OECONF_BASE = "\
 --disable-bootstrap \
 --disable-libmudflap \
 --with-system-zlib \
---with-linker-hash-style=${LINKER_HASH_STYLE} \
+
${@['','--with-linker-hash-style=${LINKER_HASH_STYLE}'][d.getVar('LINKER_HASH_STYLE')
 != '']} \
 --enable-linker-build-id \
 --with-ppl=no \
 --with-cloog=no \
-- 
2.16.2

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

Re: [OE-core] [morty][PATCH] buildhistory: fix latest_srcrev in the common case

2018-03-14 Thread Andre McCurdy 
On Tue, Feb 27, 2018 at 5:06 PM, Andre McCurdy  wrote:
> From: Christopher Larson 
>
> buildhistory was writing srcrevs.values() as SRCREV when only one
> srcrev/branch exists. This returns a view of the dictionary values in python
> 3, and used to return a list in python 2, neither of which is an appropriate
> value for SRCREV. It was resulting in latest_srcrev files like this:
>
> # SRCREV = "346584bf6e38232be8773c24fd7dedcbd7b3d9ed"
> SRCREV = "dict_values(['346584bf6e38232be8773c24fd7dedcbd7b3d9ed'])"
>
> Which in turn would result in invalid output in buildhistory-collect-srcrevs.
> Fix by calling `next(iter())` on the `.values()`

Ping.

> Signed-off-by: Christopher Larson 
> Signed-off-by: Ross Burton 
> (cherry picked from commit ef826a395612400924bbe49859d256b237ff59e1)
> Signed-off-by: Andre McCurdy 
> ---
>  meta/classes/buildhistory.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/buildhistory.bbclass 
> b/meta/classes/buildhistory.bbclass
> index 3a5bc2c..d82e9bb 100644
> --- a/meta/classes/buildhistory.bbclass
> +++ b/meta/classes/buildhistory.bbclass
> @@ -833,7 +833,7 @@ python write_srcrev() {
>  f.write('# SRCREV_%s = "%s"\n' % (name, orig_srcrev))
>  f.write('SRCREV_%s = "%s"\n' % (name, srcrev))
>  else:
> -f.write('SRCREV = "%s"\n' % srcrevs.values())
> +f.write('SRCREV = "%s"\n' % next(iter(srcrevs.values(
>  if len(tag_srcrevs) > 0:
>  for name, srcrev in tag_srcrevs.items():
>  f.write('# tag_%s = "%s"\n' % (name, srcrev))
> --
> 1.9.1
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Recipe for Linux page-types tool

2018-03-14 Thread Martin Vuille 

page-types is a simple Linux kernel debugging tool to list information about
the state of virtual memory (VM) pages.

The source is distributed as part of the kernel tree: tools/vm/page-types.c

MV

On 03/14/18 11:22, Martin Vuille wrote:

I have a recipe for building the page-types Linux kernel VM tool.
Is there any interest in this?
If so, to what project/layer should I send it?

MV

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

Re: [OE-core] [rocko][PATCH 1/8] Revert "waf.bbclass: explicitly pass bindir and libdir if supported"

2018-03-14 Thread Vincent Prince 
Hi Stefan,

If I remember correctly, you submitted this feature?

Best Regards,
Vincent

2018-03-14 16:28 GMT+01:00 Martin Jansa :

> ping, this was in rocko-next for a while and then it disappeared.
>
> On Sun, Mar 11, 2018 at 1:43 AM, Martin Jansa 
> wrote:
>
>> * this doesn't work correctly as discussed in:
>>   http://lists.openembedded.org/pipermail/openembedded-commits
>> /2018-January/218460.html
>> * some of the issues were fixed in master since then
>>   but not all, so revert it until it's completely resolved
>>
>> This reverts commit eac21f981337bfaddb2d67161a1ff049158041ce.
>>
>> Signed-off-by: Martin Jansa 
>> ---
>>  meta/classes/waf.bbclass | 17 +
>>  1 file changed, 1 insertion(+), 16 deletions(-)
>>
>> diff --git a/meta/classes/waf.bbclass b/meta/classes/waf.bbclass
>> index acbda278a2..c4698e910a 100644
>> --- a/meta/classes/waf.bbclass
>> +++ b/meta/classes/waf.bbclass
>> @@ -25,23 +25,8 @@ def get_waf_parallel_make(d):
>>
>>  return ""
>>
>> -python waf_preconfigure() {
>> -from distutils.version import StrictVersion
>> -srcsubdir = d.getVar('S')
>> -wafbin = os.path.join(srcsubdir, 'waf')
>> -status, result = oe.utils.getstatusoutput(wafbin + " --version")
>> -if status != 0:
>> -bb.warn("Unable to execute waf --version, exit code %d. Assuming
>> waf version without bindir/libdir support." % status)
>> -return
>> -version = result.split()[1]
>> -if StrictVersion(version) >= StrictVersion("1.8.7"):
>> -d.setVar("WAF_EXTRA_CONF", "--bindir=${bindir}
>> --libdir=${libdir}")
>> -}
>> -
>> -do_configure[prefuncs] += "waf_preconfigure"
>> -
>>  waf_do_configure() {
>> -   ${S}/waf configure --prefix=${prefix} ${WAF_EXTRA_CONF}
>> ${EXTRA_OECONF}
>> +   ${S}/waf configure --prefix=${prefix} ${EXTRA_OECONF}
>>  }
>>
>>  waf_do_compile()  {
>> --
>> 2.15.1
>>
>>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

2018-03-14 Thread Jason Wessel 


I can't seem to find where cmake's python checker magically decides the name of 
the shared object, but I did find an override, so you can drop the patch.   I 
had even gone so far as to simply make a zero length file instead of the 
symlink, and everything still built and run.  It is just some cmake detection 
which is broken.  The ubuntu/debian systems where this code is heavily tested 
all provide a link for the libboost_python.so which explains why this never 
turned up previously.  They don't get the option to pick python2 or python3 for 
boost, they always get both for now.

The override to build with python boost for cmake and caffe is as follows:

cmake -DBoost_PYTHON_LIBRARY_DEBUG=/usr/lib64/libboost_python3.so \
   -DBoost_PYTHON_LIBRARY_RELEASE=/usr/lib64/libboost_python3.so \
   -DBLAS=Open \
   ..


Cheers,
Jason.


On 03/14/2018 09:55 AM, Jason Wessel wrote:

Perhaps a bug in the cmake detect which is part of boost, because I am not 
using python2 for caffe.

I used the path of least resistance because as far as I could tell boost only 
let you build one or the other and in my case it was the python3 boost api. In 
the end caffe was working and all the python3 tests with the Movidius SDK pass 
(which use python3).

Jason.

On 03/14/2018 09:50 AM, Burton, Ross wrote:

I thought that boost_python was the py2 binary, and boost_python3 was the py3 
one?  Is this not a bug in caffe?

On 13 March 2018 at 03:08, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:

When using an image built with the Yocto Project which has a compiler
and all the required libraries, projects such as caffe for the
Movidius SDK which use python3 and boost fail to build because they
look for libboost_python.so.  The error that cmake returns doesn't
even point to the fact that this is why the configuration fails.

Example showing the problem with the missing symlink:

  git clone https://github.com/weiliu89/caffe.git 

  cd caffe
  mkdir build
  cd build
  cmake -DBLAS=Open ..

-- Configuring done
CMake Error at CMakeLists.txt:85 (add_dependencies):
  The dependency target "pycaffe" of target "pytest" does not exist.


Conditionally creating the link when building python3 support into
boost is all that is needed.

Signed-off-by: Jason Wessel mailto:jason.wes...@windriver.com>>
---
 meta/recipes-support/boost/boost.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-support/boost/boost.inc 
b/meta/recipes-support/boost/boost.inc
index 0461ec6..c53edf7 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -195,6 +195,9 @@ do_install() {
                fi
        done

+       if [ -e ${D}${libdir}/libboost_python3.so ]; then
+               ln -s libboost_python3.so ${D}${libdir}/libboost_python.so
+       fi
 }

 BBCLASSEXTEND = "native nativesdk"
--
2.7.4

--
___
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 v2] gstreamer: enable ptest support

2018-03-14 Thread Burton, Ross 
On 28 February 2018 at 02:51, Anuj Mittal  wrote:

> +diff --git a/Makefile.am b/Makefile.am
> +index de057c4..42e90fe 100644
> +--- a/Makefile.am
>  b/Makefile.am
> +@@ -96,6 +96,9 @@ check-torture:
> +
> + build-checks:
> +   $(MAKE) -C tests/check build-checks
> ++
> ++install-ptest:
> ++  $(MAKE) -C tests/check DESTDIR=$(DESTDIR) $@
> + else
> + check-valgrind:
>
+   echo "'check' library not installed, skipping"
>

I'd say not to bother patching the top-level and instead call the right
makefile from do_install_ptest.

++install-ptest: $(TESTS)
> ++  @$(INSTALL) -d $(DESTDIR)
> ++  @for dir in gst libs tools pipelines elements generic; do \
> ++  if [ -x $$dir/.libs ]; then \
> ++  $(INSTALL) -d $(DESTDIR)/$$dir; \
> ++  $(INSTALL_PROGRAM) $$dir/.libs/*
> $(DESTDIR)/$$dir/; \
> ++  fi \
> ++  done
>

Can this do string functions on TESTS instead of hard-coding the list of
directories?

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

Re: [OE-core] [PATCH 2/2] perf: enable support for libaudit

2018-03-14 Thread Burton, Ross 
On 2 March 2018 at 04:44, Anuj Mittal  wrote:

>  # gui support was added with kernel 3.6.35
>  # since 3.10 libnewt was replaced by slang
>  # to cover a wide range of kernel we add both dependencies
> @@ -22,6 +22,10 @@ PACKAGECONFIG[libnuma] = ",NO_LIBNUMA=1"
>  PACKAGECONFIG[systemtap] = ",NO_SDT=1,systemtap"
>  PACKAGECONFIG[jvmti] = ",NO_JVMTI=1"
>
> +# libaudit support needs python to be present
> +PACKAGECONFIG[audit] = ",NO_LIBAUDIT=1,audit python"
>

All you need in this patch is:

+# audit needs scripting to be enabled.
+PACKAGECONFIG[audit] = ",NO_LIBAUDIT=1,audit"

The convoluted logic will only get more complicated over time, when a
comment saying "if you want audit to work, turn on scripting" is sufficient.

+PACKAGECONFIG_CONFARGS += "${@bb.utils.contains_any('PACKAGECONFIG',
> 'scripting audit', '', 'NO_LIBPYTHON=1', d)}


PACKAGECONFG_CONFAGS isn't for assigning in a recipe.

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

[OE-core] ✗ patchtest: failure for kernel: (mini) consolidated pull request

2018-03-14 Thread Patchwork 
== Series Details ==

Series: kernel: (mini) consolidated pull request
Revision: 1
URL   : https://patchwork.openembedded.org/series/11383/
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:



* Patch[1/3] linux-yocto/4.14/4.15: revert 
"features/systemtap/systemtap.cfg: enable CONFIG_KERNEL_DEBUG"
 Issue Commit shortlog is too long [test_shortlog_length] 
  Suggested fixEdit shortlog so that it is 90 characters or less (currently 
92 characters)



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

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

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

Re: [OE-core] [rocko][PATCH 1/8] Revert "waf.bbclass: explicitly pass bindir and libdir if supported"

2018-03-14 Thread Martin Jansa 
ping, this was in rocko-next for a while and then it disappeared.

On Sun, Mar 11, 2018 at 1:43 AM, Martin Jansa 
wrote:

> * this doesn't work correctly as discussed in:
>   http://lists.openembedded.org/pipermail/openembedded-
> commits/2018-January/218460.html
> * some of the issues were fixed in master since then
>   but not all, so revert it until it's completely resolved
>
> This reverts commit eac21f981337bfaddb2d67161a1ff049158041ce.
>
> Signed-off-by: Martin Jansa 
> ---
>  meta/classes/waf.bbclass | 17 +
>  1 file changed, 1 insertion(+), 16 deletions(-)
>
> diff --git a/meta/classes/waf.bbclass b/meta/classes/waf.bbclass
> index acbda278a2..c4698e910a 100644
> --- a/meta/classes/waf.bbclass
> +++ b/meta/classes/waf.bbclass
> @@ -25,23 +25,8 @@ def get_waf_parallel_make(d):
>
>  return ""
>
> -python waf_preconfigure() {
> -from distutils.version import StrictVersion
> -srcsubdir = d.getVar('S')
> -wafbin = os.path.join(srcsubdir, 'waf')
> -status, result = oe.utils.getstatusoutput(wafbin + " --version")
> -if status != 0:
> -bb.warn("Unable to execute waf --version, exit code %d. Assuming
> waf version without bindir/libdir support." % status)
> -return
> -version = result.split()[1]
> -if StrictVersion(version) >= StrictVersion("1.8.7"):
> -d.setVar("WAF_EXTRA_CONF", "--bindir=${bindir}
> --libdir=${libdir}")
> -}
> -
> -do_configure[prefuncs] += "waf_preconfigure"
> -
>  waf_do_configure() {
> -   ${S}/waf configure --prefix=${prefix} ${WAF_EXTRA_CONF}
> ${EXTRA_OECONF}
> +   ${S}/waf configure --prefix=${prefix} ${EXTRA_OECONF}
>  }
>
>  waf_do_compile()  {
> --
> 2.15.1
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/3] alsa-lib: Add an RPROVIDES for alsa-lib

2018-03-14 Thread Jason Wessel 


# dnf install python-pyalsaaudio
Last metadata expiration check: 0:00:44 ago on Wed Mar 14 11:15:23 2018.
Error:
 Problem: conflicting requests
  - nothing provides alsa-lib needed by python-pyalsaaudio-0.8.4-r0.1.core2_64

---
The python-pyalsaaudio recipe in question did the following:

DEPENDS += "alsa-lib"

RDEPENDS_${PN} += "\
    alsa-lib \
"

Obviously since nothing provides that, it isn't going to work. It is probably 
better in this case to change the python recipe to RDEPENDS on libasound which 
is what the alsa-lib recipe generates.  I can understand how the author of the 
python recipe might have been confused, but it begs the question of how it 
worked in the first place.  :-)

I can reach out to the owner of the layer that provided the recipe and you can 
drop this patch.

Jason.

On 03/14/2018 09:51 AM, Burton, Ross wrote:

This sounds very odd.  Can you give an example of this happening?

Ross

On 13 March 2018 at 03:08, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:

There are a number of other recipes outside oe-core that depend on
alsa-lib and the rpm4 dependencies resolve sometimes to include
alsa-lib and the packages in the other layers fail to install because
the dependency cannot be resolved, despite the fact that libasound is
installed.

The simple is to add an RPROVIDES for alsa-lib to libasound which
provides all the shared objects for alsa.

Signed-off-by: Jason Wessel mailto:jason.wes...@windriver.com>>
---
 meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb  
| 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb 
 b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb 

index c5bf107..f7f01e8 100644
--- a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb 

+++ b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb 

@@ -25,6 +25,7 @@ FILES_alsa-server = "${bindir}/*"
 FILES_alsa-conf = "${datadir}/alsa/"

 RDEPENDS_libasound = "alsa-conf"
+RPROVIDES_libasound = "alsa-lib"

 # alsa-lib gets automatically added to alsa-lib-dev dependencies, but the
 # alsa-lib package doesn't exist. libasound is the real library package.
--
2.7.4

--
___
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] Recipe for Linux page-types tool

2018-03-14 Thread Martin Vuille 

I have a recipe for building the page-types Linux kernel VM tool.
Is there any interest in this?
If so, to what project/layer should I send it?

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

Re: [OE-core] [PATCH 7/9] linux-yocto: aufs and systemtap

2018-03-14 Thread Bruce Ashfield 

On 2018-03-14 8:50 AM, Burton, Ross wrote:
On 14 March 2018 at 12:46, Bruce Ashfield > wrote:


I'll revert this for now (or see if I can quickly move it to a debug
kernel build), and yes, there is a better way to do this. I'm just not
sure I can get it done in time for the release.


Thanks.  I'm desperately trying to be able to tell RP we can fire the M3 
build so I'm +1 on reverting now, fixing later.


revert sent. I put all the details in the commit log about how
to build systemtap with the relevant options enabled. So there's
still a way to build with the options that were the intent of that
change, and with this revert the standard kernel should go back
to normal.

Bruce



Ross


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

[OE-core] [PATCH 0/3] kernel: (mini) consolidated pull request

2018-03-14 Thread Bruce Ashfield 
Hi all,

This series is really about fixing the footprint and packaging issues
that were reported after a systemtap configuration change. I've reverted
the addition of DEBUG_KERNEL to the standard kernel's config and things
should go back to normal.

I also packaged a maintainers update (reported by Cal) and a couple of
minor bug fixes in the series.

Cheers,

Bruce

The following changes since commit 5350ee317740751f2417c1794dd39d3880347dbf:

  yocto-uninative: Upgrade to 1.8 version with glibc 2.27 (2018-03-11 06:27:02 
-0700)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (3):
  linux-yocto/4.14/4.15: revert "features/systemtap/systemtap.cfg:
enable CONFIG_KERNEL_DEBUG"
  maintainers: add maintainer for make-mod-scripts
  linux-yocto/4.12: backport bugfixes for x86

 meta/conf/distro/include/maintainers.inc   |  1 +
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.12.bb  | 16 
 meta/recipes-kernel/linux/linux-yocto_4.14.bb  |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.15.bb  |  2 +-
 10 files changed, 17 insertions(+), 16 deletions(-)

-- 
2.5.0

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

[OE-core] [PATCH 1/3] linux-yocto/4.14/4.15: revert "features/systemtap/systemtap.cfg: enable CONFIG_KERNEL_DEBUG"

2018-03-14 Thread Bruce Ashfield 
The following commit:

   Author: California Sullivan 
   Date:   Wed Feb 17 16:47:10 2016 -0800

   ktypes: add developer ktype

   The developer ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL,
   opening up more kernel options and setting some defaults.

  Signed-off-by: California Sullivan 
  Signed-off-by: Bruce Ashfield 

Was created to address the kernel footprint related issues that are related
to many of the kernel debug options.

When this commit was merged, it re-enabled CONFIG_DEBUG_KERNEL for the
standard kernel, since it includes the systemtap fragment. The correct thing
to do is to move systemtap properly into the developer kernel type.

For now, you can build the developer kernel type, or add the developer kernel
configuration fragment via a bbappend, and you'll have a functional systemtap.

[YOCTO #12603]

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.14.bb  | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.15.bb  | 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb
index fd003e4d2bec..8a6371625ee0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "4832801a14130645d2251a368cba79d937a775ab"
-SRCREV_meta ?= "54b3e9b768651ca15bf65ae1c72dfe6d957285f0"
+SRCREV_meta ?= "5f6c3e32365bffb1993c0c62abf2c5bb8916a57f"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.14;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb
index 38589927037d..9f03c98cffad 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "3247d5a26cab529bd4acc137c119bcdf71c3d5ae"
-SRCREV_meta ?= "40cef533a17de9d7a1de9b6e3578ac9125486a4a"
+SRCREV_meta ?= "65e0a9654f69241d0e6b18162289dabec877039e"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.15;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb
index 1ccbf6283e43..494d80aa4886 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "09828ddd8d8c91b2d68afdcd8eb99a48e0253582"
-SRCREV_meta ?= "54b3e9b768651ca15bf65ae1c72dfe6d957285f0"
+SRCREV_meta ?= "5f6c3e32365bffb1993c0c62abf2c5bb8916a57f"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb
index 0c0abf38f286..6ec6371b7420 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= 
"9c2e6c0fc71526c45fc7ddf3ec91e2e2f27e3da0"
 SRCREV_machine_qemux86-64 ?= "9c2e6c0fc71526c45fc7ddf3ec91e2e2f27e3da0"
 SRCREV_machine_qemumips64 ?= "f9a3a72209bde080e4ecb4fbe7a0f99954643131"
 SRCREV_machine ?= "3247d5a26cab529bd4acc137c119bcdf71c3d5ae"
-SRCREV_meta ?= "40cef533a17de9d7a1de9b6e3578ac9125486a4a"
+SRCREV_meta ?= "65e0a9654f69241d0e6b18162289dabec877039e"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH}; \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.15;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.14.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.14.bb
index a714e39751ae..ba5e35625eba 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.14.bb
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= 
"edc90f45a716ffe8e16cebaaf3b5db070af0280a"
 SRCREV_machine_qemux86-64 ?= "edc90f45a716ffe8e16cebaaf3b5db070af0280a"
 SRCREV_machine_qemumips64 ?= "6d7fbdbb7e466be645c34eed7bb2b532a9431a85"
 SRCREV_machine ?= "edc90f45a716ffe8e16cebaaf3b5db070af0280a"
-SRCREV_meta ?= "54b3e9b768651ca15bf65ae1c72dfe6d957285f0"
+SRCREV_meta ?= "5f6c3e32365bffb1993c0c62abf2c5bb8916a57f"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH}; \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.14;destsuff

[OE-core] [PATCH 2/3] maintainers: add maintainer for make-mod-scripts

2018-03-14 Thread Bruce Ashfield 
I introduced the recipe, so I get to fix any bugs!

Signed-off-by: Bruce Ashfield 
---
 meta/conf/distro/include/maintainers.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index d4e833f12768..38f7330bf418 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -483,6 +483,7 @@ RECIPE_MAINTAINER_pn-m4-native = "Robert Yang 
"
 RECIPE_MAINTAINER_pn-make = "Robert Yang "
 RECIPE_MAINTAINER_pn-makedepend = "Robert Yang "
 RECIPE_MAINTAINER_pn-makedevs = "Chen Qi "
+RECIPE_MAINTAINER_pn-make-mod-scripts "Bruce Ashfield 
"
 RECIPE_MAINTAINER_pn-man-db = "Hongxu Jia "
 RECIPE_MAINTAINER_pn-man-pages = "Hongxu Jia "
 RECIPE_MAINTAINER_pn-matchbox-config-gtk = "Maxin B. John 
"
-- 
2.5.0

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

[OE-core] [PATCH 3/3] linux-yocto/4.12: backport bugfixes for x86

2018-03-14 Thread Bruce Ashfield 
Integrating the following commits:

  60b649971940 x86/hibernate/64: Mask off CR3's PCID bits in the saved CR3
  cec3c008ec8f drm/i915/cfl: Coffee Lake works on Kaby Lake PCH.
  073873cb152c brd: remove unused brd_mutex
  912c53b1b346 audit: fix memleak in auditd_send_unicast_skb.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.12.bb  | 16 
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
index a100f7d4a9f9..ad0981296f5a 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -11,7 +11,7 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "b103a20d4b507ede60adc8478dade56a4bdaffad"
+SRCREV_machine ?= "da775aa9aab41e8a2b4e9b44ffe268446c51759f"
 SRCREV_meta ?= "4f825eeb783a279216ee45ed3b9a63dd6837f7d7"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine 
\
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
index c306db292b2e..0bbd8e28db86 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -9,7 +9,7 @@ LINUX_VERSION ?= "4.12.20"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "cec3c008ec8f7acdb01b95fceb1ef7dff35d1877"
+SRCREV_machine ?= "60b649971940737dc7e3a7f247c62ffbd7c82e4c"
 SRCREV_meta ?= "4f825eeb783a279216ee45ed3b9a63dd6837f7d7"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
index 78a291acf0a6..fabf0f554bbf 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -11,14 +11,14 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "4fb13c0d7254fe9753bebdfcfe47fd1ba4487386"
-SRCREV_machine_qemuarm64 ?= "cec3c008ec8f7acdb01b95fceb1ef7dff35d1877"
-SRCREV_machine_qemumips ?= "9eb1f72874eeadb1f17e59faaca331971d522e12"
-SRCREV_machine_qemuppc ?= "cec3c008ec8f7acdb01b95fceb1ef7dff35d1877"
-SRCREV_machine_qemux86 ?= "cec3c008ec8f7acdb01b95fceb1ef7dff35d1877"
-SRCREV_machine_qemux86-64 ?= "cec3c008ec8f7acdb01b95fceb1ef7dff35d1877"
-SRCREV_machine_qemumips64 ?= "710cc1cb7ba1384b9b0f43fc811a18a7c5a4e03f"
-SRCREV_machine ?= "cec3c008ec8f7acdb01b95fceb1ef7dff35d1877"
+SRCREV_machine_qemuarm ?= "42cf4d6a1bc84b90681cb82ad95c129387d76b4b"
+SRCREV_machine_qemuarm64 ?= "60b649971940737dc7e3a7f247c62ffbd7c82e4c"
+SRCREV_machine_qemumips ?= "571315a5526b9e22262cf99bae7c0dd6e5bd204c"
+SRCREV_machine_qemuppc ?= "60b649971940737dc7e3a7f247c62ffbd7c82e4c"
+SRCREV_machine_qemux86 ?= "60b649971940737dc7e3a7f247c62ffbd7c82e4c"
+SRCREV_machine_qemux86-64 ?= "60b649971940737dc7e3a7f247c62ffbd7c82e4c"
+SRCREV_machine_qemumips64 ?= "e7889ba18f060368d4ab35e70b076728d73ba622"
+SRCREV_machine ?= "60b649971940737dc7e3a7f247c62ffbd7c82e4c"
 SRCREV_meta ?= "4f825eeb783a279216ee45ed3b9a63dd6837f7d7"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH};
 \
-- 
2.5.0

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

Re: [OE-core] [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

2018-03-14 Thread Jason Wessel 

Perhaps a bug in the cmake detect which is part of boost, because I am not 
using python2 for caffe.

I used the path of least resistance because as far as I could tell boost only 
let you build one or the other and in my case it was the python3 boost api. In 
the end caffe was working and all the python3 tests with the Movidius SDK pass 
(which use python3).

Jason.

On 03/14/2018 09:50 AM, Burton, Ross wrote:

I thought that boost_python was the py2 binary, and boost_python3 was the py3 
one?  Is this not a bug in caffe?

On 13 March 2018 at 03:08, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:

When using an image built with the Yocto Project which has a compiler
and all the required libraries, projects such as caffe for the
Movidius SDK which use python3 and boost fail to build because they
look for libboost_python.so.  The error that cmake returns doesn't
even point to the fact that this is why the configuration fails.

Example showing the problem with the missing symlink:

  git clone https://github.com/weiliu89/caffe.git 

  cd caffe
  mkdir build
  cd build
  cmake -DBLAS=Open ..

-- Configuring done
CMake Error at CMakeLists.txt:85 (add_dependencies):
  The dependency target "pycaffe" of target "pytest" does not exist.


Conditionally creating the link when building python3 support into
boost is all that is needed.

Signed-off-by: Jason Wessel mailto:jason.wes...@windriver.com>>
---
 meta/recipes-support/boost/boost.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-support/boost/boost.inc 
b/meta/recipes-support/boost/boost.inc
index 0461ec6..c53edf7 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -195,6 +195,9 @@ do_install() {
                fi
        done

+       if [ -e ${D}${libdir}/libboost_python3.so ]; then
+               ln -s libboost_python3.so ${D}${libdir}/libboost_python.so
+       fi
 }

 BBCLASSEXTEND = "native nativesdk"
--
2.7.4

--
___
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 1/3] alsa-lib: Add an RPROVIDES for alsa-lib

2018-03-14 Thread Burton, Ross 
This sounds very odd.  Can you give an example of this happening?

Ross

On 13 March 2018 at 03:08, Jason Wessel  wrote:

> There are a number of other recipes outside oe-core that depend on
> alsa-lib and the rpm4 dependencies resolve sometimes to include
> alsa-lib and the packages in the other layers fail to install because
> the dependency cannot be resolved, despite the fact that libasound is
> installed.
>
> The simple is to add an RPROVIDES for alsa-lib to libasound which
> provides all the shared objects for alsa.
>
> Signed-off-by: Jason Wessel 
> ---
>  meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> index c5bf107..f7f01e8 100644
> --- a/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> +++ b/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
> @@ -25,6 +25,7 @@ FILES_alsa-server = "${bindir}/*"
>  FILES_alsa-conf = "${datadir}/alsa/"
>
>  RDEPENDS_libasound = "alsa-conf"
> +RPROVIDES_libasound = "alsa-lib"
>
>  # alsa-lib gets automatically added to alsa-lib-dev dependencies, but the
>  # alsa-lib package doesn't exist. libasound is the real library package.
> --
> 2.7.4
>
> --
> ___
> 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 2/3] boost: Fix link problems with caffe and Movidius SDK

2018-03-14 Thread Burton, Ross 
I thought that boost_python was the py2 binary, and boost_python3 was the
py3 one?  Is this not a bug in caffe?

On 13 March 2018 at 03:08, Jason Wessel  wrote:

> When using an image built with the Yocto Project which has a compiler
> and all the required libraries, projects such as caffe for the
> Movidius SDK which use python3 and boost fail to build because they
> look for libboost_python.so.  The error that cmake returns doesn't
> even point to the fact that this is why the configuration fails.
>
> Example showing the problem with the missing symlink:
> 
>   git clone https://github.com/weiliu89/caffe.git
>   cd caffe
>   mkdir build
>   cd build
>   cmake -DBLAS=Open ..
>
> -- Configuring done
> CMake Error at CMakeLists.txt:85 (add_dependencies):
>   The dependency target "pycaffe" of target "pytest" does not exist.
> 
>
> Conditionally creating the link when building python3 support into
> boost is all that is needed.
>
> Signed-off-by: Jason Wessel 
> ---
>  meta/recipes-support/boost/boost.inc | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-support/boost/boost.inc
> b/meta/recipes-support/boost/boost.inc
> index 0461ec6..c53edf7 100644
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -195,6 +195,9 @@ do_install() {
> fi
> done
>
> +   if [ -e ${D}${libdir}/libboost_python3.so ]; then
> +   ln -s libboost_python3.so ${D}${libdir}/libboost_python.so
> +   fi
>  }
>
>  BBCLASSEXTEND = "native nativesdk"
> --
> 2.7.4
>
> --
> ___
> 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 7/9] linux-yocto: aufs and systemtap

2018-03-14 Thread Burton, Ross 
On 14 March 2018 at 12:46, Bruce Ashfield 
wrote:

> I'll revert this for now (or see if I can quickly move it to a debug
> kernel build), and yes, there is a better way to do this. I'm just not
> sure I can get it done in time for the release.
>

Thanks.  I'm desperately trying to be able to tell RP we can fire the M3
build so I'm +1 on reverting now, fixing later.

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

Re: [OE-core] [PATCH 7/9] linux-yocto: aufs and systemtap

2018-03-14 Thread Bruce Ashfield 

On 2018-03-14 8:41 AM, Burton, Ross wrote:
On 6 March 2018 at 18:11, Bruce Ashfield > wrote:


Integrating a configuration change for systemtap:

   features/systemtap/systemtap.cfg: enable CONFIG_KERNEL_DEBUG


I noticed that all the performance machines had a big spike in kernel 
build time and build directory size, and annoyingly spent too long 
bisecting builds before noticing this in the commit message for the 
offending commit.  If I re-read the logs I might have spotted this 
sooner. :)


Agreed. I should have realized this as well, we went through a process
about a year ago of moving all of the debug configs with the split into
a production/debug set of kernel configurations.



$ buildstats-diff 20180314122002-3a8cce8b5c2 20180314122610-a7c9bc7020a/
Ignoring tasks less than 00:03.0 (3.0s)
Ignoring differences less than 00:01.0 (1.0s)

   PKG            TASK                      ABSDIFF   RELDIFF  CPUTIME1 
-> CPUTIME2
   linux-yocto    do_package                  20.2s   +153.0%     13.2s 
-> 33.3s
   linux-yocto    do_deploy                   29.9s  +1502.8%      2.0s 
-> 31.9s
   linux-yocto    do_package_write_ipk       125.5s   +310.2%     40.5s 
-> 166.0s
   linux-yocto    do_compile_kernelmodules   142.6s    +17.8%    800.3s 
-> 942.9s
   linux-yocto    do_package_write_rpm       156.0s   +563.6%     27.7s 
-> 183.7s
   linux-yocto    do_compile                 174.8s    +18.7%    934.3s 
-> 1109.1s


Cumulative cputime:
   649.5s    +35.0%    30:56.0 (1856.0s) -> 41:45.5 (2505.5s)

$ buildhistory-diff | grep SIZE
packages/qemux86-poky-linux/linux-yocto/kernel-vmlinux: PKGSIZE changed 
from 19587044 to 300944172 (+1436%)


Is this really what we want out of the box?  Can the kernel have the 
debugging bits stripped out into a separate package so even if we have 
the build time hit, we don't have the kernel size change?


I'll revert this for now (or see if I can quickly move it to a debug
kernel build), and yes, there is a better way to do this. I'm just not
sure I can get it done in time for the release.

Bruce



Ross


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

Re: [OE-core] [PATCH 7/9] linux-yocto: aufs and systemtap

2018-03-14 Thread Burton, Ross 
On 6 March 2018 at 18:11, Bruce Ashfield 
wrote:

> Integrating a configuration change for systemtap:
>
>   features/systemtap/systemtap.cfg: enable CONFIG_KERNEL_DEBUG
>

I noticed that all the performance machines had a big spike in kernel build
time and build directory size, and annoyingly spent too long bisecting
builds before noticing this in the commit message for the offending
commit.  If I re-read the logs I might have spotted this sooner. :)

$ buildstats-diff 20180314122002-3a8cce8b5c2 20180314122610-a7c9bc7020a/
Ignoring tasks less than 00:03.0 (3.0s)
Ignoring differences less than 00:01.0 (1.0s)

  PKGTASK  ABSDIFF   RELDIFF  CPUTIME1 ->
CPUTIME2
  linux-yoctodo_package  20.2s   +153.0% 13.2s ->
33.3s
  linux-yoctodo_deploy   29.9s  +1502.8%  2.0s ->
31.9s
  linux-yoctodo_package_write_ipk   125.5s   +310.2% 40.5s ->
166.0s
  linux-yoctodo_compile_kernelmodules   142.6s+17.8%800.3s ->
942.9s
  linux-yoctodo_package_write_rpm   156.0s   +563.6% 27.7s ->
183.7s
  linux-yoctodo_compile 174.8s+18.7%934.3s ->
1109.1s

Cumulative cputime:
  649.5s+35.0%30:56.0 (1856.0s) -> 41:45.5 (2505.5s)

$ buildhistory-diff | grep SIZE
packages/qemux86-poky-linux/linux-yocto/kernel-vmlinux: PKGSIZE changed
from 19587044 to 300944172 (+1436%)

Is this really what we want out of the box?  Can the kernel have the
debugging bits stripped out into a separate package so even if we have the
build time hit, we don't have the kernel size change?

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

[OE-core] [PATCH 2/2] gtk-doc: improve calling of gtkdocize

2018-03-14 Thread Ross Burton 
gtkdocize is only needed if the recipe is using autotools, so instead of hiding
all errors from it, only run it if we're also inheriting autotools.

Also instead of cd'ing into ${S}, pass --srcdir.

Signed-off-by: Ross Burton 
---
 meta/classes/gtk-doc.bbclass | 11 +--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/meta/classes/gtk-doc.bbclass b/meta/classes/gtk-doc.bbclass
index 3f731cb93bf..cfeb49a1d00 100644
--- a/meta/classes/gtk-doc.bbclass
+++ b/meta/classes/gtk-doc.bbclass
@@ -31,8 +31,15 @@ export STAGING_DIR_HOST
 inherit python3native pkgconfig qemu
 DEPENDS_append = "${@' qemu-native' if d.getVar('GTKDOC_ENABLED') == 'True' 
else ''}"
 
-do_configure_prepend () {
-   ( cd ${S}; gtkdocize --docdir ${GTKDOC_DOCDIR} || true )
+# Run gtkdocize if the recipe is using autotools
+run_gtkdocize () {
+   bbnote Running gtkdocize...
+   gtkdocize --srcdir ${S} --docdir ${GTKDOC_DOCDIR}
+}
+
+python () {
+if bb.data.inherits_class("autotools", d):
+d.appendVarFlag('do_configure', 'prefuncs', ' run_gtkdocize')
 }
 
 do_compile_prepend_class-target () {
-- 
2.11.0

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

[OE-core] [PATCH 1/2] gtk-doc: always inherit python3native

2018-03-14 Thread Ross Burton 
My attempt at only inheriting python3native if it was needed was broken and
didn't work, so back it out and always inherit.

Signed-off-by: Ross Burton 
---
 meta/classes/gtk-doc.bbclass | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/meta/classes/gtk-doc.bbclass b/meta/classes/gtk-doc.bbclass
index b8db4280bcd..3f731cb93bf 100644
--- a/meta/classes/gtk-doc.bbclass
+++ b/meta/classes/gtk-doc.bbclass
@@ -28,10 +28,8 @@ GTKDOC_DOCDIR ?= "${S}"
 
 export STAGING_DIR_HOST
 
-inherit ${@oe.utils.ifelse(d.getVar('GTKDOC_ENABLED') == 'True', 
'python3native', '')}
-
-inherit pkgconfig qemu
-DEPENDS_append = "${@oe.utils.ifelse(d.getVar('GTKDOC_ENABLED') == 'True', ' 
qemu-native', '')}"
+inherit python3native pkgconfig qemu
+DEPENDS_append = "${@' qemu-native' if d.getVar('GTKDOC_ENABLED') == 'True' 
else ''}"
 
 do_configure_prepend () {
( cd ${S}; gtkdocize --docdir ${GTKDOC_DOCDIR} || true )
-- 
2.11.0

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

[OE-core] ✗ patchtest: failure for insane.bbclass: Fix typos in 32bit risc-v machine type

2018-03-14 Thread Patchwork 
== Series Details ==

Series: insane.bbclass: Fix typos in 32bit risc-v machine type
Revision: 1
URL   : https://patchwork.openembedded.org/series/11380/
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 073d8d0010)



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

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

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

[OE-core] [PATCH] insane.bbclass: Fix typos in 32bit risc-v machine type

2018-03-14 Thread Khem Raj 
Signed-off-by: Khem Raj 
---
 meta/classes/insane.bbclass | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index 7791a867f7..fa15460842 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -71,7 +71,7 @@ def package_qa_get_machine_dict(d):
 "microblaze":  (189,   0,0,  False,
 32),
 "microblazeeb":(189,   0,0,  False,
 32),
 "microblazeel":(189,   0,0,  True, 
 32),
-"riscv":  (243,0,0,  True, 
 32),
+"riscv32":(243,0,0,  True, 
 32),
 "riscv64":(243,0,0,  True, 
 64),
   },
 "linux" : { 
@@ -99,7 +99,7 @@ def package_qa_get_machine_dict(d):
 "mipsisa64r6":   ( 8,  0,0,  False,
 64),
 "mipsisa64r6el": ( 8,  0,0,  True, 
 64),
 "nios2":  (113,0,0,  True, 
 32),
-"riscv":  (243,0,0,  True, 
 32),
+"riscv32":(243,0,0,  True, 
 32),
 "riscv64":(243,0,0,  True, 
 64),
 "s390":   (22, 0,0,  False,
 32),
 "sh4":(42, 0,0,  True, 
 32),
@@ -126,7 +126,7 @@ def package_qa_get_machine_dict(d):
 "microblaze":  (189, 0,0,  False,  
   32),
 "microblazeeb":(189, 0,0,  False,  
   32),
 "microblazeel":(189, 0,0,  True,   
   32),
-"riscv":  (243,  0,0,  True,   
   32),
+"riscv32":(243,  0,0,  True,   
   32),
 "riscv64":(243,  0,0,  True,   
   64),
 "sh4":(  42, 0,0,  True,   
   32),
   },
-- 
2.16.2

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