Install on UNIX or Linux Systems with CD

This section describes how to install GNUPro Toolkit for UNIX systems from CD. Be sure that you are familiar with the naming conventions for the tools as described in Naming Conventions and Embedded Cross-configurations.

IMPORTANT!

In the following installation input examples, for /mnt, substitute your directory or /cdrom/gnupro-02r1 (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.

1. Insert CD into CD-ROM drive.
2. Mount the CD.

The procedures for mounting a CD depend on your system type. The following examples of mount commands use default configurations; consult your system administrator if you need assistance.

• Caldera, Red Hat, S.u.S.E Linux

As root, enter the following command (the command assumes that the CD is already in /etc/fstab):

mount -t iso9660 /dev/cdrom /mnt/cdrom

• SUN SPARC Solaris

If you are running the volume manager, the CD will automatically mount as /cdrom/ gnupro-02r1 and you will not require root access.

If you are not running the volume manager, as root mount the CD manually with the following command:

mount -F hsfs -o ro /dev/dsk/c0t6d0s0 / mnt

3. Determine where to install the tools with permissions.

Install the tools in a directory that has writable access permissions. Ensure that you can put the tools in installdir as follows. Enter:

su root

After entering the root password, make the installation directory:

mkdir installdir

If a " File exists " error appears, ignore it. Change the permissions for the new directory:

chmod 777 installdir

Root access is unnecessary beyond this point. Type exit at the prompt.

4. Run the installation.

To install, use either the graphical user interface (GUI) or the command line interface (CLI) installation script.

To install using the GUI installer:

To install using the GUI installer, set the DISPLAY environment variable. If you do not know how to set this variable, have your system administrator show you.

Run the GUI installation script:

/mnt/install-gui

When installing with the GUI installer you will reach a stage where you are asked to select the type of install you want to do. The install options are "Typical Installation," "Full Installation," or "Customized Installation."

Typical Installation

Selecting a "Typical Installation" will install the packages required for a working GNUPro development environment. The following packages are installed with a "Typical Installation":

• GNUPro Compilers
• GNUPro Debugger
• GNUPro DejaGNU
• GNUPro Misc
• GNUPro HTML help files
• GNUPro Tex Info help files

"Typical Installation" is recommended for first time and new users.

Full Installation

Selecting "Full Installation" will install all of the GNUPro packages; these include all the packages list for a "Typical Installation" plus the following:

• GNUPro PDFFiles
• GNUPro ManPages
• GNUPro Utils
• GNUPro Sources

Customized Installation

Selected "Customized Installation" will enable you to select which packages you would like installed.

IMPORTANT!

Both "Typical Installation" and "Full Installation" will add the GNUPro and UserTools directories to the PATH environment variable. If you do not wish the installer to modify the Windows NT registry, then select "Customized Installation" and deselect the "Update Windows PATH" package before installing.

To install using the command line:

When using the install-cli command for a command line installation, by default the install-cli script prompts you for installation information. The following command line options allow you to install by accepting the defaults provided or by overriding the default installation directory:

--target= target
Installs for target type (see Naming Conventions for the appropriate target name to use for target).

--installdir= installdir
Provides the directory path (installdir) to where the tools install.

--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. Some of these options do not work outside of installation scripts.

Choose the options that you want (if any) and enter the command line installer name. For example:

/mnt/install-cli

5. Both installers will prompt you for installation information including specifying the installation directory and the tools to install. Upon successful completion, the following message appears.

Installation completed successfully.

6. In Step 3, you set writable permissions for the installdir directory. Now, set them to what the system usually uses; generally this would be:

chmod 755 installdir

See your system administrator if you do not know what is appropriate. Now anyone whose PATH includes installdir/bin can use the tools.

7. Build symbolic links. This task simplifies administrative procedures for upgrades to future GNUPro releases, provides the software transparently to other users, and permits users to have multiple versions in the same location.

GNUPro Toolkit installs into a installdir/gnupro-yymmdd directory, where installdir is the absolute path name within which you locate the tools. In the examples that follow, installdir/gnupro-02r1 is the default location; however, substitute your actual directory if that is not the correct path.

For an installation in the default location of installdir/gnupro-02r1, enter:

cd installdir/gnupro-02r1

ln -s gnupro-02r1/H-host

Directories of machine-independent files (source code and documentation) install directly under the gnupro-02r1 directory.

To accommodate binaries for multiple hosts in a single directory structure, the binary files for your particular host type are in the H-host subdirectory (see Naming Conventions for specific input.) The previous example 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 of changing all their paths later. The idea is to build H-host/bin so that it points to the appropriate binary subdirectory for your machine; use installdir/gnupro-02r1/H-host as the path. For instance, where host designates what you need to specify as your host, enter your commands using the binaries for the particular architecture, vendor, and operating system.

8. Using super-user access again, establish the link as follows:

ln -s installdir/gnupro-02r1/H-host/bin installdir/H-host/bin

Setting the PATH Environment Variable

To run the tools in this distribution, ensure that the PATH environment variable points to the tools. Whether you install in the default location or in an alternative location, you need to alter your PATH environment variable to point to the tools. If you created the recommended symbolic links, users who want to run the tools--regardless of whether they need binaries for a specific host or for some other platform--can use initialization files settings. If you installed into a different directory, substitute installdir for the actual directory. For host, see Table 1, Naming hosts with their canonical names for naming conventions. The following examples show how to create the final linking to the installdir/H-host/bin directory.

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

PATH=installdir/H-host/bin:$PATH
export PATH

• For C shell:

set path=(installdir/H-host/bin $path)

IMPORTANT!

The path should not include any colons for the C shell environment variable settings. The directory path should be separated only by whitespace.

For more information on using other environment variables, see "How to Use Variables" in Using make in GNUPro Development Tools.

Next Steps

Before turning to Basics of the Tools, it is useful to look over How to Report Problems first.

Install on Microsoft Windows Systems with CD

All releases of GNUPro Toolkit for Microsoft Windows1 systems2 use the following CD installation procedure.

1. Insert CD into CD-ROM drive. The installation should start automatically; if it does not, open the CD in the Windows Explorer and run setup.exe.
2. Install the tools.

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 that does not have a space in the path name.

C:\redhat is the default installation location.

GNUPro Toolkit is the default program folder name.

3. Run the programs to use the tools.

Using either the Microsoft Windows file browser or CMD.EXE command line prompt, navigate to the directory C:\redhat\gnupro-02r1\bin and run the executable bash.exe. A bash shell 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 will use the tools.

   For the Windows NT environment, choose Settings, and click Control Panel, choose System, and click on the Environment tab.

Make the appropriate changes according to your requirements by adding the contents of the C:\redhat\gnupro-02r1\cygwin1.bat to your Windows NT environment settings. You can also add the environment settings for the unsupported tools from the C:\redhat\gnupro-02r1\usertools\cygwin1.bat file.

IMPORTANT!

The unsupported tools are provided only for the purposes of rebuilding the sources. See Rebuilding from Source for more information on rebuilding.

5. Use the tools.

See Basics of the Tools. For details about using the tools for developing programs in the Win32 environment as if ported to emulate UNIX applications, see Using Cygwin.

For more information on setting environment variables, see Environment Variables for Cygwin and see "How to Use Variables" in Using make in GNUPro Development Tools.