On 6/26/2011 4:01 PM, Dale wrote:
Michael Schreckenbauer wrote:
Am Sonntag, 26. Juni 2011, 10:28:47 schrieb Dale:
Michael Schreckenbauer wrote:
Try euse -I fortran.
If anything besides gcc pops up, you should have one.
That doesn't appear to work like it should then. I get this:
root@fireball / # euse -I fortran
global use flags (searching: fortran)
************************************************************
[+ CD ] fortran - Adds support for fortran (formerly f77)
Installed packages matching this USE flag:
sys-devel/gcc-4.4.5
local use flags (searching: fortran)
************************************************************
no matching entries found
root@fireball / #
Thing is, I switched it back and programs on here now need
fortran to build. So, euse is not reporting it but R and
Cantor won't build without fortran. Basically, euse should
also report R and cantor but it isn't. If mine isn't
reporting that, then Peter's may not either.
Neither of those packages has a "fortran" USE flag, and
cantor doesn't "know" anything about FORTRAN.
cantor has an R USE flag, to switch it's R backend on/off. R
doesn't have a USE flag for FORTRAN because that would be
pointless -- it *requires* an f77 compiler, so it depends on
virtual/fortran unconditionally.
You would probably be better off using
root@platypus ~ # equery depends virtual/fortran
dev-python/numpy-1.6.0 (lapack ? virtual/fortran)
You will probably have both R and blas in that list as well.
If so, you will need to continue to enable gcc[fortran] to
build those.
(The fact that gcc has a fortran USE flag is only relevant
because it's the default compiler; you could also
potentially have ifc installed to satisfy virtual/fortran,
rendering gcc's USE flag irrelevant.)
--Mike
