Bug 125027 – failure building x11-libs/cairo-1.0.2 with -O2

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jonathan Simms 2006-03-04 18:27:35 UTC]

When trying to build the dependencies for mozilla-firefox-bin, cairo is built and i get the following error:

i686-pc-linux-gnu-gcc -shared  .libs/cairo.o .libs/cairo-arc.o .libs/cairo-array.o .libs/cairo-cache.o .libs/cairo-clip.o .libs/cairo-color.o .libs/cairo-debug.o .libs/cairo-fixed.o .libs/cairo-font.o .libs/cairo-font-options.o .libs/cairo-gstate.o .libs/cairo-hash.o .libs/cairo-hull.o .libs/cairo-image-surface.o .libs/cairo-matrix.o .libs/cairo-path.o .libs/cairo-path-bounds.o .libs/cairo-path-data.o .libs/cairo-path-fill.o .libs/cairo-path-stroke.o .libs/cairo-pen.o .libs/cairo-polygon.o .libs/cairo-region.o .libs/cairo-slope.o .libs/cairo-spline.o .libs/cairo-surface.o .libs/cairo-traps.o .libs/cairo-pattern.o .libs/cairo-unicode.o .libs/cairo-output-stream.o .libs/cairo-wideint.o .libs/cairo-meta-surface.o .libs/cairo-ft-font.o .libs/cairo-png.o .libs/cairo-xlib-surface.o .libs/cairo-xlib-screen.o -Wl,--whole-archive ../pixman/src/.libs/libpixman.a -Wl,--no-whole-archive  -lXrender -lX11 -lXext -lpng12 /usr/lib/libfontconfig.so /usr/lib/libfreetype.so -lz -lm  -march=athlon-xp -Wl,-soname -Wl,libcairo.so.2 -o .libs/libcairo.so.2.2.3
../pixman/src/.libs/libpixman.a: member ../pixman/src/.libs/libpixman.a(pixregion.o) in archive is not an object
collect2: ld returned 1 exit status
make[2]: *** [libcairo.la] Error 1
make[2]: Leaving directory `/var/tmp/portage/cairo-1.0.2/work/cairo-1.0.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/cairo-1.0.2/work/cairo-1.0.2'
make: *** [all] Error 2


my emerge --info:


[1] slyphon@willie> emerge --info                                                                                         ~
Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15.1.20060115 i686)
=================================================================
System uname: 2.6.15.1.20060115 i686 AMD Athlon(tm) XP 2800+
Gentoo Base System version 1.6.14
ccache version 2.3 [enabled]
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=athlon-xp -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache collision-protect distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 aim apache2 apm avi berkdb bitmap-fonts bzip2 crypt curl eds emboss encode expat fastcgi flash foomaticdb gd gif gpm gstreamer imap imlib jpeg kde libg++ libwww mad maildrop memlimit mikmod motif mp3 mpeg ncurses nls nptl ogg opengl oscar pam pcre pdflib perl png postgres python quicktime readline ruby samba sasl sdl spell sqlite sqlite3 ssl tcpd threads truetype truetype-fonts type1-fonts udev unicode usb user-homedirs vorbis xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

[Comment 1 Jonathan Simms 2006-03-05 01:05:01 UTC]

It seems that I can build cairo without errors if i omit "-O2" from my CFLAGS.

[Comment 2 Doug Goldstein (RETIRED) 2006-03-05 07:42:59 UTC]

I would have to say your toolchain is broken because there's hundreds of configurations that are the same as yours and work. For example, I have the same box at work and it works fine with -O2, which is infact one of the most stable opt flags.

[Comment 3 Jonathan Simms 2006-03-05 10:55:18 UTC]

(In reply to comment #2)
> I would have to say your toolchain is broken because there's hundreds of
> configurations that are the same as yours and work. For example, I have the
> same box at work and it works fine with -O2, which is infact one of the most
> stable opt flags.
> 

That may be true, but it's odd that i'm able to compile an entire system at -O2 without error but on this package, i'm repeatedly able to get it to break when -O2 is set and build when it's not.

[Comment 4 Steev Klimaszewski (RETIRED) 2006-05-18 00:26:52 UTC]

Does this still happen with 1.0.4?  Please reopen if it does