Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/gzip: bump version to 1.15
Date: Sun, 4 Oct 2026 14:18:12 +0200	[thread overview]
Message-ID: <asJEBMQpD2FYJql2@waldemar-brodkorb.de> (raw)
In-Reply-To: <20261002135956.354969-1-ps.report@gmx.net>

Hi Peter,

I am having issues compiling gzip after the update for
qemu-system-aarch64 (defconfig, glibc):

  GEN      zmore
In file included from gzip.c:61:
gzip.h:120:21: error: expected ')' before '+' token
  120 | #  define head (prev+WSIZE)  /* hash head (see deflate.c) */
      |                     ^
gzip.h:120:21: error: expected ')' before '+' token
  120 | #  define head (prev+WSIZE)  /* hash head (see deflate.c) */
      |                     ^
...

No autobuild failures, yet.

Any idea?

best regards
 Waldemar


Peter Seiderer via buildroot wrote,

> - bump version to 1.15 (for details see [1] and [2])
> 
> [1] https://cgit.git.savannah.gnu.org/cgit/gzip.git/tree/NEWS?id=e6263160768c73f6117f3c1de78291a60f2cb796
> [2] https://lists.gnu.org/r/bug-gzip/2026-09/msg00030.html
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  package/gzip/gzip.hash | 4 ++--
>  package/gzip/gzip.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/gzip/gzip.hash b/package/gzip/gzip.hash
> index 90c9be4e6e..ddf5e38f0f 100644
> --- a/package/gzip/gzip.hash
> +++ b/package/gzip/gzip.hash
> @@ -1,6 +1,6 @@
>  # Locally calculated after checking pgp signature
> -# https://ftp.gnu.org/gnu/gzip/gzip-1.14.tar.xz.sig
> +# https://ftp.gnu.org/gnu/gzip/gzip-1.15.tar.xz.sig
>  # using key 155D3FC500C834486D1EEA677FD9FCCB000BEEEE
> -sha256  01a7b881bd220bfdf615f97b8718f80bdfd3f6add385b993dcf6efd14e8c0ac6  gzip-1.14.tar.xz
> +sha256  9aa0cc780dec156b8282844833b342ab7cb08c25d2cd9a1869cdd0df31deff48  gzip-1.15.tar.xz
>  # Locally calculated
>  sha256  3972dc9744f6499f0f9b2dbf76696f2ae7ad8af9b23dde66d6af86c9dfb36986  COPYING
> diff --git a/package/gzip/gzip.mk b/package/gzip/gzip.mk
> index e79de4c99e..1c74089147 100644
> --- a/package/gzip/gzip.mk
> +++ b/package/gzip/gzip.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -GZIP_VERSION = 1.14
> +GZIP_VERSION = 1.15
>  GZIP_SOURCE = gzip-$(GZIP_VERSION).tar.xz
>  GZIP_SITE = $(BR2_GNU_MIRROR)/gzip
>  # Some other tools expect it to be in /bin
> -- 
> 2.55.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-10-04 12:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 13:59 [Buildroot] [PATCH v1] package/gzip: bump version to 1.15 Peter Seiderer via buildroot
2026-10-02 19:34 ` Thomas Petazzoni via buildroot
2026-10-04 12:18 ` Waldemar Brodkorb [this message]
2026-10-04 13:51   ` Peter Seiderer via buildroot
2026-10-05  4:47     ` Waldemar Brodkorb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=asJEBMQpD2FYJql2@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@buildroot.org \
    --cc=ps.report@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox