First, I must state that it's something I remember, but can't actually check now, cause I'm currently separated from my machine. The problem that I remember is: currently stable versions of imagemagick don't link with graphviz when use flag is set, cause configure script checks for graphviz using pkg-config, which is a correct check, but for graphviz versions that are currently not stable. I can't recall which version of graphviz started using pkg-config (although it was a fairly recent one), but that should be easy to check. I believe that correct solution is to make one of those versions stable and changing imagemagick dependencies to reflect that fact.
Please, reopen with some errors and actual versions that cause this problem. We can't guess. Thanks.
Point one: maybe my bug report is a bit vague, but if you actually read it, you'd notice that it contains all info needed to locate the bug. Point two: if you actually read the bug report you'd noticed I wrote: "I'm currently separated from my machine" Point three: that's maybe not that obvious, but by writing: "don't link with graphviz when use flag is set" I meant: imagemagick builds fine but ignores graphviz (you could deduce that from "configure script checks for graphviz using pkg-config" part) Having said that, by downloading graphviz sources and reading Changelog I found out that since release 2.4 pkgconfig is now used for reusable libraries. And as the last imagemagick stabilization took place on 1.02.2006 it should have been an easy guess that it was the version I was refering to. As a sidenote: new versions of imagemagick (6.2.7.1) (recent 23.04.2006) and graphviz (2.8) (not that recent 03.02.2006) are availble.
(In reply to comment #2) > Point two: if you actually read the bug report you'd noticed I wrote: "I'm > currently separated from my machine" So file bugs when you are ready to provide needed information, or reopen it when you have that info available. > Having said that, by downloading graphviz sources and reading Changelog I found > out that since release 2.4 pkgconfig is now used for reusable libraries. > And as the last imagemagick stabilization took place on 1.02.2006 it should > have been an easy guess that it was the version I was refering to. Sigh... we are not here to guess. Provide the info as requested and reopen then. All the versions below marked with + are *current stable*. Keywords for media-gfx/imagemagick: | a a a h i m m p p p s s s x x | l m r p a 6 i p p p 3 h p 8 8 | p d m p 6 8 p c c c 9 a 6 6 | h 6 a 4 k s 6 - 0 r - | a 4 4 m c f | a b | c s | o d | s -----------+------------------------------ 6.1.8.8 | + + + + + + + + + 6.2.0.4 | + + + + + + + + + 6.2.0.6 | ~ ~ ~ ~ ~ ~ ~ ~ ~ 6.2.1.5 | ~ ~ ~ ~ ~ ~ ~ ~ ~ 6.2.1.5-r1 | ~ ~ ~ ~ ~ ~ ~ ~ ~ 6.2.2.0 | + + + + ~ + + + + 6.2.2.0-r1 | + + + + ~ + + + + 6.2.2.3 | + + + + ~ + + + ~ 6.2.2.3-r1 | + + + + + + + + + + 6.2.4.2 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6.2.4.2-r1 | + + + + + ~ + + + + + 6.2.5.2 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6.2.5.4 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 6.2.5.5 | + + + + + ~ + + ~ + + + 6.2.6.0 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ > As a sidenote: new versions of imagemagick (6.2.7.1) (recent 23.04.2006) and > graphviz (2.8) (not that recent 03.02.2006) are availble. File another bug for version bump if there's not already one open.
Noticed, how it becomes something akind of a ping-pong match ? What more info do you need ? Yeah, it's 6.2.5.5, although I wouldn't be surprized if some earlier where affected too. To spell it out (again): One of RDEPEND of imagemagick is media-gfx/graphviz, it's trigered by graphviz use flag, but when configure script of the stable version of imagemagick runs, it fails to detect any graphviz version previous to 2.4, cause it (imagemagick) checks for it (graphviz) using pkg-config, that of course may get unnoticed, cause it does not cause imagemagick emerge to fail, it simply does not build the graphviz related parts, as can be read on screen in the short moment between econf and emake. So, what else should I explain ?
I see this has become another one of my bugs, that's permanently ignored (as #95961 is - well that one is not exactly ignored, it's just that while reporting that one, I gave a simple solution at the same time, that nobody bothered to implement). Well, I won't be crying about that. However, I want to point another bug, which, while not a simple duplicate, is strongly related to this one. It's bug #99802.
Maybe this is the problem: I compiled imagemagick before, and it compiled cleanly, after, I compiled graphviz and kdevelop (together), and after a few weeks, when doing a revdep-rebuild, it tried to reemerge imagemagick with this errors: if /bin/sh ./libtool --silent --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I./magick -I./wand -march=k8 -O3 -pipe -fomit-frame-pointer -funroll-loops -Wall -pthread -MT coders/coders_ept_la-ept.lo -MD -MP -MF "coders/.deps/coders_ept_la-ept.Tpo" -c -o coders/coders_ept_la-ept.lo `test -f 'coders/ept.c' || echo './'`coders/ept.c; \ then mv -f "coders/.deps/coders_ept_la-ept.Tpo" "coders/.deps/coders_ept_la-ept.Plo"; else rm -f "coders/.deps/coders_ept_la-ept.Tpo"; exit 1; fi coders/png.c: In function `ReadOnePNGImage': coders/png.c:1755: warning: implicit declaration of function `png_access_version' coders/png.c:1764: error: `png_ptr' undeclared (first use in this function) coders/png.c:1764: error: (Each undeclared identifier is reported only once coders/png.c:1764: error: for each function it appears in.) make: *** [coders/coders_png_la-png.lo] Error 1 make: *** Se espera a que terminen otras tareas.... !!! ERROR: media-gfx/imagemagick-6.2.5.5 failed. Call stack: ebuild.sh, line 1545: Called dyn_compile ebuild.sh, line 940: Called src_compile imagemagick-6.2.5.5.ebuild, line 86: Called die !!! compile problem !!! If you need support, post the topmost build error, and the call stack if relevant. revdep-rebuild failed to emerge all packages you have the following choices: - if emerge failed during the build, fix the problems and re-run revdep-rebuild or - use -X or --package-names as first argument (trys to rebuild package, not exact ebuild) or - set ACCEPT_KEYWORDS="~<your platform>" and/or /etc/portage/package.unmask (and remove /root/.revdep-rebuild.5_order to be evaluated again) or - modify the above emerge command and run it manually or - compile or unmerge unsatisfied packages manually, remove temporary files and try again (you can edit package/ebuild list first) To remove temporary files, please run: rm /root/.revdep-rebuild*.?_* Now as it can be seen, I cannot emerge imagemagick again. More info: emerge -pv graphviz imagemagick >>> --pretend disables --ask... removing --ask from options. These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] media-gfx/graphviz-1.16-r1 USE="-tcltk" 0 kB [ebuild R ] media-gfx/imagemagick-6.2.5.5 USE="X jpeg mpeg perl png tiff zlib -bzip2 -doc -fpx -graphviz -gs -jbig -jpeg2k -lcms -minimal -nocxx -truetype -wmf -xml" 0 kB Total size of downloads: 0 kB (I wanted graphviz only for using with kdevelop, is this the reason of the -graphviz use)
Hi, it's me again. I was a moment ago emerging ImageMagick-6.2.8.0, guess what: graphviz useflag fails again, ImageMagick-6.2.8.0 requires now libgvc >= 2.9.0, which is not yet in portage.
Ok, this time it's my mistake, while ImageMagick-6.2.8.0 does require libgvc >= 2.9.0, there's no graphviz-2.9 yet, just development snapshots. Guess ImageMagick moves a bit too fast.
*** Bug 142725 has been marked as a duplicate of this bug. ***
I've added graphviz-2.6 as a minimum requirement (when USE=graphviz is set) which should fix the pkg-config issue in imagemagick-6.3.3.
