Lines Matching refs:variable

151 by setting the shell variable @code{targ_emul} in @file{configure.tgt}.
152 This shell variable is used by the @file{configure} script to control
155 Certain conventions are enforced.  Suppose the @code{targ_emul} variable
162 with two arguments: @var{emul}, and the value of the make variable
163 @code{tdir_@var{emul}}.  The value of the latter variable will be set by
186 use the script @file{emultempl/@var{template}.em}.  If this variable is
230 set by the @code{SCRIPT_NAME} variable in the @file{emulparams} script.
235 script 5 to 9 times.  Each time it will set the shell variable
300 @code{LD_FLAG} variable, the @file{genscripts.sh} script will set
328 @code{cat} with a here document.  The linker script will use variable
334 variable substitution based on @code{RELOCATING}.  For example, on many
343 variable is defined.
407 @code{TEMPLATE_NAME} variable in the @file{emulparams} script.  If the
408 @code{TEMPLATE_NAME} variable is not set, the default is
419 variable substitutions.  Typically each function names uses a
423 Every function and variable in the emitted file should be static.  The
428 The @file{genscripts.sh} script will set the shell variable
431 The @code{ld_@var{EMULATION_NAME}_emulation} variable must be a
435 variable @code{EMULATION_NAME} and the default BFD target name (normally
436 set from the shell variable @code{OUTPUT_FORMAT} which is normally set
439 The @file{genscripts.sh} script will set the shell variable
472 @code{ldemul.c} sets the variable @var{ld_emulation} to point to it.
645 to make client access variable directly in the DLL, bypassing