Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/sedutil: fix build with gcc >= 13
Date: Tue, 07 Nov 2023 20:38:18 +0100	[thread overview]
Message-ID: <87bkc5wdzp.fsf@48ers.dk> (raw)
In-Reply-To: <20231101105253.GA114892@scaer> (Yann E. MORIN's message of "Wed,  1 Nov 2023 11:52:53 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Fabrice, All,
 > On 2023-10-30 09:50 +0100, Fabrice Fontaine spake thusly:
 >> Fix the following build failure with gcc >= 13:
 >> 
 >> In file included from ./Common/log.h:45,
 >> from LinuxPBA/LinuxPBA.cpp:25:
 >> ./Common/DtaOptions.h:33:5: error: 'uint8_t' does not name a type
 >> 33 |     uint8_t password;   /**< password supplied */
 >> |     ^~~~~~~
 >> ./Common/DtaOptions.h:1:1: note: 'uint8_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'?
 >> 
 >> Fixes:
 >> - http://autobuild.buildroot.org/results/b6feb4fb33d595414b61174deb9867e8c30cd186
 >> 
 >> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

 > Applied to master, thanks.

Committed to 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-11-07 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  8:50 [Buildroot] [PATCH 1/1] package/sedutil: fix build with gcc >= 13 Fabrice Fontaine
2023-11-01 10:52 ` Yann E. MORIN
2023-11-07 19:38   ` Peter Korsgaard [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=87bkc5wdzp.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=yann.morin.1998@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