From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>,
Brandon Maier <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH] package/gcc: add patch to fix gcc 11 build warning
Date: Sat, 11 May 2024 08:57:02 +0200 [thread overview]
Message-ID: <20240511085702.28b11e6b@windsurf> (raw)
In-Reply-To: <20240510220704.1924373-1-brandon.maier@collins.com>
On Fri, 10 May 2024 22:07:04 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
> When building GCC 11 with GCC 14 the following error occurs
>
> > ../../../libiberty/simple-object-mach-o.c:1231:17: error: passing argument 1 of 'set_32' from incompatible pointer type [-Wincompatible-pointer-types]
>
> This was fixed upstream in GCC12[1]. It is applied to the GCC 11 release
> branch[2], but has not been officially released yet.
>
> [1] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=38757aa88735ab2e511bc428e2407a5a5e9fa0be
> [2] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=02cd761eb1198df50453b2e39653f48053609ffc
>
> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
> ---
> ...libiberty-Darwin-Fix-a-build-warning.patch | 37 +++++++++++++++++++
> 1 file changed, 37 insertions(+)
> create mode 100644 package/gcc/11.4.0/0009-libiberty-Darwin-Fix-a-build-warning.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:[~2024-05-11 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 22:07 [Buildroot] [PATCH] package/gcc: add patch to fix gcc 11 build warning Brandon Maier via buildroot
2024-05-11 6:57 ` Thomas Petazzoni via buildroot [this message]
2024-06-08 7:44 ` 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=20240511085702.28b11e6b@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@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