Closed adithyabhatkajake closed 1 year ago
I forgot to re-build the container when I changed the branch. With the rebuilt container, v0.10.x has the same error as the master branch.
Hi @adithyabhatkajake. Can you please run make
from concord-bft
folder and update this ticket with the result?
@adithyabhatkajake , please follow the instructions from README.
Hi @adithyabhatkajake.
I've also encountered the same problem. It can be solved by playing with the cmake arguments.
For example, replace "cmake .." with "CC=clang CXX=clang++ cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=TRUE -DBUILD_COMM_TCP_PLAIN=FALSE -DBUILD_COMM_TCP_TLS=TRUE -DCMAKE_CXX_FLAGS_RELEASE=-O3 -g -DUSE_LOG4CPP=TRUE -DBUILD_ROCKSDB_STORAGE=TRUE -DUSE_S3_OBJECT_STORE=TRUE -DUSE_OPENTRACING=TRUE -DCMAKE_EXPORT_COMPILE_COMMANDS=TRUE -DOMIT_TEST_OUTPUT=FALSE -DKEEP_APOLLO_LOGS=TRUE -DBUILD_SLOWDOWN=FALSE -DBUILD_KVBC_BENCH=TRUE -DLEAKCHECK=FALSE -DTHREADCHECK=FALSE .."
(These arguments are used in the docker build.)
I am looking for a stable branch that compiles inside the Docker image. I wanted to test some cryptographic optimizations. I tried the
master
branch and thev0.10.x
branches.Steps to Reproduce General build:
cd concord-bft
docker build -t sbft .
mkdir build; cd build
cmake .. && make -j7
Expected behavior Everything should compile without errors.
Logs
master
branch: make-master-errors.logv0.10.x
branch: (Solved partially when I rebuilt the container) make-v0.10.x-errors.log