From: Edgar Bonet <bonet@grenoble.cnrs.fr>
To: buildroot@buildroot.org
Subject: [Buildroot] Support external toolchains based on gcc 14
Date: Thu, 16 May 2024 17:56:41 +0200 [thread overview]
Message-ID: <c79c79fb-8692-40c5-8436-25213b54102a@grenoble.cnrs.fr> (raw)
Hello all!
Last July, right before support for gcc 13 was added for buildroot's
internal toolchain in 3009095ba8 (package/gcc: add support for gcc 13),
the support was added for the external toolchain in dfbd1aae23
(toolchain/toolchain-external/toolchain-external-custom: add gcc 13
version selection).
Last week, support for gcc 14 has been added for the internal toolchain
in 5eb0203cb0 (package/gcc: add version 14.x), but this is still lacking
for the external toolchain. Is this an oversight? Should I just wait?
Should I instead submit a patch equivalent to dfbd1aae23 for gcc 14?
Regards,
Edgar.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-05-16 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 15:56 Edgar Bonet [this message]
2024-05-17 7:06 ` [Buildroot] Support external toolchains based on gcc 14 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=c79c79fb-8692-40c5-8436-25213b54102a@grenoble.cnrs.fr \
--to=bonet@grenoble.cnrs.fr \
--cc=buildroot@buildroot.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).