From: Peter Korsgaard <peter@korsgaard.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/zynaddsubfx: fix build with gcc 13
Date: Fri, 15 Sep 2023 19:41:18 +0200 [thread overview]
Message-ID: <875y4buyf5.fsf@48ers.dk> (raw)
In-Reply-To: <20230910142739.555507-1-ju.o@free.fr> (Julien Olivain's message of "Sun, 10 Sep 2023 16:27:39 +0200")
>>>>> "Julien" == Julien Olivain <ju.o@free.fr> writes:
> When compiling with gcc 13, build fails with errors, such as:
> In file included from /build/zynaddsubfx-3.0.6/src/Nio/NulEngine.h:21,
> from /build/zynaddsubfx-3.0.6/src/Nio/NulEngine.cpp:14:
> /build/zynaddsubfx-3.0.6/src/Nio/MidiIn.h:37:9: error: 'uint8_t' does not name a type
> 37 | uint8_t midiSysEx(unsigned char data);
> | ^~~~~~~
> Those gcc 13 changes were announced at:
> https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
> This commit fixes the issue by adding upstream patches, not yet
> included in a release.
> Fixes:
> http://autobuild.buildroot.net/results/97b5a30c7be820ac91e745cf60f9b759e962aa5c
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Changes v1 -> v2:
> - Reworded the commit log to correct the root cause of the issue
> (v1 was mentioning uclibc. it is in fact gcc-13)
Committed to 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-15 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 14:27 [Buildroot] [PATCH v2 1/1] package/zynaddsubfx: fix build with gcc 13 Julien Olivain
2023-09-10 16:36 ` Thomas Petazzoni via buildroot
2023-09-15 17:41 ` 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=875y4buyf5.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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