-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bryan Green wrote:
> Speaking of ebuilds and fortran, I've been nosing around trying to get
> things working with lam-mpi (I'm actually just administering a machine that
> someone else is trying to use mpi on).
> From looking at the various ebuilds for lam-mpi, lapack, and blas, it looks
> like newer ebuilds use fortran.eclass, while older ones hardcode the
> fortran compiler they want to use into the ebuild.  There is no support
> whatsoever for Portland Group (pgf).

Pretty much. The optimal solution is to get pgf into the tree.

> To get everything working with pgf90, I had to setup some ebuilds in an
> overlay which, a) avoided fortran.eclass and b) removed the FC/F77
> hardcoding in the ebuilds for blas and lapack, so that my FC setting in
> make.conf would be used.

There is no hardcoding in blas/lapack-atlas 3.7.11, they should work fine.

> fortran.eclass has to be avoided, because it simply punts if the compiler
> you request is not in its hardcoded list of blessed compilers.
> It looks like fortran.eclass is a work in progress.  Anybody have more
> information on that?  I'm wondering if I can help so that I can pick a
> fortran compiler to use on a system, without having to hack ebuilds in a
> portage overlay.

Yeah, that's a QA issue to ensure that only compilers known to
successfully compile a package are usable for it. The best solution
would be to add an ebuild for portland group compilers and start getting
them into the FORTRAN="x y z" settings in various ebuilds.

fortran.eclass is mostly done and should be able to handle anything up
through gcc-4.x. Although it might be worth adding some variable to
allow compiler overrides to the known-good setting, such as in your
case, or with g95, xl compilers, or whatever else.

Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFENGnbXVaO67S1rtsRAvYLAKCQ2OFBBT8fjLmOhIA45X5NkLw/KQCfa7VF
4eep4hHvl4tBKknMfMX3N1k=
=4AiG
-----END PGP SIGNATURE-----
-- 
[email protected] mailing list

Reply via email to