Re: [OMPI users] USE mpi

2011-05-07 Thread Dmitry N. Mikushin
Tim, I certainly do not expect anything special, just normally "make install" should not have issues, if "make" passes fine, right? What we have with OpenMPI is this strange difference: if ./configure CC=icc, "make" works, and "make install" - does not; if ./configure CC=/full/path/to/icc, then bo

Re: [OMPI users] USE mpi

2011-05-07 Thread Tim Prince
On 5/7/2011 2:35 PM, Dmitry N. Mikushin wrote: didn't find the icc compiler Jeff, on 1.4.3 I saw the same issue, even more generally: "make install" cannot find the compiler, if it is an alien compiler (i.e. not the default gcc) - same situation for intel or llvm, for example. The workaround is

Re: [OMPI users] USE mpi

2011-05-07 Thread Dmitry N. Mikushin
> didn't find the icc compiler Jeff, on 1.4.3 I saw the same issue, even more generally: "make install" cannot find the compiler, if it is an alien compiler (i.e. not the default gcc) - same situation for intel or llvm, for example. The workaround is to specify full paths to compilers with CC=...

Re: [OMPI users] Mixing the FORTRAN and C APIs.

2011-05-07 Thread Jeff Squyres
On May 7, 2011, at 5:01 PM, Jeff Squyres wrote: > example, if you have to pass an MPI datatype down to PARPACK, you'd actually > need to pass MPI_Type_f2c(MPI_INTEGER), or MPI_Type_f2c(MPI_DOUBLE_PRECISION). Blarg -- I got these backwards. I should have said: > MPI_Type_c2f(MPI_INTEGER), or MP

Re: [OMPI users] USE mpi

2011-05-07 Thread Jeff Squyres
We iterated off-list -- the problem was that "sudo make install" didn't find the icc compiler, and therefore didn't complete properly. It seems that the ompi_info and mpif90 cited in this thread were from some other (broken?) OMPI installation. On May 7, 2011, at 3:01 PM, Steph Bredenhann w

Re: [OMPI users] Mixing the FORTRAN and C APIs.

2011-05-07 Thread Jeff Squyres
In addition to what Tim Prince said: 1. you can mix C and Fortran MPI function calls in a single program 2. as such, there's no reason for your C++ app to call mpi_init__() (for example) 3. you should be able to call *all* MPI C functions as you normally would 4. the only things that you shoul

Re: [OMPI users] USE mpi

2011-05-07 Thread Steph Bredenhann
Sorry, I missed the 2nd statement: Fortran90 bindings: yes Fortran90 bindings size: small Fortran90 compiler: gfortran Fortran90 compiler abs: /usr/bin/gfortran Fortran90 profiling: yes -- Steph Bredenhann On Sat, 2011-05-07 at 14:46 -0400, Jeff Squyres wrote: > ompi_info

Re: [OMPI users] USE mpi

2011-05-07 Thread Steph Bredenhann
The output is: ifort -I/opt/openmpi-1.4.3/include -pthread -I/opt/openmpi-1.4.3/lib -vec-report0 -O3 -r8 -assume byterecl 3k-1.for -c done --- Steph Bredenhann On Sat, 2011-05-07 at 14:46 -0400, Jeff Squyres wrote: > What is the output of > > /usr/bin/mpif90 -vec-report0 -O3 -r8 -assume byt

Re: [OMPI users] USE mpi

2011-05-07 Thread Jeff Squyres
What is the output of /usr/bin/mpif90 -vec-report0 -O3 -r8 -assume byterecl $FILENAME -c --showme And ompi_info | grep 90 On May 7, 2011, at 2:40 PM, Steph Bredenhann wrote: > Thanks for the quick feedback. > > My compile line is: > > /usr/bin/mpif90 -vec-report0 -O3 -r8 -assume byterec

Re: [OMPI users] USE mpi

2011-05-07 Thread Steph Bredenhann
Thanks for the quick feedback. My compile line is: /usr/bin/mpif90 -vec-report0 -O3 -r8 -assume byterecl $FILENAME -c I have built OMPI with IFORT. Regards --- Steph Bredenhann On Sat, 2011-05-07 at 14:26 -0400, Jeff Squyres wrote: > What is the compile line that you are using to compile y

Re: [OMPI users] USE mpi

2011-05-07 Thread Jeff Squyres
What is the compile line that you are using to compile your application? If you use "mpif90 ...", then the right compiler directive should be automatically added such that the mpi module will be found (assuming that your OMPI was installed with F90 support, that is). On May 7, 2011, at 2:09 PM

[OMPI users] USE mpi

2011-05-07 Thread Steph Bredenhann
I have compiled all my fortran source files successfully with openmpi 1.4.3 wrapper for ifort on Ubuntu 10.10, except the main progran file that contains the "include mpif.h" statement. It seems that the "include mpif.h" is deprecated and that one should now use "USE mpi". However, when compiling w

Re: [OMPI users] Help: HPL Problem

2011-05-07 Thread Lee Eric
Hey mate, I have installed glibc-devel and it seems good. I also checked the status of the lib files they are all exist. Eric On Sat, May 7, 2011 at 11:11 PM, Dmitry N. Mikushin wrote: > Eric, > > You have a link-time error complaining about the absence of some > libraries. At least two of them

Re: [OMPI users] Help: HPL Problem

2011-05-07 Thread Dmitry N. Mikushin
Eric, You have a link-time error complaining about the absence of some libraries. At least two of them libm and libdl must be provided by system, not by MPI implementation. Could you locate them in /usr/lib64? Also it should be useful to figure out if the problem is global or specific to HPL: do y

[OMPI users] Help: HPL Problem

2011-05-07 Thread Lee Eric
Hi, I encountered following error messages when I compiled HPL. make[2]: Entering directory `/pool/measure/hpl-2.0/testing/ptest/Linux_PII_FBLAS' /pool/MPI/openmpi/bin/mpif90 -DAdd__ -DF77_INTEGER=int -DStringSunStyle -I/pool/measure/hpl-2.0/include -I/pool/measure/hpl-2.0/include/Linux_PII_FBLA