From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zynaddsubfx: fix uclibc compile error
Date: Sun, 10 Sep 2023 14:00:24 +0200 [thread overview]
Message-ID: <20230910140024.74a2e625@windsurf> (raw)
In-Reply-To: <1214dd8573105f0075de5019938a5d37@free.fr>
Hello,
On Sat, 09 Sep 2023 23:07:19 +0200
Julien Olivain <ju.o@free.fr> wrote:
> This build failure is the first of its kind, according to autobuild:
> http://autobuild.buildroot.net/?reason=zynaddsubfx-3.0.6
>
> Looking at the upstream code, this header inclusion is missing, so the
> bug has always been there. My guess is that this "stdint.h" header was
> included indirectly from the libc internally. I did not investigated
> further. Do you want me to?
It seems like it is related to gcc 13.x, and that the right thing would
be to include <cstdint>. See commit
27dc49378071a82688d44a5cc592c0200b3991b4 for an example of something
similar. So you could try to build (without your patch) using gcc 12.x
and gcc 13.x and see if that's the difference that causes the build
failure.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-10 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 10:47 [Buildroot] [PATCH 1/1] package/zynaddsubfx: fix uclibc compile error Julien Olivain
2023-09-09 15:08 ` Thomas Petazzoni via buildroot
2023-09-09 21:07 ` Julien Olivain
2023-09-10 12:00 ` Thomas Petazzoni via buildroot [this message]
2023-09-10 13:10 ` Julien Olivain
2023-09-10 13:48 ` Thomas Petazzoni 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=20230910140024.74a2e625@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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