Skip to content
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

Project doesn't build with GCC 11+ because of GTest and ABSL #59

Closed
flomnes opened this issue Oct 10, 2022 · 2 comments
Closed

Project doesn't build with GCC 11+ because of GTest and ABSL #59

flomnes opened this issue Oct 10, 2022 · 2 comments

Comments

@flomnes
Copy link
Collaborator

flomnes commented Oct 10, 2022

Error looks like this

/home/gergoszabo/CLionProjects/Prog2_08/test-framework/googletest-src/googletest/src/gtest-death-test.cc: In function ‘bool testing::internal::StackGrowsDown()’:
/home/gergoszabo/CLionProjects/Prog2_08/test-framework/googletest-src/googletest/src/gtest-death-test.cc:1224:24: error: ‘dummy’ may be used uninitialized [-Werror=maybe-uninitialized]
 1224 |   StackLowerThanAddress(&dummy, &result);
      |   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~
/home/gergoszabo/CLionProjects/Prog2_08/test-framework/googletest-src/googletest/src/gtest-death-test.cc:1214:13: note: by argument 1 of type ‘const void*’ to ‘void testing::internal::StackLowerThanAddress(const void*, bool*)’ declared here
 1214 | static void StackLowerThanAddress(const void* ptr, bool* result) {
      |             ^~~~~~~~~~~~~~~~~~~~~
/home/gergoszabo/CLionProjects/Prog2_08/test-framework/googletest-src/googletest/src/gtest-death-test.cc:1222:7: note: ‘dummy’ declared here
 1222 |   int dummy;
@flomnes flomnes linked a pull request Oct 10, 2022 that will close this issue
@flomnes flomnes changed the title Project doesn't build with GCC 11+ because of GTest Project doesn't build with GCC 11+ because of GTest and ABSL Oct 10, 2022
@pet-mit
Copy link
Collaborator

pet-mit commented Jun 19, 2023

Is this still an issue?

@flomnes
Copy link
Collaborator Author

flomnes commented Jun 19, 2023

No, I think that since we merged v9.5 from Google, the problem was fixed

@flomnes flomnes closed this as completed Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants