[PATCH 01/11] icu: update to 59.1

[PATCH 01/11] icu: update to 59.1

[Alexander Kanavin]

License checksum change due to copyright year update.

Latest icu will not compile with anything less than C++11, so
drop the enforcement of an earlier C++ version. This should be okay,
as there is now a fix in place for the problem of mixing native gcc 4/5
compiled code:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c21cec84886d9c70396e9be0ceb9a8ef300b54be

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/conf/distro/include/uninative-flags.inc          | 4 ----
 meta/recipes-support/icu/{icu_58.2.bb => icu_59.1.bb} | 6 +++---
 2 files changed, 3 insertions(+), 7 deletions(-)
 rename meta/recipes-support/icu/{icu_58.2.bb => icu_59.1.bb} (78%)

diff --git a/meta/conf/distro/include/uninative-flags.inc b/meta/conf/distro/include/uninative-flags.inc
index f5b15471a4b..febf2a53e52 100644
--- a/meta/conf/distro/include/uninative-flags.inc
+++ b/meta/conf/distro/include/uninative-flags.inc
@@ -1,7 +1,3 @@
-# icu configure defaults to CXX11 if no -std= option is passed in CXXFLAGS
-# therefore pass one
-BUILD_CXXFLAGS_append_pn-icu-native = " -std=c++98"
-
 # Some distros (ubuntu 16.10, debian-testing) default to gcc configured with
 # --enable-default-pie (see gcc -v). This breaks e.g. prelink-native on a pie
 # default system if binutils-native was built on a system which is not pie default
diff --git a/meta/recipes-support/icu/icu_58.2.bb b/meta/recipes-support/icu/icu_59.1.bb
similarity index 78%
rename from meta/recipes-support/icu/icu_58.2.bb
rename to meta/recipes-support/icu/icu_59.1.bb
index 47684a6c8b0..31f017b3701 100644
--- a/meta/recipes-support/icu/icu_58.2.bb
+++ b/meta/recipes-support/icu/icu_59.1.bb
@@ -1,6 +1,6 @@
 require icu.inc
 
-LIC_FILES_CHKSUM = "file://../LICENSE;md5=1b3b75c1777cd49ad5c6a24cd338cfc9"
+LIC_FILES_CHKSUM = "file://../LICENSE;md5=fe9e1f2c500466d8f18df2cd068e4b74"
 
 def icu_download_version(d):
     pvsplit = d.getVar('PV').split('.')
@@ -22,8 +22,8 @@ SRC_URI = "${BASE_SRC_URI} \
 SRC_URI_append_class-target = "\
            file://0001-Disable-LDFLAGSICUDT-for-Linux.patch \
           "
-SRC_URI[md5sum] = "fac212b32b7ec7ab007a12dff1f3aea1"
-SRC_URI[sha256sum] = "2b0a4410153a9b20de0e20c7d8b66049a72aef244b53683d0d7521371683da0c"
+SRC_URI[md5sum] = "54923fa9fab5b2b83f235fb72523de37"
+SRC_URI[sha256sum] = "7132fdaf9379429d004005217f10e00b7d2319d0fea22bdfddef8991c45b75fe"
 
 UPSTREAM_CHECK_REGEX = "(?P<pver>\d+(\.\d+)+)/"
 UPSTREAM_CHECK_URI = "http://download.icu-project.org/files/icu4c/"
-- 
2.13.2

[PATCH 02/11] btrfs-tools: upgrade to 4.11.1

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 .../btrfs-tools/{btrfs-tools_4.11.bb => btrfs-tools_4.11.1.bb}          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_4.11.bb => btrfs-tools_4.11.1.bb} (95%)

diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.1.bb
similarity index 95%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.1.bb
index 6ccb44a0db8..a7b42e9546b 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.1.bb
@@ -14,7 +14,7 @@ DEPENDS = "util-linux attr e2fsprogs lzo acl"
 DEPENDS_append_class-target = " udev"
 RDEPENDS_${PN} = "libgcc"
 
-SRCREV = "981f2d8fdc37741098bb977921c6e3f1ea88365b"
+SRCREV = "88221fc081a7a0979a012f243b66cf097382cc8f"
 SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git"
 
 inherit autotools-brokensep pkgconfig manpages
-- 
2.13.2

[PATCH 03/11] bash-completion: upgrade to 2.7

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 .../{bash-completion_2.5.bb => bash-completion_2.7.bb}                | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/bash-completion/{bash-completion_2.5.bb => bash-completion_2.7.bb} (88%)

diff --git a/meta/recipes-support/bash-completion/bash-completion_2.5.bb b/meta/recipes-support/bash-completion/bash-completion_2.7.bb
similarity index 88%
rename from meta/recipes-support/bash-completion/bash-completion_2.5.bb
rename to meta/recipes-support/bash-completion/bash-completion_2.7.bb
index dd22857a70c..7877e51d11b 100644
--- a/meta/recipes-support/bash-completion/bash-completion_2.5.bb
+++ b/meta/recipes-support/bash-completion/bash-completion_2.7.bb
@@ -9,8 +9,8 @@ SECTION = "console/utils"
 
 SRC_URI = "https://github.com/scop/bash-completion/releases/download/${PV}/${BPN}-${PV}.tar.xz"
 
-SRC_URI[md5sum] = "15300010bd4034de12c3fc4f171692e3"
-SRC_URI[sha256sum] = "b0b9540c65532825eca030f1241731383f89b2b65e80f3492c5dd2f0438c95cf"
+SRC_URI[md5sum] = "28117492bdc9408438e6041683a423ce"
+SRC_URI[sha256sum] = "41ba892d3f427d4a686de32673f35401bc947a7801f684127120cdb13641441e"
 UPSTREAM_CHECK_REGEX = "bash-completion-(?P<pver>(?!2008).+)\.tar"
 UPSTREAM_CHECK_URI = "https://github.com/scop/bash-completion/releases"
 
-- 
2.13.2

[PATCH 04/11] epiphany: upgrade to 3.24.3

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 .../recipes-gnome/epiphany/{epiphany_3.24.2.bb => epiphany_3.24.3.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-gnome/epiphany/{epiphany_3.24.2.bb => epiphany_3.24.3.bb} (84%)

diff --git a/meta/recipes-gnome/epiphany/epiphany_3.24.2.bb b/meta/recipes-gnome/epiphany/epiphany_3.24.3.bb
similarity index 84%
rename from meta/recipes-gnome/epiphany/epiphany_3.24.2.bb
rename to meta/recipes-gnome/epiphany/epiphany_3.24.3.bb
index dafad8a7938..c507d23ae93 100644
--- a/meta/recipes-gnome/epiphany/epiphany_3.24.2.bb
+++ b/meta/recipes-gnome/epiphany/epiphany_3.24.3.bb
@@ -12,8 +12,8 @@ REQUIRED_DISTRO_FEATURES = "x11"
 SRC_URI += "file://0001-yelp.m4-drop-the-check-for-itstool.patch \
             file://0001-bookmarks-Check-for-return-value-of-fread.patch \
            "
-SRC_URI[archive.md5sum] = "e035dc6f64f0c1909de823e03f16b2f3"
-SRC_URI[archive.sha256sum] = "5abc0d0c60591df5236ac9b8979dc9f7d9acbb8ad0902b4772d2b7beea81c58d"
+SRC_URI[archive.md5sum] = "c0221aec6a08935e6854eaa9de9451ef"
+SRC_URI[archive.sha256sum] = "fef51676310d9f37e18c9b2d778254232eb17cccd988c2d1ecf42c7b2963a154"
 
 EXTRA_OECONF += " --with-distributor-name=${DISTRO} --enable-debug=no"
 
-- 
2.13.2

[PATCH 05/11] gperf: upgrade to 3.1

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-extended/gperf/gperf_3.0.4.bb | 5 -----
 meta/recipes-extended/gperf/gperf_3.1.bb   | 5 +++++
 2 files changed, 5 insertions(+), 5 deletions(-)
 delete mode 100644 meta/recipes-extended/gperf/gperf_3.0.4.bb
 create mode 100644 meta/recipes-extended/gperf/gperf_3.1.bb

diff --git a/meta/recipes-extended/gperf/gperf_3.0.4.bb b/meta/recipes-extended/gperf/gperf_3.0.4.bb
deleted file mode 100644
index 64003fc0bb7..00000000000
--- a/meta/recipes-extended/gperf/gperf_3.0.4.bb
+++ /dev/null
@@ -1,5 +0,0 @@
-require gperf.inc
-
-
-SRC_URI[md5sum] = "c1f1db32fb6598d6a93e6e88796a8632"
-SRC_URI[sha256sum] = "767112a204407e62dbc3106647cf839ed544f3cf5d0f0523aaa2508623aad63e"
diff --git a/meta/recipes-extended/gperf/gperf_3.1.bb b/meta/recipes-extended/gperf/gperf_3.1.bb
new file mode 100644
index 00000000000..942820b91d5
--- /dev/null
+++ b/meta/recipes-extended/gperf/gperf_3.1.bb
@@ -0,0 +1,5 @@
+require gperf.inc
+
+
+SRC_URI[md5sum] = "9e251c0a618ad0824b51117d5d9db87e"
+SRC_URI[sha256sum] = "588546b945bba4b70b6a3a616e80b4ab466e3f33024a352fc2198112cdbb3ae2"
-- 
2.13.2

[PATCH 06/11] vala: upgrade to 0.36.4

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-devtools/vala/{vala_0.36.3.bb => vala_0.36.4.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/vala/{vala_0.36.3.bb => vala_0.36.4.bb} (56%)

diff --git a/meta/recipes-devtools/vala/vala_0.36.3.bb b/meta/recipes-devtools/vala/vala_0.36.4.bb
similarity index 56%
rename from meta/recipes-devtools/vala/vala_0.36.3.bb
rename to meta/recipes-devtools/vala/vala_0.36.4.bb
index e5707c88434..51000d9e126 100644
--- a/meta/recipes-devtools/vala/vala_0.36.3.bb
+++ b/meta/recipes-devtools/vala/vala_0.36.4.bb
@@ -4,5 +4,5 @@ SRC_URI += " file://0001-git-version-gen-don-t-append-dirty-if-we-re-not-in-g.pa
              file://0001-vapigen.m4-use-PKG_CONFIG_SYSROOT_DIR.patch \
 "
 
-SRC_URI[md5sum] = "ff093f46e1d2e0b179543ec43cf27d76"
-SRC_URI[sha256sum] = "ac8a4ecd01f62d0c5f62ba50b7290d8c5a1edb308eec772a65b8e79be68f061c"
+SRC_URI[md5sum] = "3c19014093f1a3d995357253b463082c"
+SRC_URI[sha256sum] = "e9f23ce711c1a72ce664d10946fbc5953f01b0b7f2a3562e7a01e362d86de059"
-- 
2.13.2

[PATCH 07/11] eudev: update to 3.2.2

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-core/udev/{eudev_3.2.1.bb => eudev_3.2.2.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-core/udev/{eudev_3.2.1.bb => eudev_3.2.2.bb} (96%)

diff --git a/meta/recipes-core/udev/eudev_3.2.1.bb b/meta/recipes-core/udev/eudev_3.2.2.bb
similarity index 96%
rename from meta/recipes-core/udev/eudev_3.2.1.bb
rename to meta/recipes-core/udev/eudev_3.2.2.bb
index bdfb5441ade..78fef2c1441 100644
--- a/meta/recipes-core/udev/eudev_3.2.1.bb
+++ b/meta/recipes-core/udev/eudev_3.2.2.bb
@@ -23,8 +23,8 @@ SRC_URI = "https://github.com/gentoo/${BPN}/archive/v${PV}.tar.gz;downloadfilena
 "
 UPSTREAM_CHECK_URI = "https://github.com/gentoo/eudev/releases"
 
-SRC_URI[md5sum] = "a2aae16bc432eac0e71c1267c384e295"
-SRC_URI[sha256sum] = "88f530c1540750e6daa91b5eaeebf88e761e6f0c86515c1c28eedfd871f027c6"
+SRC_URI[md5sum] = "1a0faad3a88ade3475e8c0ddef78e30b"
+SRC_URI[sha256sum] = "80628191448886846ab9cc0e2af6782358a0afb81d5b4f8cd9d982d2626cca31"
 
 inherit autotools update-rc.d qemu pkgconfig
 
-- 
2.13.2

[PATCH 08/11] mpg123: update to 1.25.4

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-multimedia/mpg123/{mpg123_1.25.0.bb => mpg123_1.25.4.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-multimedia/mpg123/{mpg123_1.25.0.bb => mpg123_1.25.4.bb} (94%)

diff --git a/meta/recipes-multimedia/mpg123/mpg123_1.25.0.bb b/meta/recipes-multimedia/mpg123/mpg123_1.25.4.bb
similarity index 94%
rename from meta/recipes-multimedia/mpg123/mpg123_1.25.0.bb
rename to meta/recipes-multimedia/mpg123/mpg123_1.25.4.bb
index f86098ce20b..96e8f21b754 100644
--- a/meta/recipes-multimedia/mpg123/mpg123_1.25.0.bb
+++ b/meta/recipes-multimedia/mpg123/mpg123_1.25.4.bb
@@ -11,8 +11,8 @@ LICENSE_FLAGS = "commercial"
 LIC_FILES_CHKSUM = "file://COPYING;md5=1e86753638d3cf2512528b99079bc4f3"
 
 SRC_URI = "https://www.mpg123.de/download/${BP}.tar.bz2"
-SRC_URI[md5sum] = "2ffbe29c99130215b0ee7d1b11c0ea4b"
-SRC_URI[sha256sum] = "552e3e1db045e00f474252917007795ac295863fc8b13891859b3382d2f24e48"
+SRC_URI[md5sum] = "810e9d00fd75c92c4afafa20245317b5"
+SRC_URI[sha256sum] = "cdb5620e8aab83f75a27dab3394a44b9cc4017fc77b2954b8425ca416db6b3e7"
 
 inherit autotools pkgconfig
 
-- 
2.13.2

[PATCH 09/11] oprofile: fix upstream version check

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-kernel/oprofile/oprofile.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-kernel/oprofile/oprofile.inc b/meta/recipes-kernel/oprofile/oprofile.inc
index 96ef43dc301..4b01654fa3e 100644
--- a/meta/recipes-kernel/oprofile/oprofile.inc
+++ b/meta/recipes-kernel/oprofile/oprofile.inc
@@ -27,6 +27,8 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz \
            file://0001-Add-rmb-definition-for-NIOS2-architecture.patch \
            file://0001-Fix-FTBFS-problem-with-GCC-6.patch \
 "
+UPSTREAM_CHECK_REGEX = "oprofile-(?P<pver>\d+(\.\d+)+)/"
+UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/oprofile/files/oprofile/"
 
 SRC_URI_append_libc-musl = " file://musl.patch"
 
-- 
2.13.2

[PATCH 10/11] webkitgtk: update to 2.16.6

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-sato/webkit/{webkitgtk_2.16.5.bb => webkitgtk_2.16.6.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-sato/webkit/{webkitgtk_2.16.5.bb => webkitgtk_2.16.6.bb} (97%)

diff --git a/meta/recipes-sato/webkit/webkitgtk_2.16.5.bb b/meta/recipes-sato/webkit/webkitgtk_2.16.6.bb
similarity index 97%
rename from meta/recipes-sato/webkit/webkitgtk_2.16.5.bb
rename to meta/recipes-sato/webkit/webkitgtk_2.16.6.bb
index dcaf8a6ed79..fbc74dc4da5 100644
--- a/meta/recipes-sato/webkit/webkitgtk_2.16.5.bb
+++ b/meta/recipes-sato/webkit/webkitgtk_2.16.6.bb
@@ -23,8 +23,8 @@ SRC_URI = "http://www.webkitgtk.org/releases/${BPN}-${PV}.tar.xz \
            file://detect-atomics-during-configure.patch \
            "
 
-SRC_URI[md5sum] = "fce72dc89cd310a663d9eb97133861fe"
-SRC_URI[sha256sum] = "8e0396f3428e757898c5856e642eed4fcd5a20ae03d96d3eaa03b76634be7dd4"
+SRC_URI[md5sum] = "0e2d142a586e4ff79cf0324f4fdbf20c"
+SRC_URI[sha256sum] = "fc23650df953123c59b9c0edf3855e7bd55bd107820997fc72375811e1ea4b21"
 
 inherit cmake pkgconfig gobject-introspection perlnative distro_features_check upstream-version-is-even gtk-doc
 
-- 
2.13.2

[PATCH 11/11] valgrind: fix upstream version check

[Alexander Kanavin]

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-devtools/valgrind/valgrind_3.13.0.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb
index feab5fc1a19..e1ff29a3120 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.13.0.bb
@@ -40,6 +40,7 @@ SRC_URI = "ftp://sourceware.org/pub/valgrind/valgrind-${PV}.tar.bz2 \
            "
 SRC_URI[md5sum] = "817dd08f1e8a66336b9ff206400a5369"
 SRC_URI[sha256sum] = "d76680ef03f00cd5e970bbdcd4e57fb1f6df7d2e2c071635ef2be74790190c3b"
+UPSTREAM_CHECK_REGEX = "valgrind-(?P<pver>\d+(\.\d+)+)\.tar"
 
 COMPATIBLE_HOST = '(i.86|x86_64|arm|aarch64|mips|powerpc|powerpc64).*-linux'
 
-- 
2.13.2

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]

This breaks the libcap build:

| In file included from <command-line>:0:0:
| ./_caps_output.gperf:71:80: error: unknown type name 'size_t'
|  gperf_case_strncmp (register const char *s1, register const char *s2,
register size_t n)
|
      ^~~~~~
| ./_caps_output.gperf:96:53: error: unknown type name 'size_t'
|  __cap_hash_name (register const char *str, register size_t len)
|                                                      ^~~~~~
| ./_caps_output.gperf:200:55: error: unknown type name 'size_t'
|  __cap_lookup_name (register const char *str, register size_t len)
|                                                        ^~~~~~
| ./_caps_output.gperf:200:1: error: conflicting types for
'__cap_lookup_name'
|  __cap_lookup_name (register const char *str, register size_t len)
|  ^~~~~~~~~~~~~~~~~
| ./_caps_output.gperf:33:29: note: previous declaration of
'__cap_lookup_name' was here
|  const struct __cap_token_s *__cap_lookup_name(const char *, unsigned
int);
|                              ^~~~~~~~~~~~~~~~~
| cap_text.c: In function 'cap_to_name':
| cap_text.c:291:2: warning: ignoring return value of 'asprintf', declared
with attribute warn_unused_result [-Wunused-result]
|   asprintf(&tmp, "%u", cap);
|   ^~~~~~~~~~~~~~~~~~~~~~~~~
| Makefile:63: recipe for target 'cap_text.o' failed

Ross

On 24 July 2017 at 15:28, Alexander Kanavin <
alexander.kanavin@linux.intel.com> wrote:

> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
>  meta/recipes-extended/gperf/gperf_3.0.4.bb | 5 -----
>  meta/recipes-extended/gperf/gperf_3.1.bb   | 5 +++++
>  2 files changed, 5 insertions(+), 5 deletions(-)
>  delete mode 100644 meta/recipes-extended/gperf/gperf_3.0.4.bb
>  create mode 100644 meta/recipes-extended/gperf/gperf_3.1.bb
>
> diff --git a/meta/recipes-extended/gperf/gperf_3.0.4.bb
> b/meta/recipes-extended/gperf/gperf_3.0.4.bb
> deleted file mode 100644
> index 64003fc0bb7..00000000000
> --- a/meta/recipes-extended/gperf/gperf_3.0.4.bb
> +++ /dev/null
> @@ -1,5 +0,0 @@
> -require gperf.inc
> -
> -
> -SRC_URI[md5sum] = "c1f1db32fb6598d6a93e6e88796a8632"
> -SRC_URI[sha256sum] = "767112a204407e62dbc3106647cf83
> 9ed544f3cf5d0f0523aaa2508623aad63e"
> diff --git a/meta/recipes-extended/gperf/gperf_3.1.bb
> b/meta/recipes-extended/gperf/gperf_3.1.bb
> new file mode 100644
> index 00000000000..942820b91d5
> --- /dev/null
> +++ b/meta/recipes-extended/gperf/gperf_3.1.bb
> @@ -0,0 +1,5 @@
> +require gperf.inc
> +
> +
> +SRC_URI[md5sum] = "9e251c0a618ad0824b51117d5d9db87e"
> +SRC_URI[sha256sum] = "588546b945bba4b70b6a3a616e80b4
> ab466e3f33024a352fc2198112cdbb3ae2"
> --
> 2.13.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 4925 bytes --]

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Khem Raj]

On Tue, Jul 25, 2017 at 6:12 AM, Burton, Ross <ross.burton@intel.com> wrote:
> This breaks the libcap build:
>
> | In file included from <command-line>:0:0:
> | ./_caps_output.gperf:71:80: error: unknown type name 'size_t'

include <stddef.h> might help

> |  gperf_case_strncmp (register const char *s1, register const char *s2,
> register size_t n)
> |
> ^~~~~~
> | ./_caps_output.gperf:96:53: error: unknown type name 'size_t'
> |  __cap_hash_name (register const char *str, register size_t len)
> |                                                      ^~~~~~

gcc is putting a caret pointer in wrong place hmm may be a cut and paste error

> | ./_caps_output.gperf:200:55: error: unknown type name 'size_t'
> |  __cap_lookup_name (register const char *str, register size_t len)
> |                                                        ^~~~~~
> | ./_caps_output.gperf:200:1: error: conflicting types for
> '__cap_lookup_name'
> |  __cap_lookup_name (register const char *str, register size_t len)
> |  ^~~~~~~~~~~~~~~~~
> | ./_caps_output.gperf:33:29: note: previous declaration of
> '__cap_lookup_name' was here
> |  const struct __cap_token_s *__cap_lookup_name(const char *, unsigned
> int);
> |                              ^~~~~~~~~~~~~~~~~
> | cap_text.c: In function 'cap_to_name':
> | cap_text.c:291:2: warning: ignoring return value of 'asprintf', declared
> with attribute warn_unused_result [-Wunused-result]
> |   asprintf(&tmp, "%u", cap);
> |   ^~~~~~~~~~~~~~~~~~~~~~~~~
> | Makefile:63: recipe for target 'cap_text.o' failed
>
> Ross
>
> On 24 July 2017 at 15:28, Alexander Kanavin
> <alexander.kanavin@linux.intel.com> wrote:
>>
>> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
>> ---
>>  meta/recipes-extended/gperf/gperf_3.0.4.bb | 5 -----
>>  meta/recipes-extended/gperf/gperf_3.1.bb   | 5 +++++
>>  2 files changed, 5 insertions(+), 5 deletions(-)
>>  delete mode 100644 meta/recipes-extended/gperf/gperf_3.0.4.bb
>>  create mode 100644 meta/recipes-extended/gperf/gperf_3.1.bb
>>
>> diff --git a/meta/recipes-extended/gperf/gperf_3.0.4.bb
>> b/meta/recipes-extended/gperf/gperf_3.0.4.bb
>> deleted file mode 100644
>> index 64003fc0bb7..00000000000
>> --- a/meta/recipes-extended/gperf/gperf_3.0.4.bb
>> +++ /dev/null
>> @@ -1,5 +0,0 @@
>> -require gperf.inc
>> -
>> -
>> -SRC_URI[md5sum] = "c1f1db32fb6598d6a93e6e88796a8632"
>> -SRC_URI[sha256sum] =
>> "767112a204407e62dbc3106647cf839ed544f3cf5d0f0523aaa2508623aad63e"
>> diff --git a/meta/recipes-extended/gperf/gperf_3.1.bb
>> b/meta/recipes-extended/gperf/gperf_3.1.bb
>> new file mode 100644
>> index 00000000000..942820b91d5
>> --- /dev/null
>> +++ b/meta/recipes-extended/gperf/gperf_3.1.bb
>> @@ -0,0 +1,5 @@
>> +require gperf.inc
>> +
>> +
>> +SRC_URI[md5sum] = "9e251c0a618ad0824b51117d5d9db87e"
>> +SRC_URI[sha256sum] =
>> "588546b945bba4b70b6a3a616e80b4ab466e3f33024a352fc2198112cdbb3ae2"
>> --
>> 2.13.2
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 4242 bytes --]

And libid3tag:

| compat.gperf:116:1: error: conflicting types for 'id3_compat_lookup'
| In file included from compat.gperf:37:0:
| ../libid3tag-0.15.1b/compat.h:36:26: note: previous declaration of
'id3_compat_lookup' was here
|  struct id3_compat const *id3_compat_lookup(register char const *,
|                           ^~~~~~~~~~~~~~~~~

http://git.savannah.gnu.org/cgit/gperf.git/commit/?id=d519d1a821511eaa22eae6d9019a548aea21e6d3
is the upstream commit that breaks everything, because the API of the
generated files has changed.

Ross

On 25 July 2017 at 14:53, Khem Raj <raj.khem@gmail.com> wrote:

> On Tue, Jul 25, 2017 at 6:12 AM, Burton, Ross <ross.burton@intel.com>
> wrote:
> > This breaks the libcap build:
> >
> > | In file included from <command-line>:0:0:
> > | ./_caps_output.gperf:71:80: error: unknown type name 'size_t'
>
> include <stddef.h> might help
>
> > |  gperf_case_strncmp (register const char *s1, register const char *s2,
> > register size_t n)
> > |
> > ^~~~~~
> > | ./_caps_output.gperf:96:53: error: unknown type name 'size_t'
> > |  __cap_hash_name (register const char *str, register size_t len)
> > |                                                      ^~~~~~
>
> gcc is putting a caret pointer in wrong place hmm may be a cut and paste
> error
>
> > | ./_caps_output.gperf:200:55: error: unknown type name 'size_t'
> > |  __cap_lookup_name (register const char *str, register size_t len)
> > |                                                        ^~~~~~
> > | ./_caps_output.gperf:200:1: error: conflicting types for
> > '__cap_lookup_name'
> > |  __cap_lookup_name (register const char *str, register size_t len)
> > |  ^~~~~~~~~~~~~~~~~
> > | ./_caps_output.gperf:33:29: note: previous declaration of
> > '__cap_lookup_name' was here
> > |  const struct __cap_token_s *__cap_lookup_name(const char *, unsigned
> > int);
> > |                              ^~~~~~~~~~~~~~~~~
> > | cap_text.c: In function 'cap_to_name':
> > | cap_text.c:291:2: warning: ignoring return value of 'asprintf',
> declared
> > with attribute warn_unused_result [-Wunused-result]
> > |   asprintf(&tmp, "%u", cap);
> > |   ^~~~~~~~~~~~~~~~~~~~~~~~~
> > | Makefile:63: recipe for target 'cap_text.o' failed
> >
> > Ross
> >
> > On 24 July 2017 at 15:28, Alexander Kanavin
> > <alexander.kanavin@linux.intel.com> wrote:
> >>
> >> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> >> ---
> >>  meta/recipes-extended/gperf/gperf_3.0.4.bb | 5 -----
> >>  meta/recipes-extended/gperf/gperf_3.1.bb   | 5 +++++
> >>  2 files changed, 5 insertions(+), 5 deletions(-)
> >>  delete mode 100644 meta/recipes-extended/gperf/gperf_3.0.4.bb
> >>  create mode 100644 meta/recipes-extended/gperf/gperf_3.1.bb
> >>
> >> diff --git a/meta/recipes-extended/gperf/gperf_3.0.4.bb
> >> b/meta/recipes-extended/gperf/gperf_3.0.4.bb
> >> deleted file mode 100644
> >> index 64003fc0bb7..00000000000
> >> --- a/meta/recipes-extended/gperf/gperf_3.0.4.bb
> >> +++ /dev/null
> >> @@ -1,5 +0,0 @@
> >> -require gperf.inc
> >> -
> >> -
> >> -SRC_URI[md5sum] = "c1f1db32fb6598d6a93e6e88796a8632"
> >> -SRC_URI[sha256sum] =
> >> "767112a204407e62dbc3106647cf839ed544f3cf5d0f0523aaa2508623aad63e"
> >> diff --git a/meta/recipes-extended/gperf/gperf_3.1.bb
> >> b/meta/recipes-extended/gperf/gperf_3.1.bb
> >> new file mode 100644
> >> index 00000000000..942820b91d5
> >> --- /dev/null
> >> +++ b/meta/recipes-extended/gperf/gperf_3.1.bb
> >> @@ -0,0 +1,5 @@
> >> +require gperf.inc
> >> +
> >> +
> >> +SRC_URI[md5sum] = "9e251c0a618ad0824b51117d5d9db87e"
> >> +SRC_URI[sha256sum] =
> >> "588546b945bba4b70b6a3a616e80b4ab466e3f33024a352fc2198112cdbb3ae2"
> >> --
> >> 2.13.2
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> >
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
>

[-- Attachment #2: Type: text/html, Size: 7162 bytes --]

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Alexander Kanavin]

On 07/28/2017 05:50 PM, Burton, Ross wrote:
> And libid3tag:
> 
> | compat.gperf:116:1: error: conflicting types for 'id3_compat_lookup' | 
> In file included from compat.gperf:37:0: | 
> ../libid3tag-0.15.1b/compat.h:36:26: note: previous declaration of 
> 'id3_compat_lookup' was here | struct id3_compat const 
> *id3_compat_lookup(register char const *, | ^~~~~~~~~~~~~~~~~
> 
> http://git.savannah.gnu.org/cgit/gperf.git/commit/?id=d519d1a821511eaa22eae6d9019a548aea21e6d3 
> is the upstream commit that breaks everything, because the API of the 
> generated files has changed.

Right. Should we just stop fighting with this, and put a 
RECIPE_NO_UPDATE_REASON into gperf? I'd rather not update gperf with 
this change reverted.

Alex

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Richard Purdie]

On Mon, 2017-07-31 at 12:35 +0300, Alexander Kanavin wrote:
> On 07/28/2017 05:50 PM, Burton, Ross wrote:
> > 
> > And libid3tag:
> > 
> > > 
> > > compat.gperf:116:1: error: conflicting types for
> > > 'id3_compat_lookup' | 
> > In file included from compat.gperf:37:0: | 
> > ../libid3tag-0.15.1b/compat.h:36:26: note: previous declaration of 
> > 'id3_compat_lookup' was here | struct id3_compat const 
> > *id3_compat_lookup(register char const *, | ^~~~~~~~~~~~~~~~~
> > 
> > http://git.savannah.gnu.org/cgit/gperf.git/commit/?id=d519d1a821511
> > eaa22eae6d9019a548aea21e6d3 
> > is the upstream commit that breaks everything, because the API of
> > the 
> > generated files has changed.
> Right. Should we just stop fighting with this, and put a 
> RECIPE_NO_UPDATE_REASON into gperf? I'd rather not update gperf with 
> this change reverted.

It does feel like upstream screwed up and should really sort this out.
Do you know what upstream plan to do (if anything)?

Cheers,

Richard

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Alexander Kanavin]

On 07/31/2017 12:43 PM, Richard Purdie wrote:

>> Right. Should we just stop fighting with this, and put a
>> RECIPE_NO_UPDATE_REASON into gperf? I'd rather not update gperf with
>> this change reverted.
> 
> It does feel like upstream screwed up and should really sort this out.
> Do you know what upstream plan to do (if anything)?

The only thing I found was this email:
http://lists.gnu.org/archive/html/bug-gperf/2017-01/msg00004.html
which was ignored by upstream.

However, both debian testing and fedora rawhide have gperf 3.1, so I'm 
not sure how they made it work. I'm running debian here, so can look 
into this.

Alex

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Alexander Kanavin]

On 07/31/2017 12:53 PM, Alexander Kanavin wrote:
> The only thing I found was this email:
> http://lists.gnu.org/archive/html/bug-gperf/2017-01/msg00004.html
> which was ignored by upstream.
> 
> However, both debian testing and fedora rawhide have gperf 3.1, so I'm 
> not sure how they made it work. I'm running debian here, so can look 
> into this.

Right. Debian dropped the updated gperf package into repositories, but 
did not rebuild anything that relies on it. When I tried that with 
libcap, I got the exact same error as we've seen.

Not sure what's going to happen when they discover the incompatibility. 
I'm a bit surprised they don't do such dependency rebuilds when changes 
are introduced.

Alex

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

Neither Debian not Fedora rebuild dependencies, you'll see a lot of
"rebuild" changelog entries where API changes demanded it to happen.

Our builds take longer but you know the build always works.  Their builds
may be broken without anyone noticing for a while.

Ross

On 31 July 2017 at 11:18, Alexander Kanavin <
alexander.kanavin@linux.intel.com> wrote:

> On 07/31/2017 12:53 PM, Alexander Kanavin wrote:
>
>> The only thing I found was this email:
>> http://lists.gnu.org/archive/html/bug-gperf/2017-01/msg00004.html
>> which was ignored by upstream.
>>
>> However, both debian testing and fedora rawhide have gperf 3.1, so I'm
>> not sure how they made it work. I'm running debian here, so can look into
>> this.
>>
>
> Right. Debian dropped the updated gperf package into repositories, but did
> not rebuild anything that relies on it. When I tried that with libcap, I
> got the exact same error as we've seen.
>
> Not sure what's going to happen when they discover the incompatibility.
> I'm a bit surprised they don't do such dependency rebuilds when changes are
> introduced.
>
> Alex
>

[-- Attachment #2: Type: text/html, Size: 1770 bytes --]

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Khem Raj]

On Mon, Jul 31, 2017 at 7:55 AM, Burton, Ross <ross.burton@intel.com> wrote:
> Neither Debian not Fedora rebuild dependencies, you'll see a lot of
> "rebuild" changelog entries where API changes demanded it to happen.
>
> Our builds take longer but you know the build always works.  Their builds
> may be broken without anyone noticing for a while.
>
> Ross
>
> On 31 July 2017 at 11:18, Alexander Kanavin
> <alexander.kanavin@linux.intel.com> wrote:
>>
>> On 07/31/2017 12:53 PM, Alexander Kanavin wrote:
>>>
>>> The only thing I found was this email:
>>> http://lists.gnu.org/archive/html/bug-gperf/2017-01/msg00004.html
>>> which was ignored by upstream.
>>>
>>> However, both debian testing and fedora rawhide have gperf 3.1, so I'm
>>> not sure how they made it work. I'm running debian here, so can look into
>>> this.
>>
>>
>> Right. Debian dropped the updated gperf package into repositories, but did
>> not rebuild anything that relies on it. When I tried that with libcap, I got
>> the exact same error as we've seen.

they do mass rebuilds but thats not like us where we build it daily.

>>
>> Not sure what's going to happen when they discover the incompatibility.
>> I'm a bit surprised they don't do such dependency rebuilds when changes are
>> introduced.
>>
>> Alex
>
>

Re: [PATCH 05/11] gperf: upgrade to 3.1

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 688 bytes --]

On 31 July 2017 at 10:43, Richard Purdie <richard.purdie@linuxfoundation.org
> wrote:

> It does feel like upstream screwed up and should really sort this out.
> Do you know what upstream plan to do (if anything)?
>

Upstream fixed a problem and whilst it was way to big a change for a point
release the code is probably "better" now.  It just breaks everything, and
you can't even be compatible with both versions.

For what its worth, systemd added a check for the argument type in
configure.ac[1] (and now meson) but also just demands 3.1, presumably for
the new options.

Ross

[1]
https://github.com/systemd/systemd/commit/c9f7b4d356a453a01aa77a6bb74ca7ef49732c08

[-- Attachment #2: Type: text/html, Size: 1277 bytes --]