-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
more helpful "PCH file built from a different branch" message #1117
Comments
Just as a warning to anyone who wants to try addressing this issue, we've spent a fair amount of effort trying to catch this message and provide guidance in CmdStanPy, but Apple/Clang changes the wording of the error message seemingly every version as well, so it ends up being very brittle. Doing that while also only having the powers of |
The forum posts I found had instructions for fixing that no longer work. So I put my SEO hat on and formulated a forum post that I hope has the Google juice to pop to the top of search results for pch conflicts: The answer is that you need to
The |
Yeah, the precompiled header files are removed in clean-all: https://github.com/stan-dev/cmdstan/blob/develop/makefile#L316
The extension is actually .hpp.gch. It should be in I think we should move that line from clean-all to clean. Seems like a good option to me. |
Summary:
The PCH file built from a different branch error does not provide a hint on how to fix it. Add such a hint.
Description:
When I try to build with the wrong precompiled header (PCH), I get this:
This is great that it says what's wrong, but it would be even better if it suggested how to fix the problem. I'm pretty sure I need to just delete a .pch file, but I don't know where it's at. A recursive search didn't work:
Reproducible Steps:
See above, but to reproduce it, you need to have two compilers, one of which built the pch file and a different one to tickle this error.
Current Output:
See above.
Expected Output:
Some hint as to where the pch file is that I need to delete. Even better, just automatically delete and rebuild after detecting this error.
Additional Information:
There are a lot of pages where people brought up this problem on our forums or in issues. The advice in the first hit on the forums didn't work, which suggested just running
make clean
. Here's what I get:Current Version:
v2.30.1
The text was updated successfully, but these errors were encountered: