From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ccache: fix build with gcc 12.3
Date: Sun, 6 Aug 2023 14:25:33 +0200 [thread overview]
Message-ID: <20230806142533.57f53a29@windsurf> (raw)
In-Reply-To: <20230801215958.1751367-1-bernd@kuhls.net>
Hello Bernd,
On Tue, 1 Aug 2023 23:59:58 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes:
> http://autobuild.buildroot.net/results/cd3/cd341365d1c429bfca505a742e86b3090897db23/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> ...-fix-Work-around-GCC-12.3-bug-109241.patch | 29 +++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 package/ccache/0001-fix-Work-around-GCC-12.3-bug-109241.patch
You forgot to explain in the commit message when this issue started
occurring. So I've added an explanation in the commit message:
https://gitlab.com/buildroot.org/buildroot/-/commit/e34063c5be6963cb3fd87e6852af0854ec1c2dc1
It would be *really* nice if you could do something like this on a
systematic fashion.
Applied to master with this change, of course.
Thanks a lot!
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-08-06 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 21:59 [Buildroot] [PATCH 1/1] package/ccache: fix build with gcc 12.3 Bernd Kuhls
2023-08-06 12:25 ` 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=20230806142533.57f53a29@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--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