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/rwmem: fix build with gcc 13
Date: Sat, 4 Nov 2023 22:31:39 +0100 [thread overview]
Message-ID: <20231104223139.473d6479@windsurf> (raw)
In-Reply-To: <20231001143708.964342-1-fontaine.fabrice@gmail.com>
On Sun, 1 Oct 2023 16:37:08 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure with gcc 13:
>
> In file included from ../librwmem/itarget.h:3,
> from ../librwmem/i2ctarget.h:4,
> from ../librwmem/i2ctarget.cpp:1:
> ../librwmem/helpers.h:51:39: error: 'uint64_t' has not been declared
> 51 | int parse_u64(const std::string& str, uint64_t* value);
> | ^~~~~~~~
>
> Fixes:
> - http://autobuild.buildroot.org/results/38f6d0fb007c3dc3c21243721395f85649442407
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> .../rwmem/0001-include-missing-cstdint.patch | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
> create mode 100644 package/rwmem/0001-include-missing-cstdint.patch
Thanks, but in the mean time, rwmem was bumped to a version that
already includes this fix.
Best regards,
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
prev parent reply other threads:[~2023-11-04 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 14:37 [Buildroot] [PATCH 1/1] package/rwmem: fix build with gcc 13 Fabrice Fontaine
2023-11-04 21:31 ` Thomas Petazzoni 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=20231104223139.473d6479@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