From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Bump cross-arm-none-eabi gcc and binutils to match non-cross packages
Date: Wed, 05 Oct 2022 20:04:32 +0200 [thread overview]
Message-ID: <20221005180432.TPd3cL05_tfdxBltievXLHy0igdo-AaXdYvEaVVlKNc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37580@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/37580#issuecomment-1268764275
Comment:
Copying @oreo639's response from `#xbps`:
> The cross-*-linux packages are dependant on the regular gcc/binutils/libc packages and pull patches from them, meaning that they have to be kept in sync (not to mention not updating them would cause inconsistent behavior in the builders when cross compiling vs native compiling).
>
> This isn't the case with cross-arm-none-eabi which is its own thing (generic newlib gcc compiler), meaning it makes more sense for it to be updated seperately. (preferably by someone who actually does embedded stuff and uses it)
next prev parent reply other threads:[~2022-10-05 18:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 1:38 [PR PATCH] " via
2022-06-18 13:50 ` [PR PATCH] [Updated] " via
2022-09-17 2:14 ` github-actions
2022-10-01 2:16 ` [PR PATCH] [Closed]: " github-actions
2022-10-01 9:06 ` JamiKettunen
2022-10-01 9:06 ` JamiKettunen
2022-10-05 18:04 ` JamiKettunen [this message]
2022-10-05 18:10 ` via
2022-10-05 18:14 ` paper42
2022-10-05 18:30 ` JamiKettunen
2022-10-05 18:31 ` JamiKettunen
2022-10-05 18:31 ` JamiKettunen
2022-10-13 2:26 ` [PR REVIEW] " wryun
2023-01-11 2:30 ` github-actions
2023-01-26 1:59 ` [PR PATCH] [Closed]: " github-actions
2023-10-26 15:36 ` riddicc
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=20221005180432.TPd3cL05_tfdxBltievXLHy0igdo-AaXdYvEaVVlKNc@z \
--to=jamikettunen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).