i found that while emerging sweep (which checks for a valid g77). gcc -version reports 3.2.3-3 while g77 was some old 2.95 build. (i set this bug to minor, as none seems to be concerned so far;-) Reproducible: Always Steps to Reproduce: i changed /usr/bin/gcc-config line 214 (function switch_function) from for x in gcc cpp cc c++ g++ "${REAL_CHOST}-gcc" "${REAL_CHOST}-c++" "${REAL_CHOST}-g++" to for x in gcc cpp cc c++ g++ g77 "${REAL_CHOST}-gcc" "${REAL_CHOST}-c++" "${REAL_CHOST}-g++" "${REAL_CHOST}-g77" Actual Results: works fine afterwards (did not test backswitch to 2.95 Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.2.5-r7,2.3.2-r3, 2.4.21) ================================================================= System uname: 2.4.21 i686 Intel(R) Pentium(R) III Mobile CPU 1000MHz Gentoo Base System version 1.4.3.10p1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/home/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="gtk2 directfb gtkhtml alsa tetex aalib nas bonobo tcltk guile perl esd mozilla ldap cdr scanner x86 oss apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gpm gtk imlib java jpeg kde -gnome libg++ libwww mad mikmod mmx -motif mpeg ncurses nls oggvorbis opengl pam pdflib png python qt quicktime readline sdl slang spell ssl dvd svga tcpd truetype X xml2 xmms xv zlib acl dvdr"
can someone commit this? not switching g77 breaks some builds for me...
Roland, Is this bug still a problem?
This is definitely still broken. Even worse, though, is that (at least with gcc-3.3.3), gcc-config doesn't create a g77 stub in /usr/bin, so even if you have f77 in your USE flags, you don't end up with a g77 binary. Here's a patch for the 1.3.5-r1 ebuild (note: I don't use objective C, so I don't know if "objc" is the correct name to use on that line): --- gcc-config-1.3.5-r1.ebuild 2004-05-25 15:01:56.775928067 -0400 +++ gcc-config-1.3.5-r1a.ebuild 2004-05-25 12:44:45.036037481 -0400 @@ -46,7 +46,11 @@ newexe ${WORKDIR}/wrapper cpp exeinto /usr/bin - for x in gcc cpp cc c++ g++ ${CHOST}-gcc ${CHOST}-c++ ${CHOST}-g++ + gcc_bins="gcc cpp cc c++ g++ ${CHOST}-gcc ${CHOST}-c++ ${CHOST}-g++" + use f77 && gcc_bins="${gcc_bins} g77 ${CHOST}-g77" + use objc && gcc_bins="${gcc_bins} objc ${CHOST}-objc" + use java && gcc_bins="${gcc_bins} gcj ${CHOST}-gcj" + for x in $gcc_bins do newexe ${WORKDIR}/wrapper ${x} done
Ok, this should be fixed with gcc-config-1.3.6 ... reopen if issues.