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

librocksdb_sys::bz_internal_error conflicts with bzip2-sys::bz_internal_error #609

Closed
nikurt opened this issue Feb 15, 2022 · 1 comment · Fixed by #628
Closed

librocksdb_sys::bz_internal_error conflicts with bzip2-sys::bz_internal_error #609

nikurt opened this issue Feb 15, 2022 · 1 comment · Fixed by #628

Comments

@nikurt
Copy link
Contributor

nikurt commented Feb 15, 2022

I'm getting the following link error due to the duplicate symbol when linking a binary with link-time optimizations:

   Compiling neard v0.0.0 (/home/nikurt/nearcore-rdb-3/neard)
warning: Linking globals named 'bz_internal_error': symbol multiply defined!

error: failed to load bc of "librocksdb_sys-33c86cdce183a558.librocksdb_sys.8e9e6b3e-cgu.0.rcgu.o":

warning: `neard` (bin "neard") generated 1 warning
error: could not compile `neard` due to previous error; 1 warning emitted
make: *** [Makefile:34: neard-release] Error 101

Symbols are defined here:

A workaround is to disable feature bzip2 of crate rocksdb.

Link-time optimizations defined in my Makefile as follows:

CARGO_PROFILE_RELEASE_LTO = fat
@dnrusakov
Copy link

dnrusakov commented May 25, 2022

Is it possible to release a new version of the rocksdb crate in order to accommodate this change? The current version available on crates.io is 0.18.0 and it doesn't have all recent changes including this one. cc @aleksuss

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