From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 17:07:45 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 418B1129 for ; Wed, 10 Jul 2013 17:07:45 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 264E21E34 for ; Wed, 10 Jul 2013 17:07:45 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6AH7BQg059568; Wed, 10 Jul 2013 10:07:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6AH7BGB059567; Wed, 10 Jul 2013 10:07:11 -0700 (PDT) (envelope-from sgk) Date: Wed, 10 Jul 2013 10:07:11 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: why fortran mailing list? Message-ID: <20130710170711.GA59476@troutmask.apl.washington.edu> References: <20130709231808.GA92444@troutmask.apl.washington.edu> <201307100759.r6A7xqsK098965@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307100759.r6A7xqsK098965@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 17:07:45 -0000 On Wed, Jul 10, 2013 at 08:59:52AM +0100, Anton Shterenlikht wrote: > From sgk@troutmask.apl.washington.edu Wed Jul 10 00:33:34 2013 > >> OpenMPI is >> the only Fortran code that I routinely build outside of the >> ports. > > Please elaborate. > I don't know much about the differences between OpenMPI > and mpich. The latter seems to work: > > # pkg info -xr mpi > mpich2-1.3.2.p1_1,5: > scotch-5.1.12.b.e > astk-serveur-1.11.0 > blocksolve95-3.0_10 > ParMetis-4.0_1 I've used both mpich2 and OpenMPI on i386 and amd64 systems. In the testing I've done with my applications, OpenMPI simply out performed mpich2. This was a while ago, so things may have changed. OpenMPI just works. The one issue I had with OpenMPI was resolved within a day. Note, I do not use ports/net/openmpi. I download the latest version from the OpenMPI, unpack it, run configure and install. -- Steve