Re: [OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread Jeffrey Squyres
Right. The revamped fortran stuff is *coming* -- it's off in a Mercurial bitbucket right now. It's not on the trunk yet. It's here, if you care: https://bitbucket.org/jsquyres/mpi3-fortran On Feb 21, 2012, at 7:57 AM, Paul H. Hargrove wrote: > > > On 2/21/2012 2:55 AM, Jeff Squyres

Re: [OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread Jeffrey Squyres
On Feb 21, 2012, at 6:39 AM, TERRY DONTJE wrote: >> Heads up that in the upcoming fortran revamp, we *only* use FC. I.E., >> there's only mpifort wrapper compiler (mpif77 and mpif90 still exist, but >> only as sym links to mpifort, signifying that mpifort is the way of the >> future). >> >>

Re: [OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread TERRY DONTJE
On 2/21/2012 5:55 AM, Jeff Squyres (jsquyres) wrote: That is truly bizarre "make" behavior. Heads up that in the upcoming fortran revamp, we *only* use FC. I.E., there's only mpifort wrapper compiler (mpif77 and mpif90 still exist, but only as sym links to mpifort, signifying that mpifort

Re: [OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread Jeff Squyres (jsquyres)
That is truly bizarre "make" behavior. Heads up that in the upcoming fortran revamp, we *only* use FC. I.E., there's only mpifort wrapper compiler (mpif77 and mpif90 still exist, but only as sym links to mpifort, signifying that mpifort is the way of the future). This was done because there

Re: [OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread Paul H. Hargrove
Thanks, Ralph. Excellent point about not needing to use the "FC" name with its special (absurd?) behavior. -Paul On 2/21/2012 1:52 AM, Ralph Castain wrote: I went ahead and applied this, with a tweak. There is no reason to call our flag "FC" as all we use it for is to call the write wrapper.

Re: [OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread Ralph Castain
I went ahead and applied this, with a tweak. There is no reason to call our flag "FC" as all we use it for is to call the write wrapper. So I renamed it to something less problematic. On Feb 21, 2012, at 1:20 AM, Paul H. Hargrove wrote: > And while we are looking at examples/Makefile on

Re: [OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread Paul H. Hargrove
And while we are looking at examples/Makefile on Solaris-10, why are the F77 examples getting built w/ mpif90? Because w/ the Solaris make setting FC also silently sets F77 (yes, I am NOT kidding)! So, reordering the F77= and FC= lines in Makefile resolves that mis-behavior. Attached is my

[OMPI devel] non-portable code in examples/Makefile

2012-02-21 Thread Paul H. Hargrove
The addition on Monday of the Java cases to examples/Makefile has shown that the default "make" in Solaris-10 will stop on the first failed grep command in the "all" rule: $ make mpicc -g -o hello_c hello_c.c mpicc -g -o ring_c ring_c.c mpicc -g -o connectivity_c connectivity_c.c mpic++