Oh, clear now, thank you!
2011/5/8 Steph Bredenhann
> Jeff is correct. The Intel environmental variables are either set in
> /etc/profile or /user/.bashrc (or manually). Root sets its own environmental
> variables and therefore the key is to make sure that the environmental
> variables are set
Jeff is correct. The Intel environmental variables are either set
in /etc/profile or /user/.bashrc (or manually). Root sets its own
environmental variables and therefore the key is to make sure that the
environmental variables are set before an installation as root is done,
i.e.:
source /opt/intel
Make all gets the same environment as make install (assuming you do it in the
same shell). But if you sudo make install, the environment may be different -
it may not inherit everything from your environment.
I advised the user to "sudo -s" and ten setup the compiler environment and then
run m
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
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
> 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=...
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
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
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
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
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
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
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
13 matches
Mail list logo
