| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Bryan Green wrote: |
| 5 |
> Speaking of ebuilds and fortran, I've been nosing around trying to get |
| 6 |
> things working with lam-mpi (I'm actually just administering a machine that |
| 7 |
> someone else is trying to use mpi on). |
| 8 |
> From looking at the various ebuilds for lam-mpi, lapack, and blas, it looks |
| 9 |
> like newer ebuilds use fortran.eclass, while older ones hardcode the |
| 10 |
> fortran compiler they want to use into the ebuild. There is no support |
| 11 |
> whatsoever for Portland Group (pgf). |
| 12 |
|
| 13 |
Pretty much. The optimal solution is to get pgf into the tree. |
| 14 |
|
| 15 |
> To get everything working with pgf90, I had to setup some ebuilds in an |
| 16 |
> overlay which, a) avoided fortran.eclass and b) removed the FC/F77 |
| 17 |
> hardcoding in the ebuilds for blas and lapack, so that my FC setting in |
| 18 |
> make.conf would be used. |
| 19 |
|
| 20 |
There is no hardcoding in blas/lapack-atlas 3.7.11, they should work fine. |
| 21 |
|
| 22 |
> fortran.eclass has to be avoided, because it simply punts if the compiler |
| 23 |
> you request is not in its hardcoded list of blessed compilers. |
| 24 |
> It looks like fortran.eclass is a work in progress. Anybody have more |
| 25 |
> information on that? I'm wondering if I can help so that I can pick a |
| 26 |
> fortran compiler to use on a system, without having to hack ebuilds in a |
| 27 |
> portage overlay. |
| 28 |
|
| 29 |
Yeah, that's a QA issue to ensure that only compilers known to |
| 30 |
successfully compile a package are usable for it. The best solution |
| 31 |
would be to add an ebuild for portland group compilers and start getting |
| 32 |
them into the FORTRAN="x y z" settings in various ebuilds. |
| 33 |
|
| 34 |
fortran.eclass is mostly done and should be able to handle anything up |
| 35 |
through gcc-4.x. Although it might be worth adding some variable to |
| 36 |
allow compiler overrides to the known-good setting, such as in your |
| 37 |
case, or with g95, xl compilers, or whatever else. |
| 38 |
|
| 39 |
Thanks, |
| 40 |
Donnie |
| 41 |
-----BEGIN PGP SIGNATURE----- |
| 42 |
Version: GnuPG v1.4.2.2 (GNU/Linux) |
| 43 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 44 |
|
| 45 |
iD8DBQFENGnbXVaO67S1rtsRAvYLAKCQ2OFBBT8fjLmOhIA45X5NkLw/KQCfa7VF |
| 46 |
4eep4hHvl4tBKknMfMX3N1k= |
| 47 |
=4AiG |
| 48 |
-----END PGP SIGNATURE----- |
| 49 |
-- |
| 50 |
gentoo-cluster@g.o mailing list |
Archives