Bug 922937 - dcmtk-devel missing libtiff-devel and libpng-devel dependencies
Summary: dcmtk-devel missing libtiff-devel and libpng-devel dependencies
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: dcmtk
Version: 22
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mario Ceresa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-18 20:03 UTC by Torsten Rohlfing
Modified: 2015-04-19 16:53 UTC (History)
3 users (show)

Fixed In Version: dcmtk-3.6.0-14.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-19 16:53:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Torsten Rohlfing 2013-03-18 20:03:42 UTC
Description of problem:

Some DCMTK libraries (e.g., dcmimage) depend on libtiff.so, which is provided by libtiff-devel, but that package is not a dependency of dcmtk-devel


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

dcmtk-devel-3.6.0-8.fc17.x86_64
libtiff-devel-3.9.7-1.fc17.x86_64


How reproducible:

Install dcmtk-devel package on a system without libtiff-devel already installed. Try to link program against dcmimage library.


Steps to Reproduce:
1. Install dcmtk-devel
2. Create c++ source file, /tmp/main.cxx containing "int main() { return 0; }"
3. Run "g++ -L/usr/lib64/dcmtk -ldcmimage -ldcmimgle -ldcmdata -lofstd -loflog -lpthread -lz -ltiff -lpng /tmp/main.cxx"
  

Actual results:

/usr/bin/ld: cannot find -ltiff
/usr/bin/ld: cannot find -lpng


Expected results:

Program should link.


Additional info:

Leaving out "-ltiff" and "-lpng" produces:

/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_create_info_struct'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_write_info'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `TIFFSetField'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_write_image'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_set_IHDR'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_destroy_write_struct'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_set_text'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `TIFFFlushData'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_init_io'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `TIFFCleanup'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `TIFFFdOpen'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_set_longjmp_fn'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `TIFFWriteScanline'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_convert_from_time_t'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_write_end'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_set_tIME'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_create_write_struct'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `png_access_version_number'
/usr/lib64/dcmtk/libdcmimage.so: undefined reference to `TIFFGetVersion'

so dcmimage definitely depends on libtiff and libpng.

Comment 1 Mario Ceresa 2013-03-19 08:35:21 UTC
Hello Torsten,
thanks for reporting. I can reproduce the bug and I'll look into it.

Mario

Comment 2 Fedora End Of Life 2013-07-04 06:20:33 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Peter Lemenkov 2013-07-04 07:14:32 UTC
Re-targeting it to Rawhide to prevent accidental closure.

Comment 4 Mario Ceresa 2013-07-10 07:53:46 UTC
Sorry I forgot about this one. New spec is building in rawhide now...

Comment 5 Fedora Update System 2013-07-10 08:30:26 UTC
dcmtk-3.6.0-14.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/dcmtk-3.6.0-14.fc19

Comment 6 Fedora Update System 2013-07-11 02:32:50 UTC
Package dcmtk-3.6.0-14.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dcmtk-3.6.0-14.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12739/dcmtk-3.6.0-14.fc19
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-07-20 09:35:12 UTC
dcmtk-3.6.0-14.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Volker Fröhlich 2014-12-18 23:01:28 UTC
This problem still exists. It is not enough to add Requires to the devel sub-package! At least the libdcmimage binary must actually be linked to libtiff and libpng.

Comment 9 Jaroslav Reznik 2015-03-03 16:52:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 10 Volker Fröhlich 2015-04-19 16:53:53 UTC
I'm not sure what I saw there, but the issue doesn't exist any longer.


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