After a recent upgrade to a new python 2.4.2 emerging pyopengl fails due to an extra spurious compiler flag -OPT:Olimit=0 (the compiler in use is gcc, not Intel's icc as shown in emerge info): (...) creating build/temp.linux-i686-2.4/src/interface_util gcc -fno-strict-aliasing -OPT:Olimit=0 -DNDEBUG -O3 -mcpu=pentium4 -march=pentium4 -msse3 -fomit-frame-pointer -funroll-loops -mfpmath=sse -ffast-math -pipe -fPIC -DGLX_PLATFORM -DNUMERIC -I/usr/include/python2.4 -I/usr/include -I/usr/local/include -I/usr/X11R6/include -I/usr/lib/tk8.4/include -I/usr/include/python2.4/Numeric -I/usr/include/python2.4/numarray -Isrc/gle/src -I/usr/include -I/usr/local/include -I/usr/X11R6/include -I/usr/lib/tk8.4/include -I/usr/include/python2.4/Numeric -I/usr/include/python2.4/numarray -Isrc/gle/src -c src/interface_util/interface_util.c -o build/temp.linux-i686-2.4/src/interface_util/interface_util.o cc1: error: invalid option `-OPT:Olimit=0' error: command 'gcc' failed with exit status 1 !!! ERROR: dev-python/pyopengl-2.0.0.44 failed. !!! Function distutils_src_compile, Line 35, Exitcode 1 !!! compilation failed !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13-gentoo-r5 i686) ================================================================= System uname: 2.6.13-gentoo-r5 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5-r2, 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.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -xP -ip -mtune=pentium4 -i_dynamic -I /opt/intel/compiler90/include" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -xP -ip -mtune=pentium4 -i_dynamic -I /opt/intel/compiler90/include" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mirror.nutsmaas.nl/gentoo/ http://gd.tuwien.ac.at/opsys/linux/gentoo/ http://gentoo.tiscali.nl/gentoo/" LANG="en_GB.UTF-8" LINGUAS="en_GB" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X aac alsa apm arts avi berkdb bitmap-fonts bonobo cdr cjk crypt cups curl divx4linux dvd eds emboss encode esd fam flac foomaticdb fortran gd gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile ifc imagemagick imlib immqt-bc ipv6 java joystick jpeg junit kde libg++ libwww lirc mad mikmod mjpeg mmx mmxext motif mozilla mp3 mpeg mysql nas ncurses nls nptl ogg oggvorbis openal opengl oss pam pdflib perl png ppds python qt quicktime readline real scanner sdl spell sse sse2 sse3 ssl svga tcltk tcpd tetex threads tiff truetype truetype-fonts type1-fonts udev unicode usb vorbis win32codecs xine xml xml2 xmms xv xvid zlib video_cards_radeon linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS
http://sourceforge.net/tracker/?func=detail&aid=1162001&group_id=5470&atid=105470 seems like this problem, we probably should include this patch. did you compile python 2.4 with icc?
yes, the python itself was compiled with icc. some of the various python utilities/extensions like pyopengl were compiled with gcc, the others, like pyode, compiled OK with icc. After reading your link from sourceforge I suppose the quick fix would be to recompile python with gcc and then try re-emerging pyopengl with gcc too. fortunately dev-python/visual, which is a real-time 3D graphics library for Python that I use most often, does not need pyopengl. thanks for your help, at least now it should be possible to use pyopengl by recompiling python with gcc. regards Chris
An update: after recompiling pyopengl with icc (the same compiler as python itself was compiled) everything is working fine. The icc was indeed giving warnings about ignoring the option '-O' but it compiled OK. When a new x86 stable python came out a few weeks ago, pyopengl refused to compile with icc. therefore I tried using gcc only to get these '-OPT:0limit=0' errors. However, today pyopengl has compiled successfully with icc and I have verified it to work correctly too. So there is no need for recompiling python with gcc. I'm changing the status of the bug to "fixed". In the future I guess it would be good if patch for the -OPT setting could be included in the python ebuild.
i think we should consider adding some sort of protection in case this happens. so i'm keeping this bug open. but thanks for your report back that things are back to normal.
ICC is being phased out in portage. As I can't test ICC issues myself and ICC itself is being removed from portage I'm not going to do anything further now. Hopefully upstream can resolve any ICC related issues.
