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
Looks like when we invoke cargo, if RUSTC=rustc, it looks up the rustc binary next to it directly, but if RUSTC=x86_64-linux-musl-rustc (as it is set here) it ends up looping back through the wrapper and accidentally adding --target twice.
We should:
Not use := in that common.mk, but instead use ?= to properly inherit whatever is being set by the BB environment
Fix our rust wrapper to have a check to ensure that if --target is set, it is the correct one, and if so don't add --target. If it's set and is not the correct one, it should error. And of course if it is not set, it should continue to set --target.
On
master
(tests in #138 reproduce the failure):With #137:
The text was updated successfully, but these errors were encountered: