From: flyxi121 <flyxi121@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Rust 1.54.0
Date: Wed, 15 Dec 2021 16:11:50 +0100 [thread overview]
Message-ID: <20211215151150.kF5s7NrjqxM1WcWhuG89-J9cIxw4TPS2kfNAb0_Rg48@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32555@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
New comment by flyxi121 on void-packages repository
https://github.com/void-linux/void-packages/pull/32555#issuecomment-994886339
Comment:
Sorry that I was not active for the last week, I had a lot to do for university...
After trying around with the alpine patches, I came to the same conclusion as @ericonr - it messes up all target names. Especially because void linux does not only have musl targets, but also glibc targets. The target names would be inconsistent and confusing for people who are not familiar with alpine linux.
I have also tried building rust without extra build targets (reusing some of void's patches and some of the other alpine patches) and everything seems to work (at least on x86_64-musl), except the fulldep tests. These tests fail, because for some reason rust finds two libc crates.
Considering that neither alpine linux nor arch linux (I chose those 2 linux distributions as they have the newest rust version available and I am familiar with them) even run the tests, I do not even know whether rustc would pass all the tests on these distributions or if they would fail as well.
If anyone has had the same problem and knows how to fix it I would also kindly appreciate it.
next prev parent reply other threads:[~2021-12-15 15:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 21:13 [PR PATCH] " ericonr
2021-08-18 1:18 ` ericonr
2021-08-18 21:54 ` ifreund
2021-08-18 21:54 ` ifreund
2021-08-19 2:47 ` [PR PATCH] [Updated] " ericonr
2021-08-19 5:31 ` ericonr
2021-09-17 14:18 ` ram02z
2021-09-17 23:01 ` cinerea0
2021-10-04 1:53 ` uninhm
2021-10-14 17:51 ` cinerea0
2021-10-21 17:49 ` cinerea0
2021-10-21 17:57 ` cinerea0
2021-10-22 1:38 ` cinerea0
2021-10-30 5:14 ` cinerea0
2021-11-01 5:39 ` cinerea0
2021-11-02 5:27 ` ericonr
2021-11-04 3:59 ` cinerea0
2021-11-11 2:26 ` cinerea0
2021-11-14 8:04 ` kartikynwa
2021-11-23 23:29 ` cinerea0
2021-12-03 3:33 ` cinerea0
2021-12-06 1:11 ` flyxi121
2021-12-06 1:55 ` ericonr
2021-12-06 23:06 ` flyxi121
2021-12-07 17:52 ` flyxi121
2021-12-07 18:49 ` flyxi121
2021-12-07 19:03 ` ericonr
2021-12-07 19:03 ` [PR PATCH] [Updated] " ericonr
2021-12-07 19:12 ` flyxi121
2021-12-07 19:16 ` flyxi121
2021-12-08 1:24 ` flyxi121
2021-12-13 18:46 ` leahneukirchen
2021-12-14 3:35 ` ericonr
2021-12-15 15:11 ` flyxi121 [this message]
2021-12-19 4:17 ` ericonr
2021-12-20 3:54 ` [PR PATCH] [Updated] " ericonr
2021-12-20 3:55 ` Rust 1.57.0 ericonr
2021-12-22 19:51 ` cinerea0
2022-01-02 19:11 ` cinerea0
2022-01-04 15:52 ` [PR PATCH] [Closed]: " q66
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=20211215151150.kF5s7NrjqxM1WcWhuG89-J9cIxw4TPS2kfNAb0_Rg48@z \
--to=flyxi121@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).