From: Peter Korsgaard <peter@korsgaard.com>
To: Javi Merino <merino.jav@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [infra] Missing tarball on sources.buildroot.net: gcc-14.2.0.tar.xz
Date: Sun, 27 Sep 2026 00:14:29 +0200 [thread overview]
Message-ID: <875wzr4q4a.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <aqrtmYhvhag_najL@einstein> (Javi Merino's message of "Wed, 16 Sep 2026 20:29:04 +0100")
>>>>> "Javi" == Javi Merino <merino.jav@gmail.com> writes:
> Hi,
> It appears that the tarball for gcc 14.2.0 (gcc-14.2.0.tar.xz) is missing from sources.buildroot.net.
> Could someone please trigger a sync or upload the archive to sources.buildroot.net when you get a chance?
Done, thanks for the heads up. I believe the reason why it never got
archived is that we never had a Buildroot version defaulting to gcc 14.x
while 14.2.0 was used (and the mirroring logic has issues with "choice"
selections).
With that said, you must be using a quite old Buildroot version to use
gcc 14.2.0 as we moved to 14.3.0 back in May 2025 with:
commit e9227311d9a63c9a829316e2ffb91cb70ed127f1
Author: Kadambini Nema <kadambini.nema@gmail.com>
Date: Fri May 30 17:22:16 2025 -0700
package/gcc: update to 14.3.0
So consider upgrading to a supported Buildroot version.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-26 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 19:29 [Buildroot] [infra] Missing tarball on sources.buildroot.net: gcc-14.2.0.tar.xz Javi Merino
2026-09-26 22:14 ` Peter Korsgaard [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=875wzr4q4a.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=merino.jav@gmail.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