@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 HPUX
standards
standards(5) File Formats Manual standards(5)NAME
standards - UNIX standards behavior on HP-UX
DESCRIPTION
HP-UX conforms to various UNIX standards. In some cases, these standards conflict. This manpage describes the methods that programmers
and users must follow to have an application conform and execute according to a particular UNIX standard.
UNIX Standard Conformant Programmer Environment
The following table lists feature test macros and environment variables that must be defined while compiling an application. Both a fea-
ture test macro and an environment variable must be defined while compiling the application so that the application conforms and executes
according to a particular UNIX standard. Otherwise, the behavior is undefined.
Standard Feature Test Macros to be Environment variable
defined during compilation to be set
UNIX 95 _XOPEN_SOURCE_EXTENDED=1 UNIX95 or
UNIX_STD=95 or
UNIX_STD=1995
UNIX 2003 _XOPEN_SOURCE=600 UNIX_STD=2003
The compiler uses the feature test macros to obtain the appropriate namespace from the header files. The compiler uses the environment
variable to link in an appropriate object file to the executable. Using the environment variable customizes libc to match UNIX standards
for various functions.
If an application has already been compiled for default HP-UX behavior or for one particular standard, and needs to change to a particular
UNIX standard behavior, recompile the application as specified in the above table.
For an HP-UX command to conform to a particular UNIX standard behavior, the application has to set the corresponding environment variable
as specified in the above table before executing that command.
UNIX Standard Conformant User Environment
To enable a particular UNIX standard conformant user environment, set the corresponding environment variable as defined in the above table.
EXAMPLES
The following examples shows an application example. To have the system be conformant to UNIX2003 behavior, set the environment variable
to and define the feature test macro before compilation.
The following example changes the command to have UNIX95 behavior by setting one of the environment variables to or to before executing
that command. There are three ways of setting the environment variable for UNIX95:
or
or
SEE ALSO cc(1), stdsyms(5).
standards(5)