[Buildroot] [PATCH 03/27] package/gperf: bump to version 3.1

[Buildroot] [PATCH 03/27] package/gperf: bump to version 3.1

[Christopher McCrory]

Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
---
 package/gperf/gperf.hash | 4 +++-
 package/gperf/gperf.mk   | 2 +-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/package/gperf/gperf.hash b/package/gperf/gperf.hash
index 21c76605b5..3d8aafbdca 100644
--- a/package/gperf/gperf.hash
+++ b/package/gperf/gperf.hash
@@ -1,5 +1,7 @@
 # Locally calculated after checking pgp signature
-sha256	767112a204407e62dbc3106647cf839ed544f3cf5d0f0523aaa2508623aad63e	gperf-3.0.4.tar.gz
+# https://ftp.gnu.org/pub/gnu/gperf/gperf-3.1.tar.gz.sig
+# with key 93C08C88471097CD
+sha256	588546b945bba4b70b6a3a616e80b4ab466e3f33024a352fc2198112cdbb3ae2	gperf-3.1.tar.gz
 
 # Locally calculated
 sha256	8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903	COPYING
diff --git a/package/gperf/gperf.mk b/package/gperf/gperf.mk
index 2a6192a48b..4b928a0ebd 100644
--- a/package/gperf/gperf.mk
+++ b/package/gperf/gperf.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-GPERF_VERSION = 3.0.4
+GPERF_VERSION = 3.1
 GPERF_SITE = $(BR2_GNU_MIRROR)/gperf
 GPERF_LICENSE = GPL-3.0+
 GPERF_LICENSE_FILES = COPYING
-- 
2.20.1

[Buildroot] [PATCH 03/27] package/gperf: bump to version 3.1

[Thomas Petazzoni]

On Sun,  8 Sep 2019 09:10:03 -0700
Christopher McCrory <chrismcc@gmail.com> wrote:

> Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
> ---
>  package/gperf/gperf.hash | 4 +++-
>  package/gperf/gperf.mk   | 2 +-
>  2 files changed, 4 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] [PATCH 03/27] package/gperf: bump to version 3.1

[Ricardo Martincoski]

Hello,

There are build failures on autobuilders possibly related to this bump.
See below.

On Sun, Sep 08, 2019 at 01:10 PM, Christopher McCrory wrote:

> 
> Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
> ---
>  package/gperf/gperf.hash | 4 +++-
>  package/gperf/gperf.mk   | 2 +-
>  2 files changed, 4 insertions(+), 2 deletions(-)

While testing an unrelated issue, I came across a build failure that seems
related somehow to this bump.

When testing based on current master (one patch after this one), I get a build
failure:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/290278807
With the same config but based on the commit just before this patch, the build
succeeds:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/290291133

Build failures are appearing on autobuilders:
http://autobuild.buildroot.net/?reason=host-libcap-2.25
I guess tomorrow 'Daily results' e-mail will show a plenty of them.

This is the error message:
>>> host-libcap 2.25 Building
...
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)
                                                                                ^~~~~~
...
Makefile:63: recipe for target 'cap_text.o' failed


Regards,
Ricardo

[Buildroot] [PATCH 03/27] package/gperf: bump to version 3.1

[Thomas Petazzoni]

Hello,

On Sun, 08 Sep 2019 18:09:38 -0300
Ricardo Martincoski <ricardo.martincoski@gmail.com> wrote:

> While testing an unrelated issue, I came across a build failure that seems
> related somehow to this bump.
> 
> When testing based on current master (one patch after this one), I get a build
> failure:
> https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/290278807
> With the same config but based on the commit just before this patch, the build
> succeeds:
> https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/290291133
> 
> Build failures are appearing on autobuilders:
> http://autobuild.buildroot.net/?reason=host-libcap-2.25
> I guess tomorrow 'Daily results' e-mail will show a plenty of them.

I can confirm I reproduced the issue locally, and reverting the gperf
bump fixes the issue. So I've reverted the gperf bump for now.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com