[gentoo-amd64] Re: GCC 4 CFLAGS

[Duncan]

Peter Humphrey <prh@××××××××××.uk> posted
200609241306.23175.prh@××××××××××.uk, excerpted below, on  Sun, 24 Sep
2006 13:06:23 +0000:

> I've started a new thread because the old one had drifted.
>
> While trying Duncan's CFLAGS I found I couldn't emerge imagemagick because
> it didn't recognise -combine or -ftree-pre.

Strange.  imagemagick is working just fine here, with those CFLAGS.  As
David notes, however, both those CFLAGS are new to gcc 4.1.  Don't try to
use them with gcc 3.x as they will cause problems.  Part of amd64's
portage bashrc does try to filter invalid flags, but it's far better not
to use them at all, which means not using these with gcc 3.x.

It's also possible, altho less likely, that the issue is an older
imagemagick, as I'm running ~arch here and have the latest updates as of
yesterday merged (the reason I know for sure it's working here). 
Currently merged here:

imagemagick-6.2.9.5-r1

> So I removed those from /etc/make.conf and reran emerge imagemagick.
> Weirdness. Here are some extracts from the compilation log:

> [...]
> ImageMagick is configured as follows. Please verify that this configuration
> matches your expectations.
> [...]
> Options used to compile and link:
>   PREFIX      = /usr
>   EXEC-PREFIX = /usr
>   VERSION     = 6.2.9
>   CC          = x86_64-pc-linux-gnu-gcc
>   CFLAGS
> = -march=k8 -Os -pipe -frename-registers -fweb -freorder-blocks -freorder-blocks-and-partition -fu
> nit-at-a-time -fgcse-sm -fgcse-las -fgcse-after-reload -fmerge-all-constants -Wall -pthread
>   CPPFLAGS    = -I/usr/include
>   PCFLAGS     =
>   DEFS        = -DHAVE_CONFIG_H
>   LDFLAGS     = -L/usr/lib64 -L/usr/lib64 -lfreetype -lz -L/usr/lib
>   LIBS
> = -lMagick -llcms -ltiff -lfreetype -ljpeg -lfontconfig -lXext -lSM -lICE -lX11 -lXt -lbz2 -lz -lp
> thread -lm -lpthread
>   CXX         = x86_64-pc-linux-gnu-g++
>   CXXFLAGS
> = -march=k8 -Os -pipe -frename-registers -fweb -freorder-blocks -funit-at-a-time -fgcse-sm -fgcse-
> las -fgcse-after-reload -fmerge-all-constants -pthread
> [...]
> /bin/install -c 'wand/Wand-config' '/var/tmp/portage/imagemagick-6.2.9.5-r1/image//usr/bin/Wand-config'
> cd PerlMagick && /usr/bin/perl Makefile.PL
> Checking if your kit is complete...
> Looks good
> Writing Makefile for Image::Magick
> ( cd PerlMagick && make CC='x86_64-pc-linux-gnu-gcc' && \
>         make CC='x86_64-pc-linux-gnu-gcc' install && \
>         make clean && rm -f  Makefile.old )
> make[2]: Entering directory
> `/var/tmp/portage/imagemagick-6.2.9.5-r1/work/ImageMagick-6.2.9/PerlMagick'
> cp Magick.pm blib/lib/Image/Magick.pm
> AutoSplitting blib/lib/Image/Magick.pm (blib/lib/auto/Image/Magick)
> /usr/bin/perl5.8.8 /usr/lib64/perl5/5.8.8/ExtUtils/xsubpp  -typemap /usr/lib64/perl5/5.8.8/ExtUtils/typemap
> Mag
> ick.xs > Magick.xsc && mv Magick.xsc Magick.c
> x86_64-pc-linux-gnu-gcc -c  -I../ -I.. -I/usr/include/freetype2 -I/usr/include/libxml2 -D_REENTRANT -D_GNU_SOURC
> E -DTHREADS_HAVE_PIDS -fno-strict-aliasing -pipe -Wdeclaration-after-statement -D_LARGEFILE_SOURCE -D_FILE_OFFSE
> T_BITS=64 -march=k8 -Os -pipe -frename-registers -fweb -freorder-blocks -freorder-blocks-and-partition -funit-at
> -a-time -fgcse-sm -fgcse-las -fgcse-after-reload -fmerge-all-constants -Wall -pthread -march=k8 -O2 -pipe -frena
> me-registers -fweb -freorder-blocks -freorder-blocks-and-partition -combine -funit-at-a-time -ftree-pre -fgcse-s
> m -fgcse-las -fgcse-after-reload -fmerge-all-constants   -DVERSION=\"6.2.9\" -DXS_VERSION=\"6.2.9\" -fPIC "-I/us
> r/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE"  -DHAVE_CONFIG_H
> Magick.c
> x86_64-pc-linux-gnu-gcc: unrecognized option `-combine'
> cc1: error: unrecognized command line option "-ftree-pre"
> make[2]: *** [Magick.o] Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/imagemagick-6.2.9.5-r1/work/ImageMagick-6.2.9/PerlMagick'
> make[1]: *** [install-exec-perl] Error 2
> make[1]: Leaving directory
> `/var/tmp/portage/imagemagick-6.2.9.5-r1/work/ImageMagick-6.2.9'
> make: *** [install-am] Error 2
>
> !!! ERROR: media-gfx/imagemagick-6.2.9.5-r1 failed.
> Call stack:
>   ebuild.sh, line 1546:   Called dyn_install
>   ebuild.sh, line 1020:   Called src_install
>   imagemagick-6.2.9.5-r1.ebuild, line 90:   Called die
>
> So I removed -rf  /var/tmp/portage/imagemagick-6.2.9.5-r1 and got exactly
> the same result!
>
> Can anyone see what I'm doing wrong? Perhaps another C flag is pulling those
> two in.

Again, that's likely because you are using gcc 3.x, or it shouldn't be a
problem.  However, that doesn't explain why those flags are still being
pulled in.

I'm not sure on that, but I *DO* know there has been some serious
re-working going on due to perlmagick -- the reason for the latest
updates.  The imagemagick build has been severely quirked from upstream,
doing some really strange stuff that cause parts of it (including
perlmagick) it to try to build against the OLD libraries still on the
system from the old version, instead of the NEW libraries just built as
part of the new version.  The Gentoo bugs mentioned in the changelog tell
the whole story, which I won't repeat here, but I STRONGLY suspect this
weirdness you are seeing is related to the extreme quirkiness, with the
build trying to trick itself into doing things in a way that works for
upstream, rather than fixing the problem (a simple library search order
inversion) properly.

Apparently, upstream has taken some of the Gentoo patches and further
versions won't be so quirked out and complex.  Meanwhile however, Gentoo
is left with a hodgepodge of patched versions, some stable some ~arch,
some all quirked out, some partially patched, some (hopefully) fully
patched... it's a rather bad situation all around.

gcc 4.1.1 is now stable.  I'd suggest you merge it if you haven't. 
However, Gentoo does NOT switch to it on its own when you upgrade.  You
then need to run gcc-config (or eselect compiler if you have it merged) to
properly switch to it (as Dave mentions).  After you do that, the new
CFLAGS (if you choose to use them) should work far better, tho as mentioned
-combine has problems with a very few packages.

As I said, imagemagick in particular works just fine, here, with those
CFLAGS (and gcc-4.1.1 of course), tho due to the perlmagick mess, you /may/
have to remerge it a couple times in a row and/or merge the latest ~arch
version, in ordered to avoid the quirked out weirdness of some of the
older imagemagick versions.  Again, read the bugs mentioned in the portage
tree imagemagick changelog and you'll very quickly understand how complex
the problem is, and why I keep calling it quirked out! =8^(  There was
some /very/ strange stuff going on!  Luckily, it seems to be getting
straightened out now.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@g.o mailing list