public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Bronder" <jsbronder@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sys-cluster/mpich/
Date: Mon, 20 Apr 2015 17:27:34 +0000 (UTC)	[thread overview]
Message-ID: <1429550833.c168d37f72be1c726ab7b02efea26c2480f3a124.jsbronder@gentoo> (raw)

commit:     c168d37f72be1c726ab7b02efea26c2480f3a124
Author:     Justin Bronder <jsbronder <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 20 17:27:13 2015 +0000
Commit:     Justin Bronder <jsbronder <AT> gentoo <DOT> org>
CommitDate: Mon Apr 20 17:27:13 2015 +0000
URL:        https://gitweb.gentoo.org/proj/sci.git/commit/?id=c168d37f

bump

Package-Manager: portage-2.2.14

 sys-cluster/mpich/ChangeLog             |   5 ++
 sys-cluster/mpich/mpich-3.1.4-r1.ebuild | 122 ++++++++++++++++++++++++++++++++
 2 files changed, 127 insertions(+)

diff --git a/sys-cluster/mpich/ChangeLog b/sys-cluster/mpich/ChangeLog
index 8630c01..d3577a5 100644
--- a/sys-cluster/mpich/ChangeLog
+++ b/sys-cluster/mpich/ChangeLog
@@ -2,6 +2,11 @@
 # Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+*mpich-3.1.4-r1 (20 Apr 2015)
+
+  20 Apr 2015; Justin Bronder <jsbronder@gentoo.org> +mpich-3.1.4-r1.ebuild:
+  bump
+
 *mpich-3.1.3-r99 (20 Apr 2015)
 
   20 Apr 2015; Justin Bronder <jsbronder@gentoo.org> +mpich-3.1.3-r99.ebuild,

diff --git a/sys-cluster/mpich/mpich-3.1.4-r1.ebuild b/sys-cluster/mpich/mpich-3.1.4-r1.ebuild
new file mode 100644
index 0000000..ee89bd1
--- /dev/null
+++ b/sys-cluster/mpich/mpich-3.1.4-r1.ebuild
@@ -0,0 +1,122 @@
+# Copyright 1999-2015 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: $
+
+EAPI=5
+
+FORTRAN_NEEDED=fortran
+
+inherit fortran-2 mpi
+
+MY_PV=${PV/_/}
+DESCRIPTION="A high performance and portable MPI implementation"
+HOMEPAGE="http://www.mpich.org/"
+SRC_URI="http://www.mpich.org/static/downloads/${PV}/${P}.tar.gz"
+
+SLOT="0"
+LICENSE="mpich"
+KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+IUSE="+cxx doc fortran mpi-threads romio threads"
+
+COMMON_DEPEND="
+	dev-libs/libaio
+	>=sys-apps/hwloc-1.9
+	romio? ( net-fs/nfs-utils )
+	$(mpi_imp_deplist)"
+
+DEPEND="${COMMON_DEPEND}
+	dev-lang/perl
+	sys-devel/libtool"
+
+RDEPEND="${COMMON_DEPEND}"
+
+S="${WORKDIR}"/${PN}-${MY_PV}
+
+pkg_setup() {
+	FORTRAN_STANDARD="77 90"
+	fortran-2_pkg_setup
+	MPI_ESELECT_FILE="eselect.mpi.mpich"
+
+	if use mpi-threads && ! use threads; then
+		ewarn "mpi-threads requires threads, assuming that's what you want"
+	fi
+}
+
+src_prepare() {
+	# Using MPICHLIB_LDFLAGS doesn't seem to fully work.
+	sed -i 's| *@WRAPPER_LDFLAGS@ *||' \
+		src/packaging/pkgconfig/mpich.pc.in \
+		src/env/*.in \
+		|| die
+}
+
+src_configure() {
+	local c="--enable-shared"
+	local hydra_c="--with-hwloc-prefix=/usr"
+
+	# The configure statements can be somewhat confusing, as they
+	# don't all show up in the top level configure, however, they
+	# are picked up in the children directories.  Hence the separate
+	# local vars.
+
+	if use mpi-threads; then
+		# MPI-THREAD requries threading.
+		c="${c} --with-thread-package=pthreads"
+		c="${c} --enable-threads=runtime"
+	else
+		if use threads ; then
+			c="${c} --with-thread-package=pthreads"
+		else
+			c="${c} --with-thread-package=none"
+		fi
+		c="${c} --enable-threads=single"
+	fi
+
+	if ! mpi_classed; then
+		c="${c} --sysconfdir=${EPREFIX}/etc/${PN}"
+		c="${c} --docdir=${EPREFIX}/usr/share/doc/${PF}"
+	else
+		c="${c} --docdir=$(mpi_root)/usr/share/doc/${PF}"
+	fi
+
+	export MPICHLIB_CFLAGS=${CFLAGS}
+	export MPICHLIB_CPPFLAGS=${CPPFLAGS}
+	export MPICHLIB_CXXFLAGS=${CXXFLAGS}
+	export MPICHLIB_FFLAGS=${FFLAGS}
+	export MPICHLIB_FCFLAGS=${FCFLAGS}
+	export MPICHLIB_LDFLAGS=${LDFLAGS}
+	unset CFLAGS CPPFLAGS CXXFLAGS FFLAGS FCFLAGS LDFLAGS
+
+	econf $(mpi_econf_args) ${c} \
+		--with-pm=hydra \
+		--disable-fast \
+		--enable-versioning \
+		${hydra_c} \
+		$(use_enable romio) \
+		$(use_enable cxx) \
+		$(use_enable fortran f77) \
+		$(use_enable fortran fc)
+}
+
+src_test() {
+	emake -j1 check
+}
+
+src_install() {
+	local d=$(echo ${ED}/$(mpi_root)/ | sed 's,///*,/,g')
+
+	default
+
+	mpi_dodir /usr/share/doc/${PF}
+	mpi_dodoc COPYRIGHT README{,.envvar} CHANGES RELEASE_NOTES
+	mpi_newdoc src/pm/hydra/README README.hydra
+	if use romio; then
+		mpi_newdoc src/mpi/romio/README README.romio
+	fi
+
+	if ! use doc; then
+		rm -rf "${d}"usr/share/doc/${PF}/www*
+	fi
+
+	mpi_imp_add_eselect
+}


             reply	other threads:[~2015-04-20 17:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 17:27 Justin Bronder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-29 20:49 [gentoo-commits] proj/sci:master commit in: sys-cluster/mpich/ Christoph Junghans
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2016-08-29 20:45 Justin Bronder
2015-12-21 13:48 Justin Bronder
2015-11-21 15:14 Christoph Junghans
2015-04-20 17:11 Justin Bronder
2015-04-20 17:11 Justin Bronder
2015-02-21  2:46 Christoph Junghans
2015-02-20  2:01 Christoph Junghans
2015-02-17  0:13 Christoph Junghans

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=1429550833.c168d37f72be1c726ab7b02efea26c2480f3a124.jsbronder@gentoo \
    --to=jsbronder@gentoo.org \
    --cc=gentoo-commits@lists.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