From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: musl
Date: Fri, 27 Jan 2023 19:29:53 +0100 [thread overview]
Message-ID: <20230127182953.xKigecaGgQDQAeFwkgW6BuGsXxdWJyiURAJBOn6p80Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41295@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/41295#issuecomment-1406921964
Comment:
@CameronNemo I've built this natively on aarhc64. I'm not going to rebuild the whole world for now, but if there's a few packages that you want to test, let me know.
@nekopsykose Those packages I mentioned need rebuild also on 64 (e.g. O_LARGEFILE, sandbox issues).
@paper42 Instead of waiting forever for abi support, wouldn't it be more practical to rebuild everything for all archs? you may have a week or two of freezing, but at least from my user perspective that's much better than the current situation.
next prev parent reply other threads:[~2023-01-27 18:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 6:05 [PR PATCH] musl CameronNemo
2022-12-26 15:45 ` musl JamiKettunen
2022-12-26 19:33 ` musl CameronNemo
2022-12-26 21:51 ` musl oreo639
2022-12-26 21:53 ` musl oreo639
2022-12-26 21:53 ` musl oreo639
2022-12-26 21:53 ` musl oreo639
2022-12-26 21:54 ` musl oreo639
2022-12-26 21:56 ` musl oreo639
2022-12-27 17:22 ` musl dkwo
2022-12-27 17:33 ` musl CameronNemo
2022-12-27 17:36 ` musl nekopsykose
2022-12-27 17:39 ` musl paper42
2022-12-27 17:57 ` musl dkwo
2022-12-27 17:58 ` musl dkwo
2023-01-27 18:29 ` musl dkwo
2023-01-27 18:29 ` dkwo [this message]
2023-01-27 20:12 ` musl CameronNemo
2023-01-28 15:56 ` musl dkwo
2023-03-15 17:50 ` musl dkwo
2023-03-20 16:10 ` [PR PATCH] [Closed]: musl CameronNemo
2023-03-20 16:10 ` musl CameronNemo
2023-03-29 19:35 [PR PATCH] musl dkwo
2023-03-29 19:36 ` musl dkwo
2023-03-29 20:04 ` musl dkwo
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=20230127182953.xKigecaGgQDQAeFwkgW6BuGsXxdWJyiURAJBOn6p80Y@z \
--to=dkwo@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).