Summary: | media-gfx/imagemagick - /usr/bin/Wand-config injects bogus CFLAGS/LDFLAGS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Francesco Lamonica <alienpenguin> |
Component: | Current packages | Assignee: | Gentoo Graphics Project <graphics+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | flameeyes, jakub |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Francesco Lamonica
2006-10-30 12:49:42 UTC
There's not a single mention of ftracers in the source code or patches. Post the output of 'grep -Rni ftracers /etc/portage' I forgot to add: i already grep'd for ftracers in /etc and there is no 'trace' (excuse the pun :)) of it, while it is present in all Makefile of /var/tmp/portage/xine-lib-1.1.2-r2 Sandstorm:~# grep -Rni ftracers /etc/portage Sandstorm:~# grep -Rni ftracers /var/tmp/portage/ /var/tmp/portage/xine-lib-1.1.2-r2/work/xine-lib-1.1.2/include/Makefile:416:WAND_CFLAGS = -march=k8 -O2 -pipe -fweb -ftracers -Wall -pthread ... etc. Since no news so far i'll add an extra bit of info i found: the only place i have -ftracers is in the WAND_CFLAGS Sandstorm:/var/tmp/portage/xine-lib-1.1.2-r2/work/xine-lib-1.1.2# grep tracers * Makefile:WAND_CFLAGS = -march=k8 -O2 -pipe -fweb -ftracers -Wall -pthread config.log:WAND_CFLAGS='-march=k8 -O2 -pipe -fweb -ftracers -Wall -pthread' config.status:s,@WAND_CFLAGS@,|#_!!_#|-march=k8 -O2 -pipe -fweb -ftracers -Wall -pthread,g this seems to belong to /usr/bin/Wand-config that is part of ImageMagick-6.2.9.5 and if i type Wand-config --cflags the result is: Sandstorm:/var/tmp/portage/xine-lib-1.1.2-r2/work/xine-lib-1.1.2# Wand-config --cflags -march=k8 -O2 -pipe -fweb -ftracers -Wall -pthread what gives? i am really puzzled ok, i got it solved deleting imagemagick use flag from xine-lib, but still dont know why Wand-config should set the wrong CFLAGS, you might want to investigate now you should be able to reproduce the bug. Thanks for investigating the issue. WAND_CFLAGS injects the CFLAGS used during compile. You probably used "-ftracers" on your imagemagick build. Anyway, to work around this same issue, xine-lib-1.1.3_pre20061112 uses pkg-config to find imagemagick. I have a little more info to share, i eventually figured that ImageMagick was giving trouble and fixed it by hand (thanks anyway Diego :-) ). Then I tried to re-emerge imagemagick but still faced problems with -ftracers. There were many places that were sharing this '-ftracers' most notably a few /usr/bin/*-config scripts: changing those and re-emerging perl as well did the trick and I managed to upgrade ImageMagick as well. Hope this helps. I'm closing this bug as it looks like a local issue and it works for the reporter now. No, it's not a local issue. The compile failure was a local issue, the bug here is not local. The bug is that Wand-config reports the CFLAGS used for building imagemagick as the CFLAGS to use to build anything else using ImageMagick. This is wrong. Wand-config should only reports those flags (-I*, -pthread, -L*, -l*) that are used to build against ImageMagick, not the CFLAGS used to build it. Similar issues happens/happened with MySQL; these are bugs, not local issue. The effects of these bugs are different: - code that shouldn't be built with optimisations will be built with optimisations; - code that shouldn't be built with debug info will be built with debug info; - if the CFLAGS used for building ImageMagick were wrong, it will break anything that uses Wand-config. The original report was for the third case, which is a local issue; but the bug remains and should be fixed. (In reply to comment #8) > I'm closing this bug as it looks like a local issue and it works for the > reporter now. > Still an issue with 6.3.3. too: betelgeuse@pena /usr/portage/media-gfx $ Wand-config --cflags -O2 -march=nocona -pipe -fomit-frame-pointer -Wall -W -pthread betelgeuse@pena /usr/portage/media-gfx $ Wand-config --ldflags -L/usr/lib -Wl,--as-needed -lfreetype -lz Should not have my CFLAGS and LDFLAGS here. Still same crap with 6.3.5.10; has anyone reported this upstream yet? (In reply to comment #11) > Still same crap with 6.3.5.10; has anyone reported this upstream yet? http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=10379 should be fixed in media-gfx/imagemagick-6.3.7.9 |