* 64 bit architecture detected, using g77. * None of the needed Fortran Compilers (g77) is installed. * To install one of these, choose one of the following steps: * [1] USE="fortran" emerge =sys-devel/gcc-3* !!! ERROR: dev-lang/R-2.1.1 failed. Call stack: ebuild.sh, line 1547: Called dyn_setup ebuild.sh, line 660: Called pkg_setup R-2.1.1.ebuild, line 45: Called fortran_pkg_setup fortran.eclass, line 173: Called need_fortran 'g77' fortran.eclass, line 107: Called die !!! Install a Fortran Compiler ! !!! If you need support, post the topmost build error, and the call stack if rel evant. >=R-2.2.1 (~amd64) will though
also important to note that gcc-3 is installed with the USE=fortran flag enabled but is not selected by default and therefore not usable with the "g77" name : laptop tmp # equery uses =sys-devel/gcc-3.4.5 | grep "+" +fortran laptop tmp # equery files =sys-devel/gcc-3.4.5 | grep g77 /usr/bin/g77-3.4.5 /usr/bin/x86_64-pc-linux-gnu-g77-3.4.5 /usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.5/info/g77.info.gz /usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.5/man/man1/g77.1.gz /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.5/g77 /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.5/x86_64-pc-linux-gnu-g77 laptop tmp # gcc-config -l [1] x86_64-pc-linux-gnu-3.4.5 [2] x86_64-pc-linux-gnu-3.4.5-hardened [3] x86_64-pc-linux-gnu-3.4.5-hardenednopie [4] x86_64-pc-linux-gnu-3.4.5-hardenednopiessp [5] x86_64-pc-linux-gnu-3.4.5-hardenednossp [6] x86_64-pc-linux-gnu-4.1.1 *
*** This bug has been marked as a duplicate of 121855 ***
this bug has been technically fixed for amd64 when R-2.2.1 was marked stable : *R-2.3.1 (02 Jun 2006) 02 Jun 2006; Danny van Dyk <kugelfang@gentoo.org> R-2.2.1.ebuild, +R-2.3.1.ebuild: Added R-2.3.1. Marked R-2.2.1 stable on amd64. but all other archs will be bitten by it if gcc-4.1.1 is declared stable, as the currently stable R package relies in the existence of the g77 binary which is removed when the user `gcc-config` the new gcc even if the gcc-3* package (and therefore g77-3*) is still installed
(In reply to comment #3) > but all other archs will be bitten by it if gcc-4.1.1 is declared stable Yeah, so what? It is stable? No. And won't be for quite a while. What are you exactly requesting here?
There is an open stabilisation bug right now for other arches to stabilise on that version. It will be stable long before GCC 4.1.* is. Mixing stable and ~arch doesn't always work - especially with toolchain issues. I see where your concern is. but the issue is being taken care of. Use the latest ~ R version or revert to a stable system.
stabilization to R-2.2.1 being tracked by bug 135318