public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/docker: Fix build with gcc-15.x
Date: Sat, 14 Mar 2026 08:53:23 +0100	[thread overview]
Message-ID: <20260314075323.14729-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260307093629.22188-1-bernd@kuhls.net>

In reply of:
> Add patch from Debian to fix build error with gcc-15.x
> 
> Fixes:
> https://autobuild.buildroot.net/results/495/4956555fd033d43c1877e66141789bcd06aff5be/
> 
> Patch sent to fork which is used by Arch Linux:
> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wmdocker
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to 2025.11.x & 2026.02.x. Thanks

> ---
> v2: updated upstream URL after commit of the PR
> 
>  ...tibility-explicit-fallthrough-undecl.patch | 38 +++++++++++++++++++
>  1 file changed, 38 insertions(+)
>  create mode 100644 package/docker/0001-fix-gcc-15-compatibility-explicit-fallthrough-undecl.patch
> 
> diff --git a/package/docker/0001-fix-gcc-15-compatibility-explicit-fallthrough-undecl.patch b/package/docker/0001-fix-gcc-15-compatibility-explicit-fallthrough-undecl.patch
> new file mode 100644
> index 0000000000..c0dc18d17a
> --- /dev/null
> +++ b/package/docker/0001-fix-gcc-15-compatibility-explicit-fallthrough-undecl.patch
> @@ -0,0 +1,38 @@
> +From 55054532589041e3c7b970fefaeeeee871f4f6be Mon Sep 17 00:00:00 2001
> +From: Tianon Gravi <tianon@debian.org>
> +Date: Wed, 25 Feb 2026 08:24:26 +0100
> +Subject: [PATCH] fix gcc-15+ compatibility (explicit fallthrough,
> + undeclared/unused arguments)
> +
> +Downloaded from Debian:
> +https://sources.debian.org/src/docker/1.5-6/debian/patches/gcc-15.patch
> +
> +Upstream: https://github.com/mdomlop/wmdocker/commit/55054532589041e3c7b970fefaeeeee871f4f6be
> +
> +[Bernd: rebased patch]
> +Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> +---
> + docker.c | 3 ++-
> + 1 file changed, 2 insertions(+), 1 deletion(-)
> +
> +diff --git a/docker.c b/docker.c
> +index 4cc8d78..6105ab8 100644
> +--- a/docker.c
> ++++ b/docker.c
> +@@ -46,7 +46,7 @@ void signal_handler(int signal)
> + }
> + 
> + 
> +-void parse_cmd_line()
> ++void parse_cmd_line(int argc, char **argv)
> + {
> +   int i;
> +   gboolean help = FALSE;
> +@@ -283,6 +283,7 @@ void event_loop()
> +       case ReparentNotify:
> +         if (e.xany.window == win) /* reparented to us */
> +           break;
> ++        /* fallthrough */
> +       case UnmapNotify:
> +       case DestroyNotify:
> +         for (it = icons; it; it = g_slist_next(it)) {
> -- 
> 2.47.3
> 
> _______________________________________________
> 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-03-14  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07  9:36 [Buildroot] [PATCH v2 1/1] package/docker: Fix build with gcc-15.x Bernd Kuhls
2026-03-07 10:49 ` Julien Olivain via buildroot
2026-03-14  7:53 ` Thomas Perale via buildroot [this message]

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=20260314075323.14729-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=thomas.perale@mind.be \
    /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