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