-
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
-fsanitize-blacklist does not work correctly with relative paths #843
Milestone
Comments
Are you attempting to use |
I'm using |
froydnj
changed the title
Sanitize + assembler support
-fsanitize-blacklist does not work correctly with relative paths
Sep 10, 2020
That wasn't, but I think your answer tells me what I need to know. The temporary workaround is to pass an absolute path for |
glandium
added a commit
to glandium/sccache
that referenced
this issue
Dec 15, 2020
When the current directory of the sccache process is not the same as the current directory for the compiler process, extra hash files are currently not found, leading to errors. Fixes mozilla#843
glandium
added a commit
that referenced
this issue
Dec 16, 2020
When the current directory of the sccache process is not the same as the current directory for the compiler process, extra hash files are currently not found, leading to errors. Fixes #843
Xanewok
referenced
this issue
in paritytech/cachepot
Apr 2, 2021
When the current directory of the sccache process is not the same as the current directory for the compiler process, extra hash files are currently not found, leading to errors. Fixes #843
drahnr
referenced
this issue
in paritytech/cachepot
Apr 6, 2021
When the current directory of the sccache process is not the same as the current directory for the compiler process, extra hash files are currently not found, leading to errors. Fixes #843
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to replace ccache with sccache in the AOSP build system but I'm facing a few errors
This is the first issue that stems from using the
-c
flag of clang enabling the use of the integrated clang assemblerThe same command without
-c
works properlyThe text was updated successfully, but these errors were encountered: