From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] musl update
Date: Sun, 21 Mar 2021 13:34:17 +0100 [thread overview]
Message-ID: <20210321123417.X-a087-O_7UsOg3bjEOwNA0i3YpT5YfWFNOHRA_Zxis@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29632@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
New comment by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/issues/29632#issuecomment-803570520
Comment:
Somehow we've managed to rebuild the whole world for new glibc. How's musl different in this aspect? Also AFAIK there's no i686-musl variant, so i686 is out of scope of the question.
On March 21, 2021 3:05:17 PM GMT+03:00, "Đoàn Trần Công Danh" ***@***.***> wrote:
>On 2021-03-21 04:54:52-0700, Artur Sinila ***@***.***> wrote:
>> What about musl update though? It's been half a year since 1.2 was
>> released, yet we are still on 1.1. Alpine somehow managed to update,
>> what are the blocking issues for Void?
>
>Rebuild the whole world for 32-bit architecture.
>And force update the whole world.
>
>For that, we need to add more feature to xbps.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2021-03-21 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 16:58 [ISSUE] " dkwo
2021-03-20 18:54 ` abenson
2021-03-20 22:19 ` dkwo
2021-03-20 23:10 ` Johnnynator
2021-03-21 11:54 ` Logarithmus
2021-03-21 11:55 ` Logarithmus
2021-03-21 12:05 ` sgn
2021-03-21 12:34 ` Logarithmus [this message]
2021-03-21 12:46 ` Duncaen
2021-03-21 12:47 ` Duncaen
2021-03-22 1:03 ` ericonr
2021-03-22 1:03 ` [ISSUE] [CLOSED] " ericonr
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=20210321123417.X-a087-O_7UsOg3bjEOwNA0i3YpT5YfWFNOHRA_Zxis@z \
--to=logarithmus@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).