From: cplir-c <cplir-c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Rust will drop support for musl before 1.2.3
Date: Tue, 25 Jun 2024 03:01:44 +0200 [thread overview]
Message-ID: <20240625010144.C02102600E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49700@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
New comment by cplir-c on void-packages repository
https://github.com/void-linux/void-packages/issues/49700#issuecomment-2187649133
Comment:
It seems to run on Voidlinux x86_64 musl now?
I force-reinstalled rustup; I'll update my system and test again.
`xbps-query -s musl` shows:
```xbps
[*] musl-1.1.24_20 Musl C library
[*] musl-devel-1.1.24_20 Musl C library - development files
[*] musl-fts-1.2.7_4 Implementation of fts(3) for musl libc
[*] musl-obstack-1.2.3_1 Implementation of obstack for musl libc
```
next prev parent reply other threads:[~2024-06-25 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 9:27 [ISSUE] " 22h49
2024-06-24 23:53 ` cplir-c
2024-06-25 1:01 ` cplir-c [this message]
2024-06-25 1:02 ` cplir-c
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=20240625010144.C02102600E@inbox.vuxu.org \
--to=cplir-c@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).