From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: Julien Olivain <ju.o@free.fr>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
"Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/gcc-bare-metal: bump to version 15.2.0 to fix build
Date: Fri, 15 Aug 2025 20:42:34 +0200 [thread overview]
Message-ID: <20250815204234.695f6fe0@windsurf> (raw)
In-Reply-To: <SA1PR12MB5615109970A6666176138370F034A@SA1PR12MB5615.namprd12.prod.outlook.com>
On Fri, 15 Aug 2025 18:38:59 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> At the moment, gcc-bare-metal does not need any of the 3 gcc 15 patches.
>
> We could just delete the patches symlink and cherry pick
> any gcc patches we might actually need in the future.
>
> Then we would truly disconnect any dependencies between the
> gcc and gcc-bare-metal packages.
That would be fine by me, especially as they don't _need_ to be
connected. In other cases, we really need to have the same version,
like package/glibc and package/localedef, so it makes sense to share
hash file and stuff. But between gcc-{final,initial} and
gcc-bare-metal, there's really no relationship whatsoever.
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:[~2025-08-15 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 15:27 [Buildroot] [PATCH 1/1] package/gcc-bare-metal: bump to version 15.2.0 to fix build Julien Olivain via buildroot
2025-08-15 15:30 ` Thomas Petazzoni via buildroot
2025-08-15 17:02 ` Frager, Neal via buildroot
2025-08-15 17:11 ` Frager, Neal via buildroot
2025-08-15 18:29 ` Thomas Petazzoni via buildroot
2025-08-15 18:38 ` Frager, Neal via buildroot
2025-08-15 18:42 ` Thomas Petazzoni via buildroot [this message]
2025-08-15 19:04 ` Frager, Neal via buildroot
2025-08-16 19:39 ` 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=20250815204234.695f6fe0@windsurf \
--to=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=neal.frager@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.