Package Details: mpich 4.2.3-1

Git Clone URL: https://aur.archlinux.org/mpich.git (read-only, click to copy)
Package Base: mpich
Description: An improved implementation of the Message Passing Interface.
Upstream URL: https://mpich.org
Licenses: custom
Replaces: mpich2
Submitter: jedbrown
Maintainer: jedbrown
Last Packager: jedbrown
Votes: 89
Popularity: 0.38
First Submitted: 2012-12-31 21:25 (UTC)
Last Updated: 2024-11-07 17:21 (UTC)

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9

jedbrown commented on 2010-10-28 20:23 (UTC)

@tam1138 Do you have gfortran installed? Looks like it should be made a dependency. I don't want to remove support for Fortran because lots of users need it. I'll add PKG_CONFIG_PATH, thanks.

<deleted-account> commented on 2010-10-28 19:56 (UTC)

Also, it'd be swell if you could include an /etc/profile.d/mpich2 along these lines: export PATH=$PATH:/opt/mpich2/bin export MANPATH=$MANPATH:/opt/mpich2/man export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/opt/mpich2/lib/pkgconfig

<deleted-account> commented on 2010-10-28 19:16 (UTC)

Configure fails because of Fortran nonsense: configure: error: Fortran 90 support requires compatible Fortran 77 support. To force the use of the Fortran 90 compiler for Fortran 77, do not use configure option --disable-f77, and set the environment variable F77 to the name of the Fortran 90 compiler, or $FC. If you do not want any Fortran support, use configure options --disable-f77 and --disable-fc. I added "--disable-f77 --disable-fc" to the configure options in the PKGBUILD, and it seems to work fine.

jedbrown commented on 2010-10-24 10:55 (UTC)

The soname has changed with version 1.3, you will need to rebuild all packages that depend on mpich2. Hydra is now the default process manager. MPD and gforker are still available if you launch with mpiexec.{mpd,gforker}, but they should not be necessary.

jedbrown commented on 2010-10-19 10:17 (UTC)

New dependency is on python2. This version (1.2.1p1-2) has one other change you should be aware of. MPICH2 historically injects it's build-time CFLAGS into the mpicc wrapper, and similar for other wrappers. Since the default /etc/makepkg.conf contains optimization (-O2), /opt/mpich2/bin/mpicc (with no optimization flags) was still compiling with optimization. This package version does MPICH2LIB_CFLAGS="$CFLAGS"; unset CFLAGS so that the wrappers no longer include optimization flags. The mpich2 library is still built with whatever optimization was in CFLAGS. This new behavior is consistent with other wrapper compilers (e.g. /usr/bin/mpicc from openmpi) and friendlier for debugging because you don't have to always remember to use -O0.

<deleted-account> commented on 2010-10-19 07:34 (UTC)

Need to use --with-python=python2 instead of --with-python=python in configure line because of python migration.

jedbrown commented on 2010-08-30 12:42 (UTC)

The trouble is that MPI applications need to link a specific MPI (only the API is standardized, not the ABI). Even if the ABI was standardized, this would make the implementations conflict, which isn't nice because most developers want to have at least two implementations installed concurrently. The solution we're living with now is to that Open MPI is the blessed implementation installed in /usr, MPICH2 is installed at /opt/mpich2 and packages built against mpich2 are usually named foo-mpich2.

domanov commented on 2010-08-30 11:35 (UTC)

Dear packager, I think it would be of use if each mpi implementation (openmpi, mpich2, ...) contains the "provides=('mpi')" array. That way a lot of packages depending on MPI infrastructure and not on the specific flavor would be much easier to mantain. Or would it bring a huge matter of conflicts I cannot see right now? I post this same comment in the openmpi AUR thread. Cheers, domanov

« First ‹ Previous 1 .. 4 5 6 7 8 9