@top level Makefile should not set values for
environment variables FC, CC, FFLAGS (etc) but
use the ones that mpi_make sets.
That's not completely true... you CAN set FC, CC and so forth, in the Makefile. You should compile it with mpicc or mpif77 or whatever. It will use what values you provide for these variables.
Normally your makefile will look something like this:
hi,
1). i would like to know what is meant by environment variables?
2). is the number of envi variables is a constant number for unix systems?
3). how to see the list of envi variables (and the values of the envi variables)in a single command?
4). if this questions were already asked... (3 Replies)
hi,
I want to create a new EV(Environment Variable) through a c program and I done this thing through setenv() method. But the newly created EV is not permanent, i.e. when I exit from the program the EV also no longer lives. But I want to make it a permanent EV for the current user. Actually I... (6 Replies)
I've seen a few other threads like this, but they either went unanswered or failed to answer my question.
How do I set an environment variable in a Makefile?
What I'm trying to do is use GNU make to automate an ant build.
In order to run ant, I've got to first set a few environment... (1 Reply)
say i define an environment variable in a particular script (upgrade.sh).
my script is upgarde.sh and it calls another script try.sh. will this environment variable be accessible to try.sh also. if not how to I make environment variables global so that they can be used by any script. (2 Replies)
Hello!
For the moment some settings in my .bashrc contain the password of my company's firewall, which is not a good idea. I would like to use the string "PASSWORD" set in .bashrc and a script that changes all appearances of "PASSWORD" in the environment variables by the actual password (which... (4 Replies)
Below is the top of my Makefile. On one machine, I have mysql_config5, and another, I have mysql_config. In my .bashrc file of one UNIX machine, I added an alias so that that mysql_config5 is mysql_config, however, when I do make, it doesn't use that environment and I get compile errors, unless I... (1 Reply)
I have read tons of posts about how you can't set persisting environment variable in a child script of a shell and have it persist. The only way is to source a file as
% . <scriptname>
I am finding that true... but I know there is a way around it. I just don't know how. I worked for 6... (5 Replies)
Hi Experts,
Need your help in understanding the commands to setup the environment variables in hp-ux.
Beleive need to use either set,setenv or export.
I am confused between above three options, when to use which option?
On command line, I have tried both set and setenv but couldn't... (1 Reply)
Hi All,
I need to understand following three environment variables and their usages in HP Unix.
_M_ARENA_OPTS
_M_CACHE_OPTS
PTHREAD_SCOPE_SYSTEM
How does these environment variables influence multi threaded applciation and how do we decide the value of these variables? Is there... (0 Replies)
Discussion started by: angshuman
0 Replies
LEARN ABOUT REDHAT
hf77
HF77(1) LAM TOOLS HF77(1)NAME
hf77, mpif77 - Compile LAM FORTRAN programs.
SYNTAX
hf77 [-showme] ...
see f77(1) (or whatever your underlying FORTRAN compiler is) for all other options.
DESCRIPTION
hf77 is a convenience wrapper for the local native FORTRAN compiler. Translation of a LAM program requires the linkage of the LAM essen-
tial services libraries which may not reside in one of the standard search directories of ld(1). hf77 passes its arguments along to the
local native FORTRAN compiler along with the -L and -l options required by LAM/MPI programs. This includes all necessary options for ROMIO
and/or C++ bindings support (if ROMIO/C++ support was included when LAM was compiled).
mpif77 is now the same as hf77. See the NOTES section, below.
By default, hf77 uses the FORTRAN compiler that was selected when LAM was configured (with the --with-fc flag to ./configure) as the local
native FORTRAN compiler, but this can be overridden by the LAMHF77 environment variable.
OPTIONS -showme
Does not invoke the underlying FORTRAN compiler. Instead, it shows the command line that would be executed to compile the FORTRAN
program.
NOTES
Previous versions of hf77 did not automatically link in the MPI library. Starting with LAM version 6.3, since hf77 has become the de facto
LAM FORTRAN compiler, the -lmpi option is now automatically passed to the underlying compiler when linking LAM/MPI programs.
Previous versions of LAM included the mpif77 wrapper script to automatically pass -lmpi to hf77. This script is now obsolete since hf77
now includes -lmpi automatically. mpif77 is now a symbolic link to hf77 to ensure backward compatibility.
SEE ALSO f77(1), ld(1), lam-helpfile(1)LAM 6.5.8 November, 2002 HF77(1)