Installing
GNUPro Toolkit
The following documentation describes how to install your GNUPro Toolkit software on Unix and Win32 systems.
The following documentation describes how to install your GNUPro Toolkit software on Unix and Win32 systems.
- To install for Unix platforms, see Installing on Unix Systems from CD.
- To install for Windows platforms, see Installing on Win 95/NT systems from CD.
For help with using the tools, see
Cygnus and GNUPro Toolkit fundamentals and Using
GNU tools on embedded systems.
For information about rebuilding the tools for other target environments, see Rebuilding from source.
Installing on Unix systems from CD
Use the following
procedures for full installation from CD for Unix
systems. In the following procedure examples, the system prompt appears
as '%'.
% mount -F hsfs -o ro /dev/dsk/c0t6d0s0 / mnt
% mount -t hsfs -o ro /dev/sr0 / mnt
% mount -t cdfs -o ro /dev/dsk/c201d2s0 / mnt
% mount -t iso9660 -o ro /dev/scsi/sc0d7l0 / mnt
% mount -t cdrfs -o ro /dev/cd0 / mnt
% mount -t cdfs -o ro /dev/rz4c / mnt
% su root(enter root password)
% mkdir /usr/cygnus(ignore "File exists" error if any)
% chmod 777 /usr/cygnus
% exit(root access not needed beyond this)
% cd /usr/cygnus/gnupro-98r2
% uncompress < /mnt/src.tar.Z | tar xpf -
% cd /usr/cygnus/gnupro-98r2
% uncompress < /mnt/doc.tar.Z | tar xpf -
% cd /usr/cygnus
% ln -s gnupro-98r2 gnupro
% su root
% ln -s /usr/cygnus/gnupro-98r2/H-host /usr/gnupro
% exit
See your system administrator for
the correct permissions at your site.
You're done! Now, anyone with '/usr/gnupro-98r2/bin' in their PATH can use this GNUPro Toolkit package.
You're done! Now, anyone with '/usr/gnupro-98r2/bin' in their PATH can use this GNUPro Toolkit package.
Using your Cygnus customer ID (see cover letter), report problems by using the Web; see Reporting problems for details.
Installation information for Unix
The following documentation describes host-specific information and installation standards for Unix systems.Platform names
Your package
contains a label that indicates the host (and target, if applicable) with
which to configure the binaries. The specifications used for hosts
and targets in the configure script are based on a three-part
naming scheme, though the scheme is slightly different between hosts and
targets.
architecture-vendor-operating system
Host names
Naming
hosts shows the usage of canonical names for referring to the corresponding
host platforms that Cygnus supports. For any questions about compatibility,
contact Cygnus (see How
to contact Cygnus).
Naming hosts
Target names
The following
documentation lists some of the more common targets supported by Cygnus,
along with their output format. Not all targets have support on every host.
See also Native
configurations support and Embedded
cross-configuration support for the matrices of the host/target combinations
supported by Cygnus. Also, for more informaton on using particular tools
and their targets, see Using GNU tools on embedded
systems, Cross-development environment,
and GNUPro
Tools for Embedded Systems.
H8/300 processor name and output format
| sh-hms | COFF object code format |
i960 processor names and output format
M68K processor names and output formats
|
ELF object
code format *
|
see Motorola m68k development in GNUPro Tools for Embedded Systems.
MIPS processor names and output formats
PowerPC processor names and output formats
|
powerpc-eabi
|
ELF object code format (EABI)
|
SPARC processor names and output formats
x86 processor names and output formats
| i386-coff | COFF object code format |
config.guess scripts
config.guess
is a shell script that attempts to deduce the host type from which it is
called, using system commands like uname if they are available.
config.guess
is remarkably adept at deciphering the proper configuration for your host;
if you are building a tree to run on the same host on which you're building,
we recommend not specifying the hosttype argument.
config.guess
is called by configure; you need
never run it by hand, unless you're curious about the output.
Links for easy access and updating
Once you extract
the tools from the CD, they are installed into a directory named 'installdir
/gnupro-98r2' where 'installdir' refers to the
full directory pathname within which you're locating the 'gnupro-98r2'
files.
For example,
if you've installed in the default location under /usr/cygnus,
use the following input.
ln -s /usr/cygnus/gnupro-98r2 /usr/cygnus/gnupro
The release
number is in the directory name so that you can keep several releases installed
at the same time, if you wish. In order to simplify administrative procedures
(such as upgrades to future Cygnus releases), we recommend that you establish
a symbolic link
of '/usr/cygnus/gnupro' to this directory with the following input.
ln -s installdir /gnupro-98r2 installdir /gnupro
Directories
of machine-independent files (source code and documentation) are
installed directly under 'gnupro-98r2'. However, to accommodate
binaries for multiple hosts in a single directory structure, the binary
files for your particular host type are in a subdirectory 'H-hosttype'.
(hosttype indicates a particular architecture, vendor and
operating system; see Host names
for more specific details on names for input.)
We recommend building these links
as the last step in the installation process.
This means that one more level of symbolic links is helpful, to allow your users to keep the same execution path defined even if they sometimes use binaries for one machine and sometimes for another. Even if this doesn't apply now, you might want it in the future; establishing these links now can save your users the trouble of changing all their paths later.
The idea is to build '/usr/gnupro/bin' on each machine so that it points to the appropriate binary subdirectory for each machine--for instance, '/usr/cygnus/gnupro-98r2/H-hosttype' where 'hosttype' corresponds to the host machine.
You may need super-user access again briefly to establish the following link.
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.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. The following shows examples with the final linked installation directory as /usr/gnupro/bin . If you installed into a different directory, substitute ` /usr/gnupro/bin ' for the actual directory.
% export PATH
Installing on Win 95/NT systems from CD
- Setup
prompts for an installation directory; the default is 'C:\Program Files\Cygnus
Solutions\gnupro-98r2'. The tools may be installed in any directory
or drive.
Make sure the installation directory is where you want to install the files. Check the box for installing souce code files, if that is an option you require.
Click Next.
\CYGNUS\gnupro-98r2\demo> MAKE
- This input will provide a test, ensuring a correct configuration.
- 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 5. If not, choose Settings,
and click Control Panel. Choose System.
Make the appropriate changes according to your requirements.
Rebuilding GNUPro Toolkit
To rebuild,
see Rebuilding from source.
|
© 2005 Red Hat, Inc. All rights reserved. About Red Hat : Legal statement : Privacy statement : Contact |