To dave, from the installation guide I found, it seemed I couldnt just directly download it from the package list, but rather Id need to use the mpicc wrapper to compile and install. I also wanted to see if I could build it from the installation guide, sorta learn how the whole process worked.
To guilles, do I need to download open mpi directly from the site to obtain the mpicc and to get the current version? Thank you both for your responces On Aug 31, 2016 11:00 AM, <users-requ...@lists.open-mpi.org> wrote: > Send users mailing list submissions to > users@lists.open-mpi.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://rfd.newmexicoconsortium.org/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-requ...@lists.open-mpi.org > > You can reach the person managing the list at > users-ow...@lists.open-mpi.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: Certain files for mpi missing when building mpi4py > (Gilles Gouaillardet) > 2. Re: Certain files for mpi missing when building mpi4py (Dave Love) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 31 Aug 2016 11:22:23 +0900 > From: Gilles Gouaillardet <gil...@rist.or.jp> > To: Open MPI Users <users@lists.open-mpi.org> > Subject: Re: [OMPI users] Certain files for mpi missing when building > mpi4py > Message-ID: <1fb7e491-be43-c59c-07d4-5890f6793...@rist.or.jp> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Sam, > > at first you mentionned Open MPI 1.7.3. > > though this is now a legacy version, you posted to the right place. > > > then you > > # python setup.py build --mpicc=/usr/lib64/mpich/bin/mpicc > > > this is mpich, which is a very reputable MPI implementation, but not > Open MPI. > > so i do invite you to use Open MPI mpicc, and try again. > > > Cheers, > > > Gilles > > > PS > > with Open MPI, you can > > mpirun -showme ... > > in order to display how the compiler (e.g. gcc) is invoked > > with mpich, that would be (there might be a better option i am unaware of) > > mpirun -v ... > > if mpich mpicc wrapper is not broken, it should include a path to mpi.h > > (e.g. -I/usr/lib64/mpich/include) > > and unless a package is missing (mpich-devel ?), that file should exist > > > you cannot use Open MPI mpi.h with mpich, nor the other way around, and > you should not copy this file to an other place > > (that should not be needed at all) > > On 8/31/2016 4:22 AM, Mahdi, Sam wrote: > > HI everyone, > > > > I am using a linux fedora. I downloaded/installed > > openmpi-1.7.3-1.fc20(64-bit) and openmpi-devel-1.7.3-1.fc20(64-bit). > > As well as pypar-openmpi-2.1.5_108-3.fc20(64-bit) and > > python3-mpi4py-openmpi-1.3.1-1.fc20(64-bit). The problem I am having > > is building mpi4py using the mpicc wrapper. I have installed and > > untarred mpi4py from https://pypi.python.org/pypi/mpi4py#downloads. I > > went to compile it and received this error. I typed in > > python setup.py build --mpicc=/usr/lib64/mpich/bin/mpicc > > This was the output > > running build > > running build_src > > running build_py > > running build_clib > > MPI configuration: [mpi] from 'mpi.cfg' > > MPI C compiler: /usr/lib64/mpich/bin/mpicc > > running build_ext > > MPI configuration: [mpi] from 'mpi.cfg' > > MPI C compiler: /usr/lib64/mpich/bin/mpicc > > checking for MPI compile and link ... > > /usr/lib64/mpich/bin/mpicc -pthread -fno-strict-aliasing -O2 -g -pipe > > -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong > > --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic > > -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall > > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong > > --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic > > -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c > > _configtest.c -o _configtest.o > > _configtest.c:2:17: fatal error: mpi.h: No such file or directory > > #include <mpi.h> > > ^ > > compilation terminated. > > failure. > > removing: _configtest.c _configtest.o > > error: Cannot compile MPI programs. Check your configuration!!! > > > > I found the file mpi.h and decided to directly export it to the path. > > export > > path=$path:/usr/lib64/python2.7/site-packages/mpich/mpi4py/ > include/mpi4py/mpi4py.h > > But this did not resolve the include mpi.h dilemma. I still recieve > > the same error when attempting to build mpi4py using mpicc wrapper. > > > > Thank you in advance > > -Sam > > > > > > > > _______________________________________________ > > users mailing list > > users@lists.open-mpi.org > > https://rfd.newmexicoconsortium.org/mailman/listinfo/users > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <https://rfd.newmexicoconsortium.org/mailman/private/users/ > attachments/20160831/b2e6f5ca/attachment.html> > > ------------------------------ > > Message: 2 > Date: Wed, 31 Aug 2016 12:55:18 +0100 > From: Dave Love <d.l...@liverpool.ac.uk> > To: Open MPI Users <users@lists.open-mpi.org> > Subject: Re: [OMPI users] Certain files for mpi missing when building > mpi4py > Message-ID: <878tvd5f15....@pc102091.liv.ac.uk> > Content-Type: text/plain > > "Mahdi, Sam" <sam.mahdi....@my.csun.edu> writes: > > > HI everyone, > > > > I am using a linux fedora. I downloaded/installed > > openmpi-1.7.3-1.fc20(64-bit) and openmpi-devel-1.7.3-1.fc20(64-bit). As > > well as pypar-openmpi-2.1.5_108-3.fc20(64-bit) and > > python3-mpi4py-openmpi-1.3.1-1.fc20(64-bit). The problem I am having is > > building mpi4py using the mpicc wrapper. > > Why build it when you have the package? > > If you do need to rebuild it for some reason, get the source rpm and > look at the recipe in the .spec file, or edit the .spec and just use > rpmbuild. > > [I assume there's a good reason for F20, but it's three versions > obsolete.] > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/users > > ------------------------------ > > End of users Digest, Vol 3592, Issue 1 > ************************************** >
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
