Using your Cygnus customer ID (see cover letter),
enable the electron
ffb
ic mail tool for reporting
problems. With the following commands, enable the send-pr tool..
% /usr/gnupro-98r1/bin/install-sid customer-ID
8. Remove
public write access restrictions from'/usr/cygnus'.
See your system administrator for the correct
permissions at your site.
You're done! Now, anyone with '/usr/gnupro-98r1/bin' in their
PATH can use this GNUPro Toolkit package.
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
hostsshows 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).
configure can represent
a very large number of target name combinations of architecture, vendor,
and object formats. Support is not possible for all combinations.
H8/300 processor name and output format
h8300-hms-coff
COFF object code format
i960 processor names and output format
i960-coff
MON960 monitor (COFF
format)
i960-vxworks5.1
VxWorks environment
i960-vxworks5.2
VxWorks environment
M68K processor names and output formats
m68k-aout
a.out object code format
m68k-coff
COFF object code format
m68k-elf
ELF object code format
m68k-vxworks5.1
VxWorks environment
m68k-vxworks5.2
VxWorks environment
MIPS processor names and output formats
mips-elf
ELF object code format
mips64-elf
ELF object code format
mips-ecoff
ECOFF object code format
mips-elf
ELF object code format
mips64vr5000-elf
ELF object code format
mips-tx39-elf
ELF object code format
SH processor name and output format
sh-hms-coff
COFF object code format
SPARC processor names and output formats
sparc-elf
ELF object code format
sparc-aout
a.out object code format
sparclet-aout
a.out object code format
sparclite-aout
a.out object code format
sparclite-coff
COFF object code format
sparc-
ffb
vxworks5.1
VxWorks environment
x86 processor names and output formats
i386-aout
a.out object code format
i386-elf
ELF 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-98r1'
where 'installdir' refers to the full directory pathname
within which you're locating the 'gnupro-98r1' files.
For example, if you've installed in the
default location under /usr/cygnus, use the following input.
ln -s /usr/cygnus/gnupro-98r1 /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-98r1 installdir /gnupro
NOTE:
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) are installed directly under 'gnupro-98r1'.
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
namesfor more specific details on names for input.)
This means tha
ffb
t 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-98r1/H-hosttype'
where 'hosttype' corresponds to the host machine.
You may need super-user
access again briefly to establish the following link.
We recommend building these
links as the last step in the installation process.
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 PATHvariable.
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_PREFIXenvironment
variable. Otherwise, the compiler can't find its resources. See gcc
paths.
Setting
PATH
To run the tools in this distribution,
make sure the PATHenvironment
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.
For Bourne-compatible shells
(/bin/sh , bash, or Korn shell):
% PATH=/usr/gnupro/bin:$PATH
<
ffb
/UL>
% export PATH
For C shell:
% set path=(/usr/gnupro/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 CD 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):
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 ... .
Installing
on Win 95/NT systems from CD
All releases of GNUPro Toolkit
for Win95/NT systems use the following
CD installation procedure.
1. Mount the
CD.
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.
2. Determine
where to install the tools.
Setup
prompts for an installation directory; the default is 'C:\CYGNUS'.
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.
3. Ensure
adequate disk space for the installation.
Setup
first checks the installation location to make sure it has enough space
before unpacking the tools. Installed GNUPro Toolkit disk usage varies
from about 10 to about 50 megabytes, depending on the target (generally,
the requirement is 19 megabytes).
4. Proceed
with the automatic installation process.
Setup
reads the CD, builds the directories and expands the files.
5. Run
the programs to use the tools.
Click on the Start
button on the lower left hand corner of your screen, and choose Programs,
where Cygnus programs are found as
a shortcut. Choose Cygnus. A DOS shell
program opens.
6. Test
the installation by building the tools with the 'MAKE'
command.
To test the installation, change your working
directory to the demo subdirectory of the CYGNUS directory
(as in the following example), and type 'MAKE' at the prompt.
C:\CYGNUS\> cd C:\CYGNUS\gnupr0-98r1\demo
C:\CYGNUS\gnupro-98r1\demo> MAKE
...
7. Set
up the environment for which you'll use the tools.
For the Win95 environment, set your working
environment to the Autoexec.bat initialization
file.
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.