1 |
On 14/12/07 12:13 +0000, Sébastien Fabbro wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> On 14/12/07 10:24, Matthias Langer wrote: |
6 |
> >> On 02:10 Thu 13 Dec , Justin Bronder (jsbronder) wrote: |
7 |
> >>> 1.1 sys-cluster/openmpi/openmpi-1.2.4.ebuild |
8 |
> >>> |
9 |
> >>> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-cluster/openmpi/openmpi-1.2.4.ebuild?rev=1.1&view=markup |
10 |
> >>> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-cluster/openmpi/openmpi-1.2.4.ebuild?rev=1.1&content-type=text/plain |
11 |
> > |
12 |
> > Why have you removed the "ifc" USE flag (as well as a few others), that |
13 |
> > was present in the ebuilds that can still be found at bug 166787? |
14 |
> |
15 |
> For icc and f90-typesafe, I advised him to do so on #gentoo-science. |
16 |
> |
17 |
> ifc/icc use flags should be avoided (see bug #97929). |
18 |
> Disabling f90-typesafe did not make much sense as a use flag once you |
19 |
> have the fortran one enabled, but why --with-mpi-f90-size=medium" |
20 |
> and "--with-f90-max-array-dim=4" disappeared I don't know. |
21 |
|
22 |
For the first, chalk this up to my own inexperience with fortran. Is this |
23 |
going to be common enough to justify a USE flag? Would it be better to just |
24 |
enable it by default when gfortran is not being used given that is slows |
25 |
compilation down significantly? |
26 |
|
27 |
In the case of the latter, that is the default when no options are passed. |
28 |
|
29 |
> For the gm and gx flags, I don't know, and there is still a nocxx one. |
30 |
|
31 |
There are no ebuilds for the above packages. I submitted them at the same |
32 |
time I commented on the openmpi bug, but no longer have access to that |
33 |
hardware. If someone does and would be willing to work with me on finishing |
34 |
up those ebuilds, please contact me. |
35 |
|
36 |
-- |
37 |
Justin Bronder |