-
Notifications
You must be signed in to change notification settings - Fork 171
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
No longer compiles due to googletest changes. #743
Comments
AphidGit
changed the title
No longer compiles.
No longer compiles due to googletest changes.
Dec 19, 2022
Hm this is weird since we use the submodule at a specific commit so it shouldn't suddenly change. How did you initialize the submodule? Can you show the output of |
On ubuntu 22.04 LTS, here's how I fixed it:
Releases 1.13.x and later will not work due to C++14 being required. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue: This no longer compiles correctly. Issue is in the imported
googletest
which is not version-bound. Some changes in this external code have made it incompatible with this repo's makefile/autotools thingamajig.A test was added that does something to blow up the compiler; specifically this bit of code;
Dummy is filled with the current stack pointer to check that the stack grows downward or upward (i.e. what do the memory addresses do, increase or decrease?). The compiler does not like this uninitialized pointer use when used with default settings including
-wError=maybe-unitialized
. This option needs to be turned off to compile googletest (and probably results in more errors; i.e. set-Wno-error-maybe-uninitialized
). Haven't been able to test any further because autotools is so impenetrably complicated.The text was updated successfully, but these errors were encountered: