Bug 1573641 - gdcm still depending on compat-openssl10-devel
Summary: gdcm still depending on compat-openssl10-devel
Alias: None
Product: Fedora
Classification: Fedora
Component: gdcm
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-01 20:30 UTC by Philip Salvaggio
Modified: 2018-05-04 14:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-04 10:36:56 UTC
Type: Bug

Attachments (Terms of Use)

Description Philip Salvaggio 2018-05-01 20:30:32 UTC
Description of problem:

According to https://sourceforge.net/p/gdcm/bugs/397/ GDCM has been updated to OpenSSL 1.1, however, the RPM build is still linking to OpenSSL 1.0, which causes lots of warnings like:

/usr/bin/ld: warning: libssl.so.10, needed by //usr/lib64/libgdcmCommon.so.2.8, may conflict with libssl.so.1.1
/usr/bin/ld: warning: libcrypto.so.10, needed by //usr/lib64/libgdcmCommon.so.2.8, may conflict with libcrypto.so.1.1

whenever linked into an executable that also links to OpenSSL 1.1. Building from source and linking to OpenSSL seems to work, so I think simply swapping line 33 in the .spec file from 

BuildRequires:	compat-openssl10-devel


BuildRequires:	openssl-devel

would resolve the issue.

Version-Release number of selected component (if applicable):


How reproducible:

For me, I was linking to OpenCV (which depends on libgdcmCommon) and another library that linked to OpenSSL 1.1, which would result in:

/usr/bin/ld: warning: libssl.so.10, needed by //usr/lib64/libgdcmCommon.so.2.8, may conflict with libssl.so.1.1

Expected results:

Ideally both would link to the latest versions, libssl.so.1.1 and libcrypto.so.1.1.

Comment 1 Igor Gnatenko 2018-05-04 10:36:56 UTC
Should be fixed in rawhide now.

Comment 2 Philip Salvaggio 2018-05-04 14:29:55 UTC
Awesome, thanks! The F29 repo works on F28 too if people want to use this fix on the current release.

Note You need to log in before you can comment on or make changes to this bug.