Jesse,

Ah - I had thought you were trying to use gfortran.  Now I think I know what the problem is.

Mac OS has a built in version of MPI and it is probably in your path.  mpif90 is defaulting to gfortran.   You need to make certain that mpif90 in your path points to the Intel compiler. (This probably means building OpenMPI if you've not done that already.)   I _think_ that there is an environment variable (MPIF90) to override this as well, but I don't have time to go look it up right now as I'm about to head home.

I'll check in again this evening in case this either did not help or you are encountering a different problem.

- Tom

On Jul 18, 2013, at 5:13 PM, Jesse Lopez <lopezj@stccmop.org> 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.F90
gfortran: realloc_lhs: No such file or directory
gfortran: uninit: No such file or directory
....

I'm a bit perplexed by the gfortran complaints. I also tried
make --debug=v MPI=YES F90=ifort F90_VENDOR=Intel 

But it doesn't reveal much beyond what I already know.  It's using Intel.mk and it dies when with the
command above.

which -a mpif90
/opt/intel/impi/4.1.0.024/intel64/bin/mpif90

Any ideas?

Thanks,
-Jesse


On Thu, Jul 18, 2013 at 3:46 PM, Tom Clune <thomas.l.clune@nasa.gov> 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.

- Tom

On Jul 18, 2013, at 4:41 PM, Jesse Lopez <lopezj@stccmop.org> 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 trouble 
with '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.

-Jesse


On 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.8

If 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,

- Tom
  

On Jul 18, 2013, at 3:49 PM, Jesse Lopez <lopezj@stccmop.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 linux

2. gfortran 4.4.6 on linux (I know, it's ancient)

3. gfortran 4.7.8 on os x 10.7

Any 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!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________
Pfunit-support mailing list
Pfunit-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pfunit-support

Thomas Clune, Ph. D.  <Thomas.L.Clune@nasa.gov>
Chief, Software Systems Support Office Code 610.3
NASA GSFC 301-286-4635
MS 610.8 B33-C128 <http://ssso.gsfc.nasa.gov>
Greenbelt, MD 20771







Thomas Clune, Ph. D.  <Thomas.L.Clune@nasa.gov>
Chief, Software Systems Support Office Code 610.3
NASA GSFC 301-286-4635
MS 610.8 B33-C128 <http://ssso.gsfc.nasa.gov>
Greenbelt, MD 20771







Thomas Clune, Ph. D.  <Thomas.L.Clune@nasa.gov>
Chief, Software Systems Support Office Code 610.3
NASA GSFC 301-286-4635
MS 610.8 B33-C128 <http://ssso.gsfc.nasa.gov>
Greenbelt, MD 20771