Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

package mingw-w64-clang-x86_64-rust should target to x86_64-pc-windows-gnullvm #13388

Closed
ArchGuyWu opened this issue Oct 4, 2022 · 3 comments

Comments

@ArchGuyWu
Copy link
Contributor

As there's only llvm-based toolchain in ucrt64 repo ,the target x86_64-pc-windows-gnu is not the proper one ,and it doesn't work even with package mingw-w64-clang-x86_64-gcc-compat installed.

@1480c1
Copy link
Contributor

1480c1 commented Oct 4, 2022

https://doc.rust-lang.org/rustc/platform-support/pc-windows-gnullvm.html

should probably ping @mati865 for his opinion

@jeremyd2019
Copy link
Member

I think that's being worked on, #13278 is related

@mati865
Copy link
Collaborator

mati865 commented Oct 4, 2022

As there's only llvm-based toolchain in ucrt64 repo

UCRT64 repo is GCC/Binutils based, CLANG64 is LLVM based.

the target x86_64-pc-windows-gnu is not the proper one ,and it doesn't work

It works fine because of hacks, we have compiled multiple packages with it: https://packages.msys2.org/package/mingw-w64-clang-x86_64-rust

mingw-w64-clang-x86_64-rust should target to x86_64-pc-windows-gnullvm

That is long-term goal but:

  1. Getting it to build with pacman under MSYS2 has been troublesome and so far it's even more hacky than using regular *-pc-windows-gnu triples.
  2. Ecosystem is not ready yet. Because of the dependencies, migrating right now would break building half of the packages (or more) that we already build with Rust for CLANG64.

@msys2 msys2 locked and limited conversation to collaborators Jun 6, 2023
@jeremyd2019 jeremyd2019 converted this issue into discussion #17466 Jun 6, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants