-
Notifications
You must be signed in to change notification settings - Fork 552
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
-Xarch
Clang compiler option not supported
#2090
Comments
Same for me... Is there a resolution for this? |
- workaround for sccache issue: mozilla/sccache#2090
+1. I also am facing this issue with sccache on Mac OS X. |
Don't hesitate to propose a patch for this. AFAIK, we (Mozilla) aren't impacted by this. |
I believe a patch wasn't proposed due to the issue mentioned, "obviously this isn't sustainable long-term, since it should actually parse 2 arguments from the option (arg1 and arg2) which doesn't seem to be possible right now." |
A new ArgDisposition is introduces that combines the Concatenated and Separated behaviors, but produces results similar to a plain Separated argument with the full original -Xarch_<arch> argument. Fixes mozilla#2090
I made a stab at a more generic fix in #2265 @sylvestre please have a look, thanks! |
A new ArgDisposition is introduces that combines the Concatenated and Separated behaviors, but produces results similar to a plain Separated argument with the full original -Xarch_<arch> argument. Fixes mozilla#2090
A new ArgDisposition is introduces that combines the Concatenated and Separated behaviors, but produces results similar to a plain Separated argument with the full original -Xarch_<arch> argument. Fixes mozilla#2090
I'm not sure what the exact conditions are, but CMake (sometimes?) generates
-Xarch_<arch>
before architecture-specific PCH includes with (both LLVM and Apple) Clang on macOS. The option's syntax is kind of weird (-Xarch_<arg1> <arg2>
Clang CLI ref) and it not being properly supported results in arguments getting reordered weirdly causing the following errors:I managed to work around the issue for my specific use case in this commit, but obviously this isn't sustainable long-term, since it should actually parse 2 arguments from the option (
arg1
andarg2
) which doesn't seem to be possible right now.The text was updated successfully, but these errors were encountered: