public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Justin Bronder <jsbronder@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: gentoo-x86 commit in sys-cluster/openmpi: ChangeLog openmpi-1.1.1.ebuild openmpi-1.2.4.ebuild
Date: Fri, 14 Dec 2007 09:53:35 -0500	[thread overview]
Message-ID: <20071214145335.GA16123@mejis.cold-front> (raw)
In-Reply-To: <47627362.7050902@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]

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.

-- 
Justin Bronder

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2007-12-14 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1J2dWi-0006Ue-Fk@stork.gentoo.org>
2007-12-13  9:18 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-cluster/openmpi: ChangeLog openmpi-1.1.1.ebuild openmpi-1.2.4.ebuild Donnie Berkholz
2007-12-14 10:24   ` Matthias Langer
2007-12-14 12:13     ` Sébastien Fabbro
2007-12-14 14:12       ` Matthias Langer
2007-12-14 16:16         ` Sébastien Fabbro
2007-12-14 17:12           ` Matthias Langer
2007-12-14 19:52             ` Sébastien Fabbro
2007-12-15  1:51               ` Duncan
2007-12-14 14:53       ` Justin Bronder [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071214145335.GA16123@mejis.cold-front \
    --to=jsbronder@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox