-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Microbenchmark is not compatible with 1.6.x Google benchmark #9489
Comments
I guess somehow you are using the latest google Would you be able to utilize make or cmake build system instead of building directly with g++ to make sure library version is correct? For example, in your rocksdb folder do |
I'm using google benchmark 1.6.1and I'm building rocksdb using cmake. |
Is there any chance you could install/use a 1.5.5 version as a quick fix if you don't necessarily need to use 16.1? 1.5.5 version works fine with me. |
All other packages in my diseo have no problems with that version. |
Yeah and there isn’t any immediate plan to make change on Rocksdb side. But I tried to clarify things a bit here #9505 Is there anything else I can help you with before closing the issue? |
Does it mean that you are not going to adapt rocksdb code to be able use it with latest google benchmark? 🤔 |
We might in the future - I was just saying there isn’t an intermediate plan. The INSTALL file change is there for more clarity right now. (And I changed the issue title.) |
Summary: **Context:** Google benchmark [v1.6.0](https://github.com/google/benchmark/releases/tag/v1.6.0) introduced a breaking change "`introduce accessorrs for public data members (https://github.com/google/benchmark/pull/1208)`" that will fail RocksDB build of microbench developed based on previous code. For example, #9489. **Summary:** Clarify the maximum version of Google benchmark needed. Pull Request resolved: #9505 Test Plan: CI Reviewed By: ajkr Differential Revision: D34023447 Pulled By: hx235 fbshipit-source-id: 0128ffc31485f2d752ab2116771f6ae53231fcd7
Thanks @hx235 for calcifying it in the doc. Yeah, unfortunately it's because Google benchmark introduced a non-backward compatible change in By default, micro-benchmark is disabled, unless you explicitly enable that by |
Just tested 7.0.1 and looks like issue still is around .. 🤔 |
It's because a non-backward compatible change from google benchmark. If we upgrade, then it will break the build for the user with 1.5.x. And for example Ubuntu 20.0 is still using google benchmark 1.5.0 version. |
gcc 12.0.0 from fedora rawhide
The text was updated successfully, but these errors were encountered: