install-texi.in

早期freebsd实现

@file{||INSTALLdir||/cygnus/tar.log}.  

If you are installing a ``cross-development'' configuration---that is,
one that runs on a ||HOST||, but is meant to develop code for another
platform---@code{Install} is done at this point; skip to the next
step.  (Cross development tapes have @samp{target=@var{machine}} on
the Cygnus tape label.)

If you are installing a ``native'' configuration---that is, one that
both runs on a ||HOST|| and is meant for development on the same
platform---@code{Install} continues by preparing copies of your system
header files.  @xref{Why-fixincludes,,Why Convert System Header
Files?}, for a discussion.  A log for the @code{fixincludes} step goes
in @file{||INSTALLdir||/cygnus/||RELEASEDIR||-||RELNO||/fixincludes.log}.
@emph{Your system's original header files are not changed;}
@code{Install} writes the converted copies in a separate,
@sc{gcc}-specific directory.

As it executes, @code{Install} displays occasional messages to keep you
informed about which of these steps it's executing.  Among them, these
messages mark completion of the major stages of installation:

@cartouche
@example
Cygnus Support software distribution extracted!

@i{Native configurations only:}
Fixed include files installed!

@i{Native configurations only:}
Cygnus Support software distribution tested!

Done.
@end example
@end cartouche

@ifset HOSTrs6000
If the test step fails on a @samp{.s} file, you may not have the
correct assembler from IBM installed.  @xref{Requirements,,System
Requirements}.
@end ifset

@item
Now that the software is on your system, you need to arrange for users
to run it conveniently.  We recommend the following links; see
@ref{Links,,Links for Easy Access and Updating}, for a discussion.

@cartouche
@example
eg$ @b{cd ||INSTALLdir||/cygnus}
eg$ @b{ln -s ||RELEASEDIR||-||RELNO|| ||RELEASEDIR||}

eg$ @b{su root}            @i{root privileges may be needed}
password:               @i{to put link in ||INSTALLdir||}
# @b{ln -s ||INSTALLdir||/cygnus/||RELEASEDIR||/H-||HOSTstr|| ||INSTALLdir||/||RELEASEDIR||}
# exit                  @i{give up root privileges as soon as possible}
@end example
@end cartouche

@item
Finally, in case you need to send problem reports to Cygnus, we've
included a script @code{send_pr} (and a supporting online template) to
structure and transmit your reports.  Please use the
script @code{install_cid} to record your Cygnus customer ID in your copy
of the problem report form.  (You can find your customer ID in the cover
letter that came with this release; or call the Cygnus hotline, 
@w{[phone]}.)  This will enable us to respond as quickly as
possible to any problem reports you send.

@cartouche
@example
eg$ @b{cd} @b{||INSTALLdir||/cygnus/||RELEASEDIR||-||RELNO||/H-||HOSTstr||/bin}
eg$ @b{./install@t{_}cid} @var{ID}
install_cid: `@var{ID}' is now the default customer ID
 for send_pr
@end example
@end cartouche

@item
We recommended permissions @code{777} for the @file{||INSTALLdir||/cygnus}
directory, to be sure you could run this procedure.  However, for the
long term, it is usually not a good idea to leave directories
world-writable (especially directories where executables come from).

For better security, remove public write access from
@file{||INSTALLdir||/cygnus}.  See your System Administrator for the
correct permissions at your site.
@end enumerate

You're done!  Anyone who puts @samp{||INSTALLdir||/||RELEASEDIR||/bin} in
her or his @code{PATH} can use the Developer's Kit.

@node cross-install,  , local-install, Installing
@unnumberedsubsec Installing in @file{||INSTALLdir||/cygnus}, with another machine's tape drive 
This checklist is for a ||HOST|| that does not have its own tape drive,
but can share a file system with another machine that does have a tape
drive.  The other machine need not be a ||HOST||.  

Installing this way will install all the source, plus the binaries for
the ||HOST||.  If you don't want both source and binaries, stop after
extracting @code{Install} from the tape, and read about what options you
can use with @code{Install} in @ref{Install-Options,,Installation
Options}.  For examples of variations on what to install,
@xref{Examples,,Installation Examples}.

@enumerate
@item
find a machine with a suitable tape drive on the same network as your
||HOST||, and sign on to it.  If the only machine with a tape
drive isn't on the network, @pxref{No Drive,,No Local Tape Drive}.

@item
find out the name of the @emph{non-rewinding} tape device on the machine
that can read the release tape.  Cygnus release tapes are labelled to
identify the kind of tape used---either ||TAPEdflt||, or Exabyte.

You should use one of the following devices on ||HOST|| (or
compatible) systems:
@table @emph
@item ||TAPEdflt|| tapes
Use @file{||DEVdflt||} where the examples show @code{/dev/@var{tape}}.

@item Exabyte tapes
The device name depends on how your Exabyte tape drive was installed;
check with your system administrator.  
@ifset HOSTsun4
You will probably use one of
@file{/dev/nrst0} or @file{/dev/nrst1} where the example shows
@code{/dev/@var{tape}}.
@end ifset
@ifset HOSTsun3
You will probably use one of
@file{/dev/nrst0} or @file{/dev/nrst1} where the example shows
@code{/dev/@var{tape}}.
@end ifset
@end table

@item
Choose a directory where you will install the Developer's Kit.  The
directory must be accessible from both machines (the one with the tape
drive, and the ||HOST|| where you want to use the software)---for
example, over NFS.  Wherever this note uses @var{shr}, substitute the
name of the directory you chose.

The shared directory need not have the same name on both machines,
though we show it as @var{shr} on both, for simplicity.

@item
Check that you have enough space available (@pxref{Requirements,,System
Requirements}) in @var{shr}.  You can use @samp{df @var{shr}} to check.

@item
Check whether there's already a @file{@var{shr}/cygnus} directory,
and whether you can write in it.  Typing the following line checks both:

@cartouche
@example
eg$ @b{touch @var{shr}/cygnus/test; rm @var{shr}/cygnus/test}
@end example
@end cartouche

@noindent
@emph{If you get no errors from this line, skip the next step.}

@item
If you got ``No such file or directory'' or ``Permission denied''
errors, you need to sign on (or @code{su}) to an account that has
permission to write in @var{shr} or in an existing
@file{@var{shr}/cygnus} directory.  If only @code{root} has access,
the best procedure is to @code{su root} @emph{briefly}, and create a writable
@file{@var{shr}/cygnus}---then return to your usual sign-on.  For
instance:

@cartouche
@example
eg$ @b{su root}
password:           @i{(enter root password)}
# @b{mkdir @var{shr}/cygnus}      @i{(ignore ``File exists'' error if any)}
# @b{chmod 777 @var{shr}/cygnus}
# @b{exit}              @i{root access not needed beyond this}
eg$
@end example
@end cartouche

@item
Load the Cygnus Support release tape (labelled ``||RELEASEDIR||--||RELNO||'') into
the tape drive.  In these examples, @var{tape} stands for the
device name for the appropriate tape drive on your system.

@item
The first file on the tape is a script called @code{Install}.
That script automates most of the installation procedure---but first you
need to bootstrap the installation by getting @code{Install} itself from
the tape.  It doesn't really matter where you put this initial
copy of @code{Install}; it is only used to get things started---these
examples assume you put it in @file{/tmp}.  When you use this copy of
@code{Install} to extract software from the tape, another copy of
@code{Install} will be saved in
@file{@var{shr}/cygnus/||RELEASEDIR||-||RELNO||}.  Later, you will use that
second copy to finish the installation on your ||HOST||.

These commands will get @code{Install} into the @file{/tmp} directory
(remember, @var{tape} stands for the device name for the appropriate
tape drive on your system):

@cartouche
@example
eg$ @b{cd /tmp}
eg$ @b{tar xfv /dev/@var{tape} Install}
@end example
@end cartouche

@noindent
@c UPDATE! tar error messages on other hosts?
If you get any error messages beginning with something like ``tar: can't
open'', check that the tape is correctly placed in your tape drive, and
that you typed the right name for @var{tape}.

@quotation
@emph{If you don't want both source and binaries, stop now,} and read about
what options you can use with @code{Install} in
@ref{Install-Options,,Installation Options}.  For examples of variations
on what to install, @xref{Examples,,Installation Examples}.
@end quotation

@item
Now you can extract all the software by running @samp{Install extract}.
Use the @samp{-tape=} option to identify your tape drive, and the
@w{@samp{-installdir=}} option to point to the @var{shr} directory.

@cartouche
@example
eg$ @b{cd /tmp}
eg$ @b{./Install extract -tape=/dev/@var{tape} -installdir=@var{shr}/cygnus}
@end example
@end cartouche

This is a time-consuming step.  @code{Install} will use @code{tar} to
extract software for your system, leaving a log in the file
@file{@var{shr}/cygnus/tar.log}.

When @code{Install} is done extracting the tape contents, it
displays the messages

@cartouche
@example
Cygnus Support software distribution extracted!
Done.
@end example
@end cartouche

@item
Log on to the ||HOST|| where you want to use the software.

@item
Create a symbolic link from @file{@var{shr}/cygnus/||RELEASEDIR||-||RELNO||}
to @file{||INSTALLdir||/cygnus/||RELEASEDIR||-||RELNO||} on your ||HOST||.  You may
need to become @code{root} @emph{briefly}, as in this example:

@iftex
@widen{1pc}
@end iftex
@cartouche
@example
eg-||HOSTstr||$ @b{su root}
password:
# @b{mkdir ||INSTALLdir||/cygnus}        @i{(ignore ``File exists'' error if any)}
# @b{chmod 777 ||INSTALLdir||/cygnus}
# @b{ln -s @var{shr}/cygnus/||RELEASEDIR||-||RELNO|| ||INSTALLdir||/cygnus/||RELEASEDIR||-||RELNO||}
# exit              @i{root access not needed beyond this}
@end example
@end cartouche
@iftex
@widen{-1pc}
@end iftex

@noindent
If you don't have access to any account with permission to write in
@file{||INSTALLdir||}, @pxref{No access,,No Access to @file{||INSTALLdir||/cygnus}}.

@item
@quotation
@emph{Skip this step if you are installing a ``cross-development''
configuration.}  A cross-development configuration is one that runs on a
||HOST||, but is meant to develop code for another platform.  Cross development
tapes have @samp{target=@var{machine}} on the Cygnus tape label.
@end quotation
Fix up system header files on your ||HOST||, and test the installation, with
the copy of @code{Install} that was placed in
@file{@var{shr}/cygnus/||RELEASEDIR||-||RELNO||}:

@cartouche
@example
@i{Native configurations only}
eg-||HOSTstr||$ @b{cd ||INSTALLdir||/cygnus/||RELEASEDIR||-||RELNO||}
eg-||HOSTstr||$ @b{./Install @b{f}ixincludes test}
@end example
@end cartouche

@noindent
@xref{Why-fixincludes,,Why Convert System Header Files?}, for a
discussion.  A log for the @code{fixincludes} step goes in
@file{||INSTALLdir||/cygnus/||RELEASEDIR||-||RELNO||/fixincludes.log}.
@emph{Your system's original header files are not changed;}
@code{Install} writes the converted copies in a separate,
@sc{gcc}-specific directory.

When each stage of this work is complete, @code{Install} displays these
messages (the last, @samp{Done.}, simply indicates that @code{Install}
has finished executing).

@cartouche
@example
@i{Native configurations only}
Fixed include files installed!

Cygnus Support software distribution tested!

Done.
@end example
@end cartouche

@ifset HOSTrs6000
If the test step fails on a @samp{.s} file, you may not have the
correct assembler from IBM installed.  @xref{Requirements,,System
Requirements}.
@end ifset

@item
Now that the software is on your system, you need to arrange for users
to run it conveniently.  We recommend the following links; see
@ref{Links,,Links for Easy Access and Updating}, for a discussion.

@cartouche
@example
eg-||HOSTstr||$ @b{cd ||INSTALLdir||/cygnus}
eg-||HOSTstr||$ @b{ln -s ||RELEASEDIR||-||RELNO|| ||RELEASEDIR||}

eg-||HOSTstr||$ @b{su root}      @i{root privileges may be}
password:               @i{needed to put link in ||INSTALLdir||}
# @b{ln -s ||INSTALLdir||/cygnus/||RELEASEDIR||/H-||HOSTstr|| ||INSTALLdir||/||RELEASEDIR||}
# exit                  @i{give up root privileges as soon as possible}
@end example
@end cartouche

@item
Finally, in case you need to send problem reports to Cygnus, we've
included a script @code{send_pr} (and a supporting online form) to
structure and transmit your reports.  Please use the
script @code{install_cid} to record your Cygnus customer ID in your copy
of the problem report form.  (You can find your customer ID in the cover
letter that came with this release; or call the Cygnus hotline, 
@w{[phone]}.)  This will enable us to respond as quickly as
possible to any problem reports you send.

@cartouche
@example
eg$ @b{cd} @b{||INSTALLdir||/cygnus/||RELEASEDIR||-||RELNO||/H-||HOSTstr||/bin}
eg$ @b{./install@t{_}cid} @var{ID}
install_cid: `@var{ID}' is now the default customer ID
 for send_pr
@end example
@end cartouche

@item
We recommended permissions @code{777} for the @file{||INSTALLdir||/cygnus} and
@file{@var{shr}/cygnus} directories, to make sure you could run this