From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [WIP] riscv64-musl port
Date: Sat, 17 Sep 2022 04:13:57 +0200 [thread overview]
Message-ID: <20220917021357.7fLV_3WsltaqiczsZuz3KBGLLX_K8-1Yp9-MSz4j00k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13207@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
There's a closed pull request on the void-packages repository
[WIP] riscv64-musl port
https://github.com/void-linux/void-packages/pull/13207
Description:
This is the beginning of a port of Void to riscv64-musl.
musl supports RISC-V as of 1.1.23.
- [x] base-devel
- [x] base-system
- [x] chroot tested on Fedora in QEMU
- [ ] linux5.2
- [ ] running directly on QEMU
- [ ] running on hardware (I don't have any...)
Feel free to contribute! Having access to a bulk build would be very helpful (Debian has ~10% fallout).
next prev parent reply other threads:[~2022-09-17 2:13 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 11:37 [PR PATCH] " voidlinux-github
2019-07-19 13:35 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-19 13:35 ` voidlinux-github
2019-07-26 21:56 ` voidlinux-github
2019-07-27 12:58 ` voidlinux-github
2019-07-27 14:56 ` voidlinux-github
2019-07-27 15:32 ` voidlinux-github
2020-12-30 18:20 ` leahneukirchen
2020-12-31 9:26 ` Anachron
2020-12-31 9:26 ` Anachron
2021-01-03 13:35 ` advancedwebdeveloper
2021-01-15 2:56 ` HadetTheUndying
2021-06-23 7:09 ` dkwo
2022-01-14 7:05 ` jcgruenhage
2022-01-14 16:43 ` leahneukirchen
2022-03-03 6:18 ` jailbird777
2022-03-04 19:24 ` leahneukirchen
2022-03-04 22:23 ` jailbird777
2022-03-04 22:50 ` leahneukirchen
2022-06-03 2:10 ` github-actions
2022-09-02 2:15 ` github-actions
2022-09-17 2:13 ` github-actions [this message]
2023-01-08 19:38 ` JamiKettunen
2023-01-14 18:26 ` leahneukirchen
2023-01-15 0:21 ` Johnnynator
2023-01-15 13:35 ` Anachron
2023-01-15 15:06 ` Johnnynator
2023-05-27 16:38 ` blacklightpy
2023-08-25 19:27 ` Anachron
2023-08-25 19:42 ` RoozbehOssia
2023-08-26 12:46 ` leahneukirchen
2023-08-26 14:36 ` [PR PATCH] [Updated] " leahneukirchen
2023-08-29 20:30 ` Anachron
2023-08-29 20:33 ` leahneukirchen
2023-08-29 21:14 ` leahneukirchen
2023-08-30 7:44 ` sug0
2023-09-03 12:10 ` blacklightpy
2023-09-03 12:16 ` blacklightpy
2023-09-03 12:21 ` blacklightpy
2023-09-03 12:50 ` blacklightpy
2023-10-10 13:35 ` Piraty
2023-10-18 21:43 ` RoozbehOssia
2024-01-17 1:46 ` github-actions
2024-01-17 3:54 ` fvalasiad
2024-02-21 10:25 ` dataCobra
2024-02-21 10:53 ` blacklightpy
2024-02-21 10:53 ` blacklightpy
2024-02-21 11:38 ` dataCobra
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=20220917021357.7fLV_3WsltaqiczsZuz3KBGLLX_K8-1Yp9-MSz4j00k@z \
--to=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).