From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/libnpupnp: needs gcc >= 7
Date: Tue, 14 Jul 2026 11:25:10 +0200 [thread overview]
Message-ID: <9cd20fee98212e3f670168fe7e3a3091@free.fr> (raw)
In-Reply-To: <20260704100700.2336075-1-bernd@kuhls.net>
On 04/07/2026 12:06, Bernd Kuhls wrote:
> Buildroot commit 2774502344f35b587ea8f1a2f43ec2398c3ebdad bumped the
> package from 4.2.2 to 6.2.3. Upstream added the usage of
> std::scoped_lock in version 6.2.0:
> https://framagit.org/medoc92/npupnp/-/commit/a760b3278aee06408d9f50d0c54942f5ba9df989
>
> causing a build error detected by the Gitlab pipelines for the
> bootlin-aarch64-glibc-old defconfig:
>
> ../src/inc/upnpapi.h:132:22: error:
> ‘scoped_lock’ is not a member of ‘std’
>
> scoped_lock was introduced in gcc 7.1:
> https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017
>
> so we raise the minimum required gcc version accordingly.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-14 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 10:06 [Buildroot] [PATCH 1/2] package/libnpupnp: needs gcc >= 7 Bernd Kuhls
2026-07-04 10:07 ` [Buildroot] [PATCH 2/2] package/libnpupnp: bump version to 6.3.0 Bernd Kuhls
2026-07-14 9:25 ` Julien Olivain via buildroot [this message]
2026-07-17 15:47 ` [Buildroot] [PATCH 1/2] package/libnpupnp: needs gcc >= 7 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=9cd20fee98212e3f670168fe7e3a3091@free.fr \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fontaine.fabrice@gmail.com \
--cc=ju.o@free.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