Oh - I did not read far enough. I now see you've already shown that mpif90 is pointing to the right compiler.I still think that somehow you are using the "wrong" mpif90, but I cannot explain why "which" is saying that you are not. Probably GNUmake is using slightly different environment variables.Please tryexport MPIF90=/opt/intel/impi/4.1.0.024/intel64/bin/mpif90and see if that fixes the problem. I know that years ago I had a lot of trouble flushing the builtin mpif90 out of my path, but no longer remember the steps I took.- TomOn Jul 18, 2013, at 5:13 PM, Jesse Lopez <email@example.com> wrote:Hi Tom,I'm explicitly providing the compiler and vendor.make all F90=ifort F90_VENDOR=Intel [good]make tests F90=ifort F90_VENDOR=Intel [good]make tests MPI=YES F90=ifort F90_VENDOR=Intel [bad]mpif90 -c -assume realloc_lhs -g -O0 -traceback -check uninit -check bounds -check stack -check uninit -DSTRINGIFY_OPERATOR -I../include -DUSE_MPI -DIntel -DLinux -I/state/partition1/home/lopezj/pFUnit/include -DLONG_PTR -DSTRINGIFY_OPERATOR -DIntel -o MpiContext.o MpiContext.F90gfortran: realloc_lhs: No such file or directorygfortran: uninit: No such file or directory....I'm a bit perplexed by the gfortran complaints. I also triedmake --debug=v MPI=YES F90=ifort F90_VENDOR=IntelBut it doesn't reveal much beyond what I already know. It's using Intel.mk and it dies when with thecommand above.which -a mpif90/opt/intel/impi/4.1.0.024/intel64/bin/mpif90Any ideas?Thanks,-JesseOn Thu, Jul 18, 2013 at 3:46 PM, Tom Clune <firstname.lastname@example.org> wrote:
Hi Jesse,The error log suggests that you are somehow getting Ifort compile flags with gfortran. So either you don't have F90=gfortran for that case or you have F90_VENDOR set to Intel.Seems unrelated to MPI.- TomOn Jul 18, 2013, at 4:41 PM, Jesse Lopez <email@example.com> wrote:Hi Tom,Thanks for the prompt response. I had in fact specified the F90*, so I was good there.I did successfully compile with ifort 13.0 as you suggested. But, I ran into some troublewith 'make tests MPI=YES' with complaints from gfortran!Any idea about the gfortran 4.7.3 error on OS X?Thanks again for your help.-JesseOn Thu, Jul 18, 2013 at 3:21 PM, Tom Clune <Thomas.L.Clune@nasa.gov> wrote:
Hi Jesse,For ifort, you probably need a more recent compiler, though gfortran 4.7.8 ought to have worked. We recommend ifort 13.x and gfortran 4.7/4.8If you can provide a log of what goes wrong with cases 1 and 2 we'll help trouble shoot. (Case 2 simply will not work.) One obvious thing that others have pointed out (and should go in the documentation once we push it to the repository): you need to define the variable F90 to be ifort/gfortran. Or you can use F90_VENDOR=Intel/GNU.Cheers,- TomOn Jul 18, 2013, at 3:49 PM, Jesse Lopez <firstname.lastname@example.org> wrote:------------------------------------------------------------------------------Hello all,I've just cloned pFUnit from the master branch on the sourceforge repository and I've been unable to successfully compile the code with a variety of compilers/platforms.1. ifort 12.1.0 on linux2. gfortran 4.4.6 on linux (I know, it's ancient)3. gfortran 4.7.8 on os x 10.7Any hints on how to get it compiled and working would be much appreciated.Thanks,-Jesse
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
Pfunit-support mailing list