-
Notifications
You must be signed in to change notification settings - Fork 381
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
build-std is not passing to cargo if falling back to host #1590
Comments
I'm not sure if this is is what should happen or not. Could you explain why this is a problem? |
As a user, I would expect that when I run Parameters that are passing from command line arguments will apply to builds that are running in both container and host. It should be consistent for parameters in |
But this is an error, the error being that you've not setup cross correctly. This will eventually become a hard error without a fallback. |
Em, Ok. If there will be no fallback, it is Ok. But if there is a fallback, behavior should be kept consistent. |
Checklist
Describe your issue
I was trying to build for target
mips-unknown-linux-musl
withcross
with latest master. Build withCross.toml
setting:But no
-Zbuild-std=std,panic_abort,proc_macro
in the final command line.What target(s) are you cross-compiling for?
mips-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?
What architecture is the host?
What container engine is cross using?
cross version
cross 0.2.5 (4090bec 2024-10-15)
Example
Additional information / notes
No response
The text was updated successfully, but these errors were encountered: