Skip to content
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

prjtrellis: don't force clang #10573

Merged
merged 1 commit into from
Jan 20, 2022
Merged

prjtrellis: don't force clang #10573

merged 1 commit into from
Jan 20, 2022

Conversation

umarcor
Copy link
Contributor

@umarcor umarcor commented Jan 18, 2022

According to #10547, and tested by several users, using GCC instead of clang does fix the issues with an early check introduced in mingw-w64-crt. This PR changes prjtrellis not to use clang on the default where GCC is the default.

/cc @Biswa96 @stnolting @sylefeb

@Biswa96
Copy link
Member

Biswa96 commented Jan 18, 2022

Just curious. Was there any reason to use clang in mingw or ucrt environment where gcc is default?

@umarcor
Copy link
Contributor Author

umarcor commented Jan 19, 2022

No particular reason other than IIRC the default guidelines upstream using clang. I changed the description now to use the default on each environment. I guess the issue (#10547) will remain on clang32 and clang64 only.

@umarcor umarcor changed the title prjtrellis: don't use clang, to temporarily work around #10547 prjtrellis: don't force clang Jan 19, 2022
@jeremyd2019
Copy link
Member

the issue was in the combination of clang with BFD ld. clang+lld should be fine, and is what clang* envs use.

@lazka lazka merged commit 58bb5ba into msys2:master Jan 20, 2022
@umarcor umarcor deleted the prjtrellis-gcc branch January 20, 2022 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants