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
This is a workaround for a previous problem with Darwin target support.
Note that when using the -mtriple flag, except for Darwin targets, ldc2 does not set the -target flag to CC.
Thus, zig cc will assume that the target is native (which is the default), and will not recognize a specific triple-target.
Likewise, looking at ldc2 internally, it appears that, like rustc, it calls the CC (like arm-none-eabi-gcc) of the selected target.
# rustc - arm64/macos
error: unable to run `dsymutil`: No such file or directory (os error 2)
# rustc - arm64/windows
error: toolchain 'nightly-x86_64-unknown-linux-gnu' does not support target 'aarch64-pc-windows-gnu'
note: you can see a list of supported targets with `rustc --print=target-list`
note: if you are adding support for a new target to rustc itself, see https://rustc-dev-guide.rust-lang.org/building/new-target.html
install
+- hellors
+- rustup failure
error: the following command exited with error code 1:
/home/runner/.cargo/bin/rustup target add aarch64-pc-windows-gnu
Rust-std not have mipsel and riscv64gc-musl support!
@import("builtin")
get only native target.tested in ldc2-druntime/gist
This is a workaround for a previous problem with Darwin target support.
Note that when using the
-mtriple
flag, except for Darwin targets, ldc2 does not set the-target
flag toCC
.Thus, zig cc will assume that the target is native (which is the default), and will not recognize a specific triple-target.
Likewise, looking at ldc2 internally, it appears that, like rustc, it calls the
CC
(likearm-none-eabi-gcc
) of the selected target.Reference
The text was updated successfully, but these errors were encountered: