-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The no_std targets seem hardcoded in bootstraping #97322
Comments
…std-build, r=jyn514 Don't build std for *-uefi targets rust-lang#97322
…std-build, r=jyn514 Don't build std for *-uefi targets rust-lang#97322
Note that you can avoid building [target.x86_64-unknown-uefi]
no-std = true This avoids relying on the hard-coded values in |
Closing it now since #99765 is already merged. |
I was trying to build
library/core
forx86_64-unknown-uefi
. However, it was trying to buildlibrary/test
and by extensionlibrary/std
for some reason. This is odd since the UEFI targets are no_std targets according to rust platform support. The error I was getting is as follows:Building for some other no_std targets such as
x86_64-unknown-none
works fine and only builds core, rustc-std-workspace-core, compiler_builtins and alloc.After some digging around, I found that this can be fixed by making the following changes
However, hardcoding no_std like this doesn't seem to be a good solution. Maybe #95503 will solve this but I don't really know. So just wanted to bring this to community's attention (unless everyone is already aware of this).
The text was updated successfully, but these errors were encountered: