3.11.2: python module build fails

[kloczek]

+ cd python
+ CFLAGS='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto=auto -flto-partition=none'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -flto=auto -flto-partition=none -fuse-linker-plugin'
+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -s'
running build
running build_py
Generating google/protobuf/descriptor_pb2.py...
terminate called after throwing an instance of 'std::system_error'
  what():  Unknown error -1
error: Bad exit status from /var/tmp/rpm-tmp.cJpZTU (%build)

[stac47]

I think the problem comes the fact you are using the --as-needed linker option.
Behind the scene, python setup.py build will run protoc which will not have the NEEDED shared lib dependency onto libpthread.so.0.

[kloczek]

Using indirect linking is wrong and should be fixed.

[stac47]

By the way, this is a known issue of the gnu libc++: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55394

[kloczek]

After disable LTO I was able build protobuf.

[filimonov]

#5107 (comment)

[elharo]

For questions or troubleshooting, please see the protobuf mailing list: https://groups.google.com/forum/#!forum/protobuf or Stack Overflow https://stackoverflow.com/questions/tagged/protocol-buffers

We don't formally monitor stack overflow, but there are a lot of experienced developers there who also use protobuf.