All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/gzip: add upstream patch to fix build for aarch64
Date: Sun, 4 Oct 2026 21:16:51 +0200	[thread overview]
Message-ID: <20261004211651.40a998e1@pc-1> (raw)
In-Reply-To: <asJz0OE5k0gQODfW@windsurf>

On Sun, 4 Oct 2026 17:42:30 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> On Sun, Oct 04, 2026 at 04:59:50PM +0200, Peter Seiderer via buildroot wrote:
> > - add 0001-build-avoid-failure-to-build-on-linux-aarch64.patch
> >   (from upstream, see [1])
> > 
> > Fixes:
> > 
> >   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) */
> >         |                     ^
> > 
> > [1] https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=b4ed8e73401968bcad749afb0e636dd3ec205ca7  
> 
> Which version bump introduced this regression?

The bump from 1.14 to 1.15 with buildroot commit

	fe21a5fe30 package/gzip: bump version to 1.15

Regards,
Peter


> 
> Thanks!
> 
> Thomas

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-04 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 14:59 [Buildroot] [PATCH v1] package/gzip: add upstream patch to fix build for aarch64 Peter Seiderer via buildroot
2026-10-04 15:42 ` Thomas Petazzoni via buildroot
2026-10-04 19:16   ` Peter Seiderer via buildroot [this message]
2026-10-06 19:19     ` Julien Olivain via buildroot

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=20261004211651.40a998e1@pc-1 \
    --to=buildroot@buildroot.org \
    --cc=ps.report@gmx.net \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.