Оценок - 0, средний балл: 0
(
)
)
|
К этому устройству также есть другие инструкции:
Компьютеры - HP Integrity NonStop H-Series (16.73 mb)
Компьютеры - HP Integrity NonStop H-Series (957.56 kb)
Компьютеры - HP Integrity NonStop H-Series (881.66 kb)
Компьютеры - HP Integrity NonStop H-Series (965.62 kb)
Компьютеры - HP Integrity NonStop H-Series (676.93 kb)
Компьютеры - HP Integrity NonStop H-Series (393.72 kb)
Компьютеры - HP Integrity NonStop H-Series (776.57 kb)
Фрагмент инструкции
builds the server with a function pqr, which can have a service association. tpadvertise() could be used
to map a service name to the pqr function.
A filename can be specified with the -s option by prefacing the filename with the '@' character. Each line of
this file is treated as an argument to the -s option. You may put comments in this file. All comments must
start with the '#' character. This file can be used to specify all the functions in the server that may have
services mapped to them.
The -s option may appear several times. Note that services beginning with the character '.' are reserved for
system use, and buildserver will fail if the -s option is used to include such a service in the server.
-C
Specifies COBOL compilation. buildserver normally uses the default C compiler to produce the a.out.
In order to allow for the specification of an alternate compiler, buildserver checks for the existence of a
shell variable named CC. If CC does not exist in buildserver's environment, or if it is the string " ",
buildserver uses the default C compiler as the compiler. If CC does exist in the environment, its value is
taken to be the name of the compiler to be executed. Likewise, the shell variable CFLAGS is taken to contain
a set of parameters to be passed to the compiler.
-k
Keeps the server "main" stub. buildserver generates a "main" stub with data structures such as the
service table and a main() function. This is normally compiled and then removed when the server is built.
This option indicates that the source file should be kept (to see what the source file name is, use the -v
option). NOTE: the generated contents of this file may change from release to release. DO NOT count on the
data structures and interfaces exposed in this file. This option is provided to aid in debugging of build
problems.
Environment Variables
TUXDIR
buildserver uses the environment variable TUXDIR to find the System/T libraries and include files to use
during compilation of the server process.
CC
buildserver normally uses the default C language compilation command to produce the server
executable. The default C language compilation command is defined for each supported operating system
platform and is defined as C89(1) for Open System Services. In order to allow for the specification of an
alternate compiler, buildserver checks for the existence of an environment variable named CC. If CC
does not exist in buildserver's environment, or if it is the string " ", buildserver will use the default
C language compiler. If CC does exist in the environment, its value is taken to be the name of the compiler to
be executed.
CFLAGS
The environment variable CFLAGS is taken to contain a set of arguments to be passed as part of the compiler
command line. This is in addition to the command line option "-I TUXDIR/include " and others, passed
automatically by buildserver. To see the options passed to the compiler, and by the compiler to the
linker, use the buildserver -v option.
If -WBstatic is specified in the variable, then static linking is performed using the library archives in
$TUXDIR/lib. Otherwise, the server dynamically links to user libraries when it executes. NonStop Tuxedo
DLLs are contained in the directory $TUXDIR/lib and have filenames ending with .so.
ALTCC
When the -C option is specified for COBOL compilation, buildserver normally uses the OSS COBOL85
compiler frontend "ecobol" found using the OSS $PATH, which calls/G/system/system/ecobol to
...Эта инструкция также подходит к моделям:
Компьютеры - HP Integrity NonStop J-Series (70.19 kb)