Unable to run protoc #5107
Labels
Comments
|
Could you try running |
|
Output from Running Running |
|
@Bidski Is "Linux Mint" something that can be ran inside docker? If so could you help create a docker image that we can run to reproduce the issue? |
|
@xfxyjwf "Linux MInt 18.2" is little more than "Ubuntu Xenial". I am unable to create a docker container to reproduce this. Are there any further tests that I can run to help diagnose this issue? |
|
The output from @Bidski As one more test could you try building |
|
@acozzette the master branch fails to compile at all for me. I get this error from |
|
@acozzette the |
|
@acozzette any update on this? Is there some other diagnostic I can perform to gather more information? |
|
Figured I would try the cmake build system (although you market it as only being for building on windows?). Using the 3.6.1 tarball and the master branch, cmake (and ninja) successfully builds protoc and running On the 3.6.x branch cmake a small patch is needed to Why would the cmake build be successful where the autotools build is not? |
|
@Bidski That is interesting and I can't think of why it would work with cmake but not the autotools build. Unfortunately I don't really have time to look into this now but if cmake works then that may be the best workaround. We are considering deprecating the autools build in favor of cmake soon anyway. |
|
The problem Autotools build system uses version scripts ( (Issue #6113 for this difference between build systems.) |
|
About the original issue - I've faced the same (ClickHouse/ClickHouse#7114 ). It looks like it happens when pthread is not linked to protoc. Most probably relates to: |
|
I recommend the addition of linux label. |
lipnitsk
added a commit
to protobuf-c/protobuf-c
that referenced
this issue
May 9, 2020
-lpthread was missing from the linker command line. See protocolbuffers/protobuf#5107 for more details. .travis.yml: Run CMake debug build for verification
lipnitsk
added a commit
to protobuf-c/protobuf-c
that referenced
this issue
May 9, 2020
-lpthread was missing from the linker command line. See protocolbuffers/protobuf#5107 for more details. .travis.yml: Run CMake debug build for verification
lipnitsk
added a commit
to protobuf-c/protobuf-c
that referenced
this issue
May 9, 2020
-lpthread was missing from the linker command line. See protocolbuffers/protobuf#5107 for more details. .travis.yml: Run CMake debug build for verification
lipnitsk
added a commit
to protobuf-c/protobuf-c
that referenced
this issue
May 9, 2020
-lpthread was missing from the linker command line. See protocolbuffers/protobuf#5107 for more details. .travis.yml: Run CMake debug build for verification
|
I am facing same issue . Any Updates on this issue?? |
|
For cross-compiling, you can specify an protoc binary using this will resolve the issue |
|
Closing out old issues. Please reopen if this still occurs on recent releases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of protobuf and what language are you using?
Version: v3.6.1
Language: C++
What operating system (Linux, Windows, ...) and version?
Linux Mint 18.2
What runtime / compiler are you using (e.g., python version or gcc version)
gcc 7.3.0
What did you do?
Steps to reproduce the behavior:
What did you expect to see
libprotoc 3.6.1
What did you see instead?
terminate called after throwing an instance of 'std::system_error'
what(): Unknown error -1
Aborted
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment
The text was updated successfully, but these errors were encountered: