Installing
GNUPro Toolkit
The
following documentation describes how to install
your GNUPro Toolkit software on UNIX and Win32 systems.
Installation will provide all the tools
that Cygnus supports as well as many tools that have no support (even though
unsupported tools may work with high success).
For help with using the tools, see Cygnus
and GNUPro Toolkit fundamentals and Using the
tools on native and embedded systems.
For information about rebuilding the tools for other target
environments, see Rebuilding from source.
Installing
on UNIX systems from CD
GNUPro Toolkit
for UNIX systems uses the following CD installation procedure.
For more details on naming conventions for the tools as
they pertain to specific systems, see Naming
hosts and targets and, specifically, Naming
hosts. See also Links
for easy access and updating, install-cli
options, Setting the PATH environment
variable, and Rebuilding from source.
Note:
In the following
installation input examples, for /mnt, substitute your
directory or /cdrom/gnupro_99r1
(the default directory in which
you will mount the tools). host designates what you need
to specify as your host type in using the binaries for the particular architecture,
vendor, and operating system (see Table
7: Naming hosts for naming standards)
1. Mount the CD.
Insert CD into CD-ROM drive.
The procedures for mounting the CD depend on your system type. The following
discussion details some examples of mount commands for each host (the examples
use defaults for some configurations). Consult your system administrator
if you need assistance.
If
you are running the volume manager, the CD will automatically mount as
/cdrom/gnupro_99r1
and you will not require root access.
If
you are not running the volume manager, you will need to mount the CD manually
with the following command.
mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /mnt
SPARC SunOS
mount -t hsfs -o ro /dev/sr0 /mnt
HP-UX
mount -t cdfs -o ro /dev/dsk/c201d2s0 /mnt
SGI IRIX
mount -t iso9660 -o ro /dev/scsi/sc0d7l0 /mnt
AIX
mount -t cdrfs -o ro /dev/cd0 /mnt
Digital Unix
Linux
mount -t cdfs -o ro /dev/ /mnt
2. Determine
where to install the tools with permissions.
-
Install the tools in a directory
that has writable access permissions. If you don't have permissions, you
must get root access to put the tools in a non-standard directory by using
the following example’s input.
su root
After entering a root password, use the following example’s
input.
mkdir /usr/cygnus
Ignore “File exists” error, if any message appears;
continue to change the permissions for that new directory, using the following
example’s input.
chmod 777 /usr/cygnus
Root access is unnecessary beyond this point. Enter “exit”
at the prompt.
-
To install, use either the graphical
user interface (GUI) or the command line interface (CLI) installation script.
-
To install using the GUI installation, use the following
input.
/mnt/install-gui
Before
running the GUI installation script, set the DISPLAY environmental
variable so that there are permissions to access programs without security
restrictions for that system’s DISPLAY. If you don’t know how
to set this variable, have your system administrator show you.
-
To install using the CLI installation, use the following
input.
/mnt/install-gui
For details on other options to the
CLI installation script, see install-cli
options.
Follow the onscreen directions. Both installers
will prompt you for installation information including specifying installation
directory and the tools to install. Upon successful completion, the following
message appears.
Finished.
4. Build
symbolic links to make executable paths easy to negotiate.
You may need root access to put the link in the
‘/usr’ folder. ‘host’ in the following example’s
fourth line’s instruction stands for the host machine that you’ll be using;
see also Links for easy access
and updating.
cd /usr/cygnus
ln -s gnupro-99r1 gnupro
su root
ln -s /usr/cygnus/gnupro-99r1/H-host /usr/gnupro
5. Change
permissions from the ‘/usr/cygnus’
location and you’re ready to use the tools.
In Step 2, you set writable permissions.
Now, you set them to what the system usually uses. See your system administrator
if you don’t know what’s appropriate. Now, anyone with ‘/usr/gnupro/bin’
in their PATH can use the tools.
Links
for easy access and updating
Build symbolic
links as the last step in the installation process.
IMPORTANT:
This task simplifies administrative procedures
for upgrades to future GNUPro releases, providing the software transparently
to other users and permitting users to have multiple installations in the
same location.
ln -s /usr/cygnus/gnupro-99r1 /usr/cygnus/gnupro
cd /usr/cygnus
ln -s gnupro-99r1 gnupro
The input for the last two
examples of input match (installdir means the same location
as the default that you assign for usr/cygnus.
Directories
of machine-independent files (source code and documentation) install directly
under the ‘gnupro-99r1’ level. To accommodate binaries for multiple
hosts in a single directory structure, the binary files for your particular
host type are in the ‘H-hosttype’ subdirectory (hosttype
indicates a particular architecture, vendor and operating system; see Naming
hosts for more specific input.)
The previous example shows input that provides one more
level of symbolic links so that other users can define the same executable
path even if they use binaries sometimes for one machine and sometimes
for another machine. Establishing these links now can save developers the
trouble later of changing all their paths. The idea is to build ‘/usr/gnupro/bin’
so that it points to the appropriate binary subdirectory for your machine.
For instance, use the path, /usr/cygnus/gnupro-99r1/H-host,
where host designates what you need to specify as your host type in using
the binaries for the particular architecture, vendor, and operating system
(see Naming hosts for naming
standards).
You may then need super-user access again, using the following
example’s input to establish the link.
ln
-s /usr/cygnus/gnupro-99r1/H-host /usr/cygnus/gnupro
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 tools.
If you create the symbolic
links we recommend (see Links
for easy access and updating), users who want to run the tools—regardless
of whether they need binaries for your particular host, or for some other
platform—can use initialization files
settings. The following examples show the appropriate input for creating
the final linking to the /usr/gnupro/bin directory. If you
installed into a different directory, substitute ‘/usr/gnupro/bin’
for the actual directory. For the appropriate input for <host>,
see Naming hosts for naming
standards of your operating system or processor.
-
For Bourne-compatible
shells (bash or tcsh shell):
PATH=/usr/cygnus/gnupro-99r1/H-<host>/bin:/usr/cygnus/snavigator-99r1/H-<host>/bin:$PATH
export PATH
For C
shell:
set path=/usr/cygnus/gnupro-99r1/H-<host>/bin /usr/cygnus/snavigator-99r1/H-<host>/bin $path)
install-cli options
By default, the install-cli script prompts you for installation
information. There are also command line options to allow you to install
by accepting the defaults provided or overriding the default installation
directory. A summary follows of these options.
--target=target
Installs for target type (see Target
names for the appropriate input for the target name to use for target).
--installdir=yourinstalldirectory
Provides the location of yourinstalldirectory
where you installed the tools. ‘/usr/gnupro/’ is the default directory.
--defaults
Installs default products and packages. Where
applicable, the defaults are English, all binary packages, all documentation
packages, no source tools, no demonstration packages.
--help
Lists all available options.
Note:
Some of the options that will list for the --help
command are what install-cli uses internally; these commands cannot
work for use outside of the installation scripts.
Installing
on Win NT/95/98 systems from CD
All releases
of GNUPro Toolkit for WinNT/95/98 *
systems †
use the following CD installation procedure.
Insert
CD into CD-ROM drive. The Cygnus installation will start; if it doesn't,
open the CD in the Windows Explorer
and open setup.exe.
After accepting the terms
of the license agreement, follow the on-screen instructions to select the
location where the tools install. Also specify a program folder name and
which products and packages to install.
Important!
Install the tools on any drive and in any directory which
does not have a space in the pathname.
‘C:\cygnus’
is the default installation location.
‘Cygnus GNUPro Toolkit’
is the default program folder name.
3. Run the programs
to use the tools.
Click on the Start
button on the lower left hand corner of your screen, and then Programs,
where you have shortcut access to all your programs. Choose Cygnus
GNUPro Toolkit and then Cygnus,
gnupro-99r1
and the target on which you select to run the tools (see
Target
names for designations for
target). If you set up a
different path for the tools or a different folder name, substitute that
designation as appropriate.
A shell window will activate with the appropriate PATH
settings for using the tools.
If you have installed the unsupported tools, click on
the Start button on the lower left hand corner of your screen, and then
Programs, where you have shortcut access to all your programs. Choose Cygnus
GNUPro Toolkit and then Cygnus, unsupported-99r1 and, last, bash. A bash
window will activate with the appropriate PATH settings for using the unsupported
tools; the unsupported tools are available only for the purposes of rebuilding‡
the sources.
4. Set
up the environment for which you’ll use the tools.
For the Win95 environment,
add the contents of the C:\cygnus\gnupro-99r1\CYGNUS.BAT
initialization file to your autoexec.bat
file, or initialize it from the Start
button, using the Program menu as in
Step
3.
For the NT environment, as
long as you use the Start button in
the lower left hand corner of your screen, you can always start the programs
as in Step 3. If not, choose Settings,
and click Control Panel. Choose System.
Make the appropriate changes according to your requirements by adding the
contents of the C:\cygnus\gnupro-99r1\CYGNUS.BAT
initialization file to your autoexec.bat
file.
You can also add the environment settings for the Cygnus
unsupported tools from the C:\cygnus\gnupro-99r1\CYGNUS.BAT
initialization file.
Note:
The unsupported tools are provided only for the purposes
of rebuilding the sources. See Step 3 footnote
and Rebuilding from source for more information.
5. Use the
tools.
| * |
To name the Windows operating systems, Cygnus uses the
standards of “NT4.0-sp3” for Windows NT 4.0/service pack 3, and “95-osr2”
for Windows 95/operating system revision 2. |
| † |
The 486, 586 and 686 are the supported versions. |
| ‡ |
IMPORTANT: There is no support for rebuilding
cross-configurations for the Windows 95 and 98 versions; rebuilding is
only available for the NT version. |
Rebuilding
GNUPro Toolkit