Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

libprotobuf version problem issue?

See original GitHub issue

I did the following line in bash

python -c "import deepchem as dc"

But was getting the following error:

I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcudnn.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcurand.so locally
[libprotobuf FATAL google/protobuf/stubs/common.cc:78] This program was compiled against version 3.1.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.2.0).  Contact the program author for an update.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "external/protobuf/src/google/protobuf/any.pb.cc".)
terminate called after throwing an instance of 'google::protobuf::FatalException'
  what():  This program was compiled against version 3.1.0 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.2.0).  Contact the program author for an update.  If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library.  (Version verification failed in "external/protobuf/src/google/protobuf/any.pb.cc".)
Aborted (core dumped)

But it is not caused by tensorflow since I tried import tensorflow as tf and we are good.

Are you guys aware of any other dependency package which uses the protobuf?

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

XericZephyrcommented, Mar 7, 2017

Thanks @patrickhop, it works by putting import tensorflow before import deepchem as dc, i.e.,

python -c "import tensorflow as tf; import deepchem as dc"

0reactions

lilleswingcommented, Jul 5, 2017

We are currently using protobuf 3.1.0 with tf 1.0.1. Latter versions of tf require protobuf 3.2.x. We will upgrade the protobuf when we upgrade tensorflow (probably to 1.2.x). This issue can be closed and further conversation can be had https://github.com/deepchem/deepchem/issues/602

Top Results From Across the Web

libprotobuf version mismatch · Issue #10761 - GitHub

I am getting this error while running some testcases from my application as: [libprotobuf FATAL external/com_google_protobuf/src/google/protobuf ...

Protobuf version mismatch - Stack Overflow

If these libs are built using with different version of protobuf, it will cause this problem. Rebuild all the libs (including tf) using...

Issue 370 in protobuf: static initialization problem with dlopen

If I changed src/google/protobuf/compiler/cpp/cpp_file.cc to use non-static version of 'bool already_here' like in the attached file, the problem seems

Google protocol buffer (Protobuf) version conflict on Linux ...

Common Problem/ Error: Protobuf compiler version doesn't match library version. The version mismatch creates difficulties in compiling ...

Protobuf version error on Ubuntu 18.04 and gazebo9 [closed]

... ii python3-protobuf 3.0.0-9.1ubuntu1 amd64 Python 3 bindings for protocol buffers Issue open on gazebo repo too : https://bitbucket.org/osrf/gazebo/iss.