From: tjkirch <tjkirch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rust-analyzer: update to 2022.01.03.
Date: Wed, 05 Jan 2022 19:40:50 +0100 [thread overview]
Message-ID: <20220105184050.53VgkPQ0TgQrBtwI6_YSOzsPeJYrPsEXYwf5kiqaTz0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34856@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
New comment by tjkirch on void-packages repository
https://github.com/void-linux/void-packages/pull/34856#issuecomment-1005983260
Comment:
The CI checks on ARM* failed because compiling a dependency, [indexmap](https://docs.rs/indexmap/latest/indexmap/index.html), failed because of a missing generic parameter for types like [IndexSet](https://docs.rs/indexmap/latest/indexmap/set/struct.IndexSet.html). The [code](https://docs.rs/indexmap/1.7.0/src/indexmap/set.rs.html#63-69) shows that there's a default value for that parameter, but only if Rust `has_std`.
I see that other Rust-based PRs like [ncspot](https://github.com/void-linux/void-packages/pull/33600) are failing for the same arches; I can't see the error details, but someone linked to [this issue](https://github.com/librespot-org/librespot/issues/774) which sounds very much the same.
The last rust-analyzer PR checked fine, and rust-analyzer doesn't seem to have changed arch support; they still have an official aarch64 build. I wonder if Void's recent [Rust update](https://github.com/void-linux/void-packages/pull/32555) changed something that might be related... Maybe @q66 has context since they did the update?
next prev parent reply other threads:[~2022-01-05 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 22:31 [PR PATCH] " tjkirch
2022-01-05 18:40 ` tjkirch [this message]
2022-01-05 19:03 ` ericonr
2022-01-05 19:22 ` tjkirch
2022-01-05 19:23 ` ericonr
2022-01-05 19:23 ` ericonr
2022-01-17 19:42 ` tjkirch
2022-01-17 23:56 ` ericonr
2022-01-18 0:04 ` tjkirch
2022-02-27 12:13 ` tranzystorek-io
2022-02-27 19:01 ` tjkirch
2022-04-05 2:32 ` Goorzhel
2022-06-15 21:18 ` classabbyamp
2022-06-15 21:18 ` [PR PATCH] [Closed]: " classabbyamp
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=20220105184050.53VgkPQ0TgQrBtwI6_YSOzsPeJYrPsEXYwf5kiqaTz0@z \
--to=tjkirch@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).