From: RoundDuckKira <RoundDuckKira@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Apple Silicon Mac support packages (v2)
Date: Mon, 22 Jan 2024 21:24:24 +0100 [thread overview]
Message-ID: <20240122202424.1CCB922D51@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39796@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
New comment by RoundDuckKira on void-packages repository
https://github.com/void-linux/void-packages/pull/39796#issuecomment-1904746488
Comment:
> I know rust-for-linux says 'single version' for now, but they also say 'generally speaking, newer versions should work, as long as one patches any potential compilation errors coming from changes in unstable features.' Maybe we are lucky and asahi have done that? What if we just add void's current rust to hostmakedepends? @RoundDuckKira Can you post a kconfig diff for enabling gpu stuff here? (The rest was working fine last time I checked, see first post.)
gonna have to figure out how to do the kconfig right, the one I used in my original project was directly copied from the Fedora config and well it didn't work too well by itself or even with oldconfig done to it, so gonna have to compile a kernel independently and see if it compiles right with a properly set kconfig, I'll use your peeps' kconfig.
next prev parent reply other threads:[~2024-01-22 20:24 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 18:46 [PR PATCH] " dkwo
2022-10-07 18:50 ` [PR PATCH] [Updated] " dkwo
2022-10-07 18:55 ` dkwo
2022-10-07 20:32 ` dkwo
2022-10-07 20:45 ` Skirmisher
2022-10-07 22:02 ` dkwo
2022-10-13 20:15 ` [PR PATCH] [Updated] " dkwo
2022-10-13 20:20 ` dkwo
2022-10-13 20:31 ` [PR PATCH] [Updated] " dkwo
2022-10-14 18:53 ` dkwo
2022-10-24 22:35 ` dkwo
2022-10-24 22:43 ` dkwo
2022-10-24 22:44 ` dkwo
2022-10-26 16:08 ` dkwo
2022-10-27 15:43 ` dkwo
2022-10-27 15:45 ` dkwo
2022-10-27 15:47 ` dkwo
2022-11-03 17:58 ` dkwo
2022-11-03 18:06 ` dkwo
2022-11-17 21:11 ` [PR PATCH] [Updated] " dkwo
2022-12-01 19:52 ` dkwo
2022-12-01 20:05 ` dkwo
2022-12-01 21:28 ` [PR PATCH] [Updated] " dkwo
2022-12-06 19:13 ` dkwo
2022-12-17 9:55 ` Anachron
2022-12-17 9:56 ` Anachron
2022-12-17 9:56 ` Anachron
2022-12-17 10:00 ` Anachron
2022-12-17 10:01 ` Anachron
2022-12-17 11:47 ` Skirmisher
2022-12-17 14:31 ` dkwo
2023-04-10 18:52 ` [PR PATCH] [Updated] " dkwo
2023-04-10 18:55 ` dkwo
2023-04-11 20:27 ` dkwo
2023-04-11 20:42 ` dkwo
2023-04-11 22:02 ` dkwo
2023-04-11 22:06 ` dkwo
2023-04-12 22:36 ` dkwo
2023-04-12 22:42 ` [PR PATCH] [Updated] " dkwo
2023-04-13 15:23 ` dkwo
2023-04-13 21:40 ` dkwo
2023-04-13 21:45 ` dkwo
2023-04-13 22:04 ` dkwo
2023-04-13 22:05 ` [PR PATCH] [Updated] " dkwo
2023-05-30 21:02 ` dkwo
2023-06-09 0:25 ` dkwo
2023-06-10 22:51 ` dkwo
2023-06-22 22:33 ` dkwo
2023-09-21 1:44 ` github-actions
2023-09-21 12:24 ` jcgruenhage
2023-09-21 16:06 ` dkwo
2023-09-26 14:01 ` [PR PATCH] [Updated] " dkwo
2023-10-02 16:20 ` dkwo
2023-10-29 14:11 ` [PR PATCH] [Updated] " dkwo
2023-12-02 23:37 ` dkwo
2023-12-03 19:08 ` dkwo
2023-12-04 20:35 ` dkwo
2023-12-11 16:15 ` [PR PATCH] [Updated] " dkwo
2024-01-22 12:57 ` RoundDuckKira
2024-01-22 13:03 ` RoundDuckKira
2024-01-22 16:05 ` dkwo
2024-01-22 17:28 ` [PR PATCH] [Updated] " dkwo
2024-01-22 19:25 ` dkwo
2024-01-22 20:24 ` RoundDuckKira [this message]
2024-01-22 20:25 ` RoundDuckKira
2024-01-24 11:41 ` RoundDuckKira
2024-01-24 11:42 ` RoundDuckKira
2024-01-24 15:08 ` dkwo
2024-01-25 2:49 ` RoundDuckKira
2024-01-25 2:50 ` RoundDuckKira
2024-01-25 15:58 ` dkwo
2024-01-25 22:21 ` dkwo
2024-01-30 4:37 ` RoundDuckKira
2024-01-30 4:38 ` RoundDuckKira
2024-01-30 16:35 ` dkwo
2024-02-20 19:50 ` dkwo
2024-03-31 14:32 ` [PR PATCH] [Updated] " dkwo
2024-04-23 20:29 ` dkwo
2024-04-24 19:36 ` [PR PATCH] [Updated] " dkwo
2024-04-25 14:21 ` 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=20240122202424.1CCB922D51@inbox.vuxu.org \
--to=roundduckkira@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).