-
-
Notifications
You must be signed in to change notification settings - Fork 12.8k
LLVM / Clang system config file setting breaks with -no-canonical-prefixes
#220757
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
Comments
homebrew
and config path is defined by relatively.
When the path is simplified,
and
the config path is now wrong. |
I'd suggest laying out the configuration |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Not sure why this is stale -- this is a continuing issue that is breaking a specific use case. I have a workaround but that won't work forever. Would really like to see this get fixed. |
This definitely seems like an upstream bug as what we do is explicitly supported: https://github.com/llvm/llvm-project/blame/2e1809f94aa0f1c1fa0281d1351c0e0ea0bf06e3/clang/lib/Driver/Driver.cpp#L269-L278. The bug seems to be that it assumes |
Yes, this is an upstream bug. I'll try to find the time to send a patch. |
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
Use
clang
with the flag-no-canonical-prefixes
, which results in generally better paths by preserving useful symlinks, and has worked for many years.What happened (include all command output)?
Note that in the failing execution the system configuration file directory becomes
/opt/etc/clang
instead of/opt/homebrew/etc/clang
. The result is that it fails to find the configuration file and include the relevant SDK paths.What did you expect to happen?
Both
clang
invocations should find the configuration directory and succeed.Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: