There are those who really don't want to have to rebuild their compilers (especially their cross compilers) again when keywords such as fortran gets removed. Any ideas why fortran was removed as a keyword and intel's ifc mandated for emerge? It would have been nice to have some notice of this happening, thanks. Sorry if I am complaining but I'd like to know why this has to happen. Reproducible: Always
Hi Alex, we reordered the dependency chain. We depend now on any fortran compiler not only on gcc[fortran]. Strange atrtifect is, taht Although gcc[fortran] is set as number one choice, portage requests ifort to be emerged. I will test that. meanwhile, just emerge gcc[fortran] and virtual/fortran and you should be fine.
My test show, that portage want's to emerge gcc[gfortran] and not ifc. So generally the dependencies are resolved as expected. I can't see what is wrong on your system. If you had gcc[gfortran] emerged before, nothing should change for you.
Probably you add sys-devel/gcc -fortran to your /etc/portage/package.use
Yes, it still insists on installing ifort if sys-devel/gcc doesn't have fortran keyword set. This also effects cross compilers as well (crossdev will need to enable fortran keyword for compilers it builds)
I added fortran to default use again. Fixed now,
