checking for i686-pc-linux-gnu-g77... (cached) i686-pc-linux-gnu-g77 checking whether we are using the GNU Fortran 77 compiler... (cached) no checking whether i686-pc-linux-gnu-g77 accepts -g... (cached) no checking how to get verbose linking output from i686-pc-linux-gnu-g77... configure: WARNING: compilation failed checking for Fortran libraries of i686-pc-linux-gnu-g77... checking for dummy main to link with Fortran libraries... none checking for Fortran name-mangling scheme... configure: error: cannot compile a simple Fortran program See `config.log' for more details. This error occurs during emerges of both stable fftw-3.0.1-r2 and testing fftw-3.1.1 Earlier in the configure, I saw these messages: checking for i686-pc-linux-gnu-g77 option to produce PIC... -fPIC checking if i686-pc-linux-gnu-g77 PIC flag -fPIC works... no checking if i686-pc-linux-gnu-g77 static flag -static works... no checking if i686-pc-linux-gnu-g77 supports -c -o file.o... no checking whether the i686-pc-linux-gnu-g77 linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... gcc-config error: i686-pc-linux-gnu-g77 wrapper: Unable to determine executable. CTARGET=i686-pc-linux-gnu exec=g77 and while following the GCC general upgrade procedure yesterday, I noticed that last message occurring during the configure stage in many packages, though they generally seemed to build okay.
Created attachment 89478 [details] fftw-3.1.1 configure log
Looks like it's this dumb breakage in eselect yet again. Edit the files in /etc/eselect/compiler/ and remove the lines like alias_gfortran=g77 and alias_g77=gfortran. Also delete /usr/bin/*g77.
Oh also looks like you're using confcache. Edit /var/tmp/confcache/config.cache to remove the line with g77 in it.
I didn't have any of those alias lines in i686-pc-linux-gnu-4.1.1 - only in the old i686-pc-linux-gnu-3.4.6.conf file - and I'm not using confcache (it's not installed and there's no /var/tmp/confcache/) but I did 'rm /usr/bin/*g77' and that seems to have done the trick. Thanks very much Donnie :)
Reopening to resolve properly.
*** This bug has been marked as a duplicate of 136363 ***