You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noratrieb opened this issue
Mar 16, 2025
· 5 comments
Labels
C-bugCategory: This is a bug.O-trustyOperating system: trusty (https://doc.rust-lang.org/nightly/rustc/platform-support/trusty.html)T-libsRelevant to the library team, which will review and decide on the PR/issue.
Noratrieb
added
O-trusty
Operating system: trusty (https://doc.rust-lang.org/nightly/rustc/platform-support/trusty.html)
and removed
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
labels
Mar 16, 2025
I have been told that apparently trusty only very recently actually got std support, in that case it makes sense. It seems like Miri was just not aware about whether it actually supports it
Oh no, I'm very sorry about this! Trusty libstd support was just landed and I did not realize it was causing build breakage. I thought I had checked that it built and hadn't seen any of these errors, clearly my testing was missing some steps. Is it okay for me to address this issue tomorrow when I'm back in the office? If this is time sensitive I can try to address it now.
C-bugCategory: This is a bug.O-trustyOperating system: trusty (https://doc.rust-lang.org/nightly/rustc/platform-support/trusty.html)T-libsRelevant to the library team, which will review and decide on the PR/issue.
There are multiple build errors with trusty std.
Most recently it's an unsafe error:
https://does-it-build.noratrieb.dev/build?nightly=2025-03-16&target=x86_64-unknown-trusty&mode=miri-std
Before that thread locals didn't build:
https://does-it-build.noratrieb.dev/build?nightly=2025-02-24&target=x86_64-unknown-trusty&mode=miri-std
It's not worked at all in the past over a year:
https://does-it-build.noratrieb.dev/target?target=x86_64-unknown-trusty
If you're not interested in having std you can remove std, but this state is not great.
@randomPoison @ahomescu
The text was updated successfully, but these errors were encountered: