Hi Axel, I attempted the manual symlink route before, and it made the program segfault during the OpenSSL FIPS self check. I'm not sure the package is supposed to touch on libraries either, as it may cause conflicts. Does upstream not agree that the devel version should not be required? Best, Georg On 5/5/22 11:30, Axel Braun wrote:
Am Freitag, 29. April 2022, 16:50:13 CEST schrieb Axel Braun:
H Gents,
Am Freitag, 29. April 2022, 16:36:01 CEST schrieb Georg Pfuetzenreuter:
Great input Marcus - thank you very much!
Installing libopenssl-devel makes it work immediately: Confirmed! Here as well. However, a -devel package should not be needed after compilation.
Apr 29 16:34:41 dracutdev01.home.lysergic.dev orthanc[23899]: W0429 16:34:41.640477 HttpServer.cpp:1775] HTTP server listening on port: 8042 (HTTPS encryption is enabled, remote access is not allowed)
I hope Axel can incorporate that into the package (or, even better, check with the developers if this can be solved upstream).
Yes, I will report this upstream.
I just wonder why Debian uses libcrypto.so instead of libcrypto.so.<major> - or maybe they create a symlink?
looks like that ends up in a ping-pong between upstream and openSUSE :-(
As solution I could add the -devel pacakge as runtime dependency, what i not really like, or determine the libcrypto.so.<version> and create a symlink without <version> during build.
Can anyone tell me how to determine the lib version during build? ldconfig -v | grep libcrypto.so did not work...
Thanks Axel