Contents|Index|Previous|Next

Running the programs

In order to run the tools in GNUPro Toolkit after you install them, you must first set a few environment variables so your shell can find them.

- At the very least, set your PATH variable. See Setting PATH.
- If you install the tools in a non-default location and don’t set the standard symbolic links (see Links for easy access and updating), you must also set the GCC_EXEC_PREFIX environment variable. Otherwise, the compiler can’t find its resources. See gcc paths.
- If you install GNUPro Toolkit in an alternate location, you need to set the variable, INFOPATH, so that info can find the online documentation. See Online documentation paths.
- Some man programs recognize the environment variable, MANPATH, as a search path for online manual pages. You must either add your installation directory to your MANPATH environment variable, or copy the online manual pages in your distribution into a location where your man program can find them. See Online documentation paths.

Setting PATH

To run the tools in this distribution, make sure the PATH environment variable can find the tools. Whether you install in the default location, as in the following example for the input, or in an alternate location, you need to alter your PATH environment variable to point toward the newly installed tools.

/usr/cygnus/progressive-97r1a

If you create the symbolic links we recommend (see Links for easy access and updating), users who want to run the GNUPro Toolkit—regardless of whether they need binaries for your particular host, or for some other platform—can use initialization files settings like for one of the following shells. The following shows examples with the final linked installation directory as /usr/progressive/bin. If you installed into a different directory, substitute ‘/usr/progressive/bin’ for the actual directory.

For Bourne-compatible shells (/bin/sh, bash, or Korn shell):

PATH=/usr/progressive/bin:$PATH
export PATH

For C shell:

set path=(/usr/progressive/bin $path)

gcc paths

You can run the compiler GCC without recompiling, even if you install the distribution in an alternate location, by first setting the environment variable, GCC_EXEC_PREFIX. This variable specifies where to find the executables, libraries, and data files used by the compiler. Its value will be different depending on which set of binaries you need to run. For example, if you install the tape distribution under ‘/local’ (instead of the default ‘/usr/cygnus’), and you wish to run gcc as a native compiler, you could set GCC_EXEC_PREFIX as follows.

For shells compatible with Bourne shell (/bin/sh, bash, or Korn shell):

# GCC_EXEC_PREFIX=/local/progressive-97r1a\
/H-hosttype/lib/gcc-lib/
# export GCC_EXEC_PREFIX

For C shell:

# setenv GCC_EXEC_PREFIX /local/progressive-97r1a\
/H-hosttype/lib/gcc-lib

Note:
The trailing slash ‘/’ is important. The gcc program uses GCC_EXEC_PREFIX as a prefix. If you omit the slash (or make any other mistakes in specifying the prefix), gcc fails with a message: installation problem, cannot execute ....

Online documentation paths

Other than the HTML files, you also an online documentation help browser, info. Its default location, ‘/usr/cygnus/progressive-97r1a/info’, is compiled into info. If you install elsewhere, set the environment variable, INFOPATH, to indicate the alternate location. For example, if you install under ‘/local’, set location as follows.

For shells compatible with Bourne shell (/bin/sh, bash, or Korn shell):

# INFOPATH=/local/progressive-97r1a/info
# export INFOPATH

For C shell:

# setenv INFOPATH /local/progressive-97r1a/info

If you build ‘progressive’ as a symbolic link to ‘progressive-97r1a’, as recommended in Links for easy access and updating; then use ‘/local/progressive/info’ as the value for INFOPATH as shown in the previous examples. Be sure that your man command can pick up the manual pages for these tools.

Some man programs recognize a MANPATH environment variable. If your man program does, users at your site can include lines like the following in their initialization file.

For Bourne-compatible shells:

# MANPATH=/usr/cygnus/progressive/man:$MANPATH:/usr/man
# export MANPATH

For C shell:

# setenv MANPATH /usr/cygnus/progressive/man:$MANPATH:/usr/man

If your man program doesn’t recognize MANPATH, try copying or linking files from ‘installdir/progressive/man/man1’ into your ‘man/man1’ directory.