Quote from: 1blockologist on July 07, 2017, 01:57:21 PM

Quote from: clintar2 on July 07, 2017, 12:10:56 AM

If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratch

you can get the branch with

Code:

git clone -b lmdb_scratch https://github.com/clintar/boolberry.git

then

Code:

mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon

should compile it, at least in linux. Let me know if it compiles or not at least!

I tested it out on OSX, this is what I got

Code:

cmake -DDATABASE=lmdb ../..
-- Building for a 64-bit system
-- Could not find DATABASE in env (not required unless you want to change database type from default: lmdb)
CMake Warning at CMakeLists.txt:56 (find_package):
  By not providing "FindBerkeleyDB.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "BerkeleyDB", but CMake did not find one.

  Could not find a package configuration file provided by "BerkeleyDB" with
  any of the following names:

   BerkeleyDBConfig.cmake
   berkeleydb-config.cmake

  Add the installation prefix of "BerkeleyDB" to CMAKE_PREFIX_PATH or set
  "BerkeleyDB_DIR" to a directory containing one of the above files. If
  "BerkeleyDB" provides a separate development package or SDK, be sure it has
  been installed.

-- BerkeleyDB not found and has been disabled.
-- Boost version: 1.59.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- atomic
-- program_options
-- Found Git: /usr/local/bin/git
CMake Error at contrib/db_drivers/CMakeLists.txt:32 (add_subdirectory):
  add_subdirectory given source "liblmdb" which is not an existing directory.

-- Configuring incomplete, errors occurred!

this was from the "cmake -DDATABASE=lmdb ../.." line

and for the following make command, there is no 'daemon' target to build

I'll check a linux node

Maybe follow this: http://macappstore.org/berkeley-db/
I did have an issue before that should be fixed. It would have a floating point exception in case you ran into that already.