-
Notifications
You must be signed in to change notification settings - Fork 13
Edit New issue Fix build for libsnappy and libbz2 #11
Comments
Trying to understand where snappy and bz2 are, so that rocksdb build sees them while CMake in MySQL doesn't. Makefile in rocksdb has a libsnappy.a target but it's only used for building rocksdbjavastatic target. There is also build_tools/fbcode_config.sh which has:
and then EXEC_LDFLAGS is used in the Makefile like so:
|
So, in conventional terms, it is
and
I have it to work by setting environment variable ROCKSDB_LIBRARIES before invoking cmake. @mdcallag , would it be ok if I make this to work by having CMakeLists.txt require that the user sets |
yes On Fri, Dec 5, 2014 at 5:20 AM, Sergei Petrunia [email protected]
Mark Callaghan |
But are you only solving this for snappy? Or will this allow multiple On Fri, Dec 5, 2014 at 8:31 AM, MARK CALLAGHAN [email protected] wrote:
Mark Callaghan |
- Basic support for Column Families (writes/reads go the right column family). - CFs are specified per-index in the index comment: INDEX (col1,col2) COMMENT 'cf_name'
…or column families
I get this link error:
...a39a3e/bin/ld: cannot find -lsnappy
From the command line I see that librocksdb.a has a full path, but not so for snappy and bz2:
... /home/mcallaghan/rocksdb/librocksdb.a -lsnappy -lbz2
And there is magic in storage/rocksdb/CMakeLists.txt to do that for librocksdb.a, but not the others
FIND_LIBRARY(Rocksdb_LIBS NAMES rocksdb
PATHS ${Rocksdb_LIB_PATHS} ${Rocksdb_LIB} $ENV{ROCKSDB_LIBRARIES})
IF(EXISTS ${Rocksdb_LIBS})
GET_FILENAME_COMPONENT(LINK_DIR ${Rocksdb_LIBS} ABSOLUTE)
ELSE()
MESSAGE(SEND_ERROR "No rocksdb library directory found! Consider using environment variable ROCKSDB_LIBRARIES=...")
RETURN()
ENDIF()
...
MYSQL_ADD_PLUGIN(rocksdb_se ${ROCKSDB_SOURCES} STORAGE_ENGINE STATIC_ONLY MANDATORY LINK_LIBRARIES ${LINK_DIR} snappy bz2)
I think the workaround is to remove "snappy bz2" from the line above and build RocksDB without support for bz2 and snappy.
The text was updated successfully, but these errors were encountered: