Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour via buildroot <buildroot@buildroot.org>
To: Michael Nosthoff <buildroot@heine.tech>, buildroot@buildroot.org
Cc: Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v2] package/supertux: fix build with gcc > 11
Date: Sun, 17 May 2026 23:42:09 +0200	[thread overview]
Message-ID: <4df73f6e-047f-45ae-bef2-5735fd79e021@smile.fr> (raw)
In-Reply-To: <20260407123424.3983175-2-buildroot@heine.tech>

Hello Michael, All,

Le 07/04/2026 à 14:34, Michael Nosthoff via buildroot a écrit :
> Fixes:
>  "missing #include <memory>" when building with GCC > 11.
> 
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>

Its been a while since the last release but here it is:

  https://github.com/SuperTux/supertux/releases/tag/v0.7.0

Applied to master. Thanks.

Best regards,
Romain


> 
> ---
> V2: add "Upstream" to patch
> 
> ---
>  package/supertux/0001-fix-gcc11-build.patch | 33 +++++++++++++++++++++
>  1 file changed, 33 insertions(+)
>  create mode 100644 package/supertux/0001-fix-gcc11-build.patch
> 
> diff --git a/package/supertux/0001-fix-gcc11-build.patch b/package/supertux/0001-fix-gcc11-build.patch
> new file mode 100644
> index 0000000000..d5ada531c6
> --- /dev/null
> +++ b/package/supertux/0001-fix-gcc11-build.patch
> @@ -0,0 +1,33 @@
> +From 81809dd5e6f611b1d64d952f6d96310bcc9c5fca Mon Sep 17 00:00:00 2001
> +From: Semphris <semphris@protonmail.com>
> +Date: Fri, 17 Jun 2022 12:36:26 -0400
> +Subject: [PATCH] Fix problem with GCC 11 and Partio's ZIP manager (missing
> + #include <memory>)
> +
> +Closes #2219 on GitHub. Same fix, but puts the include closer to the copyright header.
> +
> +Upstream: https://github.com/SuperTux/supertux/commit/81809dd5e6f611b1d64d952f6d96310bcc9c5fca
> +Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
> +---
> + external/partio_zip/zip_manager.hpp | 8 ++++++--
> + 1 file changed, 6 insertions(+), 2 deletions(-)
> +
> +diff --git a/external/partio_zip/zip_manager.hpp b/external/partio_zip/zip_manager.hpp
> +index 666884dda53..245303c76be 100644
> +--- a/external/partio_zip/zip_manager.hpp
> ++++ b/external/partio_zip/zip_manager.hpp
> +@@ -1,8 +1,12 @@
> + // SOURCE: https://github.com/wdas/partio/blob/main/src/lib/io/ZIP.h
> ++// NOTE: This file was edited for purposes of compatibility with SuperTux.
> + 
> +-/*
> ++// This include has been added to fix a problem with GCC 11+ (and maybe 10)
> ++#include <memory>
> ++
> ++// =============================================================================
> + 
> +-NOTE: This file was edited for purposes of compatibility with SuperTux.
> ++/*
> + 
> + PARTIO SOFTWARE
> + Copyright 2010 Disney Enterprises, Inc. All rights reserved

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

  reply	other threads:[~2026-05-17 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 12:34 [Buildroot] [PATCH v2] package/supertux: fix build with gcc > 11 Michael Nosthoff via buildroot
2026-05-17 21:42 ` Romain Naour via buildroot [this message]
2026-05-29  8:30 ` Thomas Perale 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=4df73f6e-047f-45ae-bef2-5735fd79e021@smile.fr \
    --to=buildroot@buildroot.org \
    --cc=buildroot@heine.tech \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    /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