All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: buildroot@buildroot.org, thomas.petazzoni@bootlin.com,
	romain.naour@smile.fr, romain.naour@gmail.com,
	ibai.erkiaga-elorza@amd.com
Subject: Re: [Buildroot] [PATCH v2 1/1] package/gcc-bare-metal: decouple from gcc package
Date: Wed, 24 Sep 2025 22:53:45 +0200	[thread overview]
Message-ID: <e5679f7f728970d4ffb3291be7936277@free.fr> (raw)
In-Reply-To: <20250818044755.3155924-1-neal.frager@amd.com>

On 18/08/2025 06:47, Neal Frager via buildroot wrote:
> This patch decouples the gcc-bare-metal package from the gcc package to 
> avoid
> potential build issues when bumping the version of one package before 
> the
> other.
> 
> Such as the build issue example here:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/11026775160
> 
> Since the gcc-bare-metal package does not currently require the gcc 
> 15.2.0
> downstream patches, this patch simply deletes the link for patching
> gcc-bare-metal 15.2.0 with patches that are not needed for bare-metal 
> apps.
> 
> As for the hash link, this patch creates a new file called 
> gcc-bare-metal.hash
> which has the same hashes in the gcc.hash file.  But by having its own 
> hash
> file, hashes from the gcc package can be removed when version bumping 
> without
> causing build errors for the gcc-bare-metal package.
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-09-24 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  4:47 [Buildroot] [PATCH v2 1/1] package/gcc-bare-metal: decouple from gcc package Neal Frager via buildroot
2025-09-24 20:53 ` Julien Olivain 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=e5679f7f728970d4ffb3291be7936277@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=ju.o@free.fr \
    --cc=neal.frager@amd.com \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.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 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.