Bug 179200 - ImageMagick-devel should "Requires" lcms-devel
Summary: ImageMagick-devel should "Requires" lcms-devel
Alias: None
Product: Fedora
Classification: Fedora
Component: ImageMagick
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2006-01-28 00:20 UTC by Kevin Fenzi
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2006-01-30 14:03:24 UTC

Attachments (Terms of Use)
mock build.log with compile failure (50.13 KB, text/plain)
2006-01-28 00:20 UTC, Kevin Fenzi
no flags Details

Description Kevin Fenzi 2006-01-28 00:20:09 UTC
Description of problem:
autotrace fails to build under mock for fc5/devel. 
Possibly a missing BuildRequires for lcms-devel.

end of mock build.log: 

gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m32 -march=i386 -mtune=pentium4
-fasynchronous-unwind-tables -o .libs/autotrace atou.o main.o getopt.o getopt1.o
 ./.libs/libautotrace.so -L/usr/lib -lMagick -llcms -ltiff
/usr/lib/libfreetype.so -ljpeg -lgs -lXext -lSM -lICE -lX11 -lXt -lbz2 -lpthread
-lpng -lz -lm
/usr/bin/ld: cannot find -llcms
collect2: ld returned 1 exit status
make[1]: *** [autotrace] Error 1
make[1]: Leaving directory `/builddir/build/BUILD/autotrace-0.31.1'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.78515 (%build)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.78515 (%build)

Full build.log attached as well.

Comment 1 Kevin Fenzi 2006-01-28 00:20:09 UTC
Created attachment 123816 [details]
mock build.log with compile failure

Comment 2 Roozbeh Pournader 2006-01-28 20:54:30 UTC
This is actually a bug in ImageMagick-devel. It should have a dependency on
lcms-devel, since Magick-config reports "-llcms" but does not have it as a

Comment 3 Roozbeh Pournader 2006-01-29 10:10:56 UTC
For the record, this happens with ImageMagick-devel-

Comment 4 Matthias Clasen 2006-01-30 14:03:24 UTC
Will be fixed with the next rebuild.

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