From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pistache: fix build with gcc >= 13
Date: Thu, 2 Nov 2023 18:46:09 +0100 [thread overview]
Message-ID: <20231102184609.72475a8a@windsurf> (raw)
In-Reply-To: <20231102171118.4810-1-fontaine.fabrice@gmail.com>
On Thu, 2 Nov 2023 18:11:18 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure with gcc >= 13:
>
> In file included from ../include/pistache/reactor.h:19,
> from ../src/common/reactor.cc:13:
> ../include/pistache/flags.h:29:35: error: 'uint8_t' was not declared in this scope
> 29 | struct TypeStorage<sizeof(uint8_t)>
> | ^~~~~~~
> ../include/pistache/flags.h:17:1: note: 'uint8_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'?
> 16 | #include <iostream>
> +++ |+#include <cstdint>
> 17 | #include <type_traits>
>
> Fixes:
> - http://autobuild.buildroot.org/results/d3b6eb6fb943d69571a311235944df879fccc831
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...-missing-cstdint-header-include-1142.patch | 23 +++++++++++++++++++
> 1 file changed, 23 insertions(+)
> create mode 100644 package/pistache/0003-Add-missing-cstdint-header-include-1142.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-02 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 17:11 [Buildroot] [PATCH 1/1] package/pistache: fix build with gcc >= 13 Fabrice Fontaine
2023-11-02 17:46 ` Thomas Petazzoni via buildroot [this message]
2023-11-08 13:39 ` Peter Korsgaard
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=20231102184609.72475a8a@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox