First, (or last) LAM is completely different than MPI. There may be some kind of forward compatibility library, but only for the simplest of programs.
Second, (or "(3)") mpif77/mpif90 are essentially MPI macros for running different compilers that you have on your system. What program "mpif77" runs is dependent on your local configuration and some environment variables. Presumably you can change some environment variables to use ifort or f90. But that's not necessary -- just pass ifort the correct options for your MPI fortran header files and library. Doesn't your compute cluster have a local system administrator??
The answer to (1) is simple: you compile your f90 code once, and put the resulting .o files in a directory, say $HOME/objs. Then to include them, pass them to the full paths to the ifort command...
Now maybe you need one version for each compiler version. So you put the F90 version in $HOME/objs/f90/ and use this:
Hi, I have some questions about RHEL and CentOS download and installation.
(1) Is RHEL6.0 x86_64 beta downloaded from Red Hat site working fine?
(2) Where to download CentOS 5.5 DVD iso without using BitTorrent?
(3) What are the differences between these two images - CentOS 5.5 i386 and... (6 Replies)
Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured
server:
/etc/hosts.allow:
all : all
all :all@all
setup my /etc/exports file... (4 Replies)
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
marching into the new version of RHEL 6.0...
other than ext4 and /boot can be ext4 and "/" root filesystem can be encrypted...I can't see much more new features that are quite significant and practical than RHEL 5.0, kernel is still 2.6.18.xxxx
I wonder if it has newer tools to manage... (4 Replies)
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Hi All,
I am a Solaris administartor. I got in to a probelm with RHEL.
I thought someone can help me on this forum ..
Can we download/install packages on a Redhat server with yum with out registering on RHEL network or website ? (1 Reply)
Hello all, I am having a bit of an issue on my Spacewalk installation. Some amplifying information is that it is Spacewalk 2.3 installed on a RHEL 6 machine and I am attempting to install/update a RHEL 5 channel/repository. I am fairly new to Spacewalk so I am still learning but this is what I... (3 Replies)
I know this question might have been asked a lot but couldn't find anything that worked. From a windows machine 'A' I can only SSH into Linux server 'B' from where I can SSH into another Linux server 'C'. I need to be able to run GUI interfaces on server C which run on my Windows machine. I... (3 Replies)
Hi
We have RHEL 6.7 on an HP physical server and want to install RHEL 7 (not upgrade) on top of it by means of virtualization. Is it possible to install/configure RHEV/KVM virtualization on base RHEL 6.7 OS instance and then install RHEL 7 as a VM guest on it? If yes, could you please guide me... (1 Reply)
Discussion started by: magnus29
1 Replies
LEARN ABOUT REDHAT
hcc
HCC(1) LAM TOOLS HCC(1)NAME
hcc, mpicc, hcp, mpiCC - Compile LAM C/C++ programs.
SYNTAX
hcc [-showme] ...
hcp [-showme] ...
see cc(1) and CC(1) (or whatever your underlying C/C++ compilers are) for all other options.
DESCRIPTION
hcc and hcp are convenience wrappers for the local native C and C++ compilers. Translation of a LAM program requires the linkage of the
LAM specific libraries which may not reside in one of the standard search directories of ld(1). It also often requires the inclusion of
header files what may also not be found in a standard location. hcc passes its arguments to the local native C compiler along with the -I,
-L and -l options required by LAM programs. This includes all necessary options for ROMIO and/or C++ bindings support (if ROMIO/C++ sup-
port was included when LAM was compiled). hcp is similar, but invokes the native C++ compiler instead.
mpicc is now the same as hcc, just as mpiCC is now the same as hcp. See the NOTES section, below.
By default, hcc uses the C compiler that was selected when LAM was configured (with the --with-cc flag to ./configure, or by setting the
environment variable CC before ./configure was invoked) as the local native C compiler, but this can be overridden by the LAMHCC environ-
ment variable. Likewise, hcp uses the C++ compiler that was selected when LAM was configured (with the --with-cpp flag to ./configure, or
by setting the environment variable CXX before invoking ./configure) by default, but this can be overridden by the LAMHCP environment vari-
able.
OPTIONS -showme
Does not invoke the underlying C/C++ compiler. Instead, it shows the command line that would be executed to compile the C/C++ pro-
gram.
NOTES
Previous versions of hcc and hcp did not automatically link in the MPI library. Starting with LAM version 6.3, since hcc and hcp have
become the de facto LAM C and C++ compilers, the -lmpi option is now automatically passed to the underlying compiler when linking LAM/MPI
programs.
Previous versions of LAM included the mpicc and mpiCC wrapper scripts to automatically pass -lmpi to hcc and/or hcp. These scripts are now
obsolete since hcc and hcp now include -lmpi automatically. mpicc and mpiCC are now symbolic links to hcc and hcp, respectively, to ensure
backward compatibility.
SEE ALSO cc(1), CC(1), ld(1), lam-helpfile(5)LAM 6.5.8 November, 2002 HCC(1)