relnotes.texi

早期freebsd实现

\input texinfo
@c
@c This file may require a nonstandard texinfo.tex to format; if you
@c need it, please contact Cygnus Support (email [e-mail])
@setfilename RELEASE.info
@c
@c This file describes a Cygnus Progressive Release (Developer's Kit).
@c
@c Copyright (C) 1991, 1992 Cygnus Support
@c This text may be freely distributed under the terms of the GNU
@c General Public License.
@c
@c $Id: relnotes.texi,v 1.3 1992/11/30 09:40:46 zoo Exp $
@c
@iftex
@c The include file "texiplus.tex" is in the texinfo/cygnus dir, and
@c implements Cygnus modifications to the texinfo manual style.
@input texiplus
@c The include file "smpklug.texi" is a kluge to deal with local
@c document production issues at Cygnus; it's safe to comment out this
@c line if you don't have (or don't want) the file.
@input smpklug.texi
@smallbook
@cropmarks
@finalout
@settitle Release Notes
@setchapternewpage on
@c
@end iftex
@tex
\global\def\manvers{Progressive p3-921001}
@end tex

@titlepage
@title Release Notes
@sp 3
@table @strong
@item Cygnus Support Developer's Kit
@item Progressive Release p3-921001
@end table
@author Cygnus Support
@page

@tex
\xdef\Rmanvers{{\it Release Notes (Progressive p3-921001 Developer's Kit)}} % *NOT* for use in headers, footers
{\parskip=0pt \hfill Cygnus Support\par \hfill \Rmanvers\par \hfill
\TeX{}info \texinfoversion\par }
\global\def\manvers{Progressive p3-921001}
@end tex

@vskip 0pt plus 1filll
Copyright @copyright{} 1992 Cygnus Support

Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
are preserved on all copies.

Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided also that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.

Permission is granted to copy and distribute translations of this manual
into another language, under the above conditions for modified versions.

@end titlepage

@setfilename notes-p3-921001.info
@c         PROOFREADING: set FIXMES to include FIXME text in formatted
@c         output
@clear FIXMES

@ifinfo
@node Top
@top Progressive p3-921001
@end ifinfo

@menu
* Introduction::                Overview
* Versions::                    Closest FSF Versions
* New::                         New in This Release
* Limits::                      Limitations and Warnings
* Cross::                       Cross-Development: Special Considerations
* Rebuilding::                  Rebuilding from Source
* Bugs::                        Known Bugs
* Cygnus-FSF::                  Cygnus Progressive Releases and the FSF
* Cygnus-Support::              About Cygnus Support
@end menu

@node Introduction
@chapter Overview

@table @strong
@item Cygnus Support Developer's Kit
@item Progressive Release p3-921001
@end table

This is the first Progressive Release where several standard
@dfn{cross-development} configurations are available.  A
cross-development configuration is for developing software to run on a
different machine (the @dfn{target}) than the development tools
themselves (which run on the @dfn{host})---for example, you might use a
SPARCstation to generate and debug code for an AMD 29K-based board.

Naturally, we also continue to offer @dfn{native} configurations, where
the tools and your code run on the same kind of machine.

This table shows the host/target combinations available:

@ifinfo
@example
       \ HOST |                   DEC   IBM   SGI
TARGET  \     | SUN3  SUN4  SOL2  STN   RS6K  IRIS  DOS  HP300  HP700
--------------+--------------------------------------------------------
Native        |  X     X     X     X     X     X     
68k VxWorks   |  X     X           X     X     X           X      X
68k a.out     |  X     X           X                 X            X
68k coff      |        X           O                 O
29k UDI       |        X                             X
ix86 a.out    |        X           O                 O
i960 VxWorks  |        O           O     X                        O
i960 Nindy    |        O           O
SPARC VxWorks |        X                                               
SPARC a.out   |        O            

X     = on the shelf                     
O     = may be custom built
68k   = 68000, 68010, 68020, 68030, 68040
ix86  = 386, 486
i960  = KA, KB, CA
SPARC = SPARC, SPARClite
@end example
@end ifinfo

@tex
{\def\X{\vrule height 0.4em width0.4em}
\halign{\hfill \rm #\ &\bf\hfil # \hfil\ &\bf\hfil # \hfil\ &\bf\hfil #
\hfil\ &\bf\hfil # \hfil\ &\bf\hfil # \hfil\ &\bf\hfil #
\hfil\ &\bf\hfil # \hfil\ &\bf\hfil # \hfil\ & \bf\hfil # \hfil\cr
\cr
          &Sun  &Sun  &Sol  &DEC    &IBM &SGI &   &HP    &HP\cr
\bf TARGET&3    &4    &2    &stn    &rs6k&Iris&DOS&300   &700   \cr
\noalign{\strut\hrule}
\noalign{\strut}
\it Native&\X  &\X  &\X  &\X    &\X &\X \cr
68k VxWorks&\X  &\X  &     &\X    &\X &\X &   & \X  & \X  \cr
68k a.out &\X  &\X  &     &\X    &    &    &\X&      & \X  \cr
68k coff  &     &\X  &     &\ *   &    &    &\ *&      &      \cr
29k UDI   &     &\X  &     &       &    &    &\X&      &      \cr
iX86 a.out&     &\X  &     &\ *   &    &    &\ *&      &      \cr
i960 VxWorks&   &\ * &     &\ *   &\X &    &   &      &\ *  \cr
i960 Nindy&     &\ * &     &\ *   &    &    &   &      &      \cr
SPARC VxWorks&  &\X  &     &       &    &    &   &      &      \cr
SPARC a.out&    &\ * &     &       &    &    &   &      &      \cr
\cr}
\halign{\rm\hfil #\quad$=$\quad&\rm #\hfil\cr
\X&on the shelf\cr
\ *&custom tape\cr
\cr
68k&Motorola 68000, 68010, 68020, 68030, 68040\cr
iX86&Intel 386, 486\cr
i960&Intel 960 KA, KB, CA\cr
SPARC&SPARC, SPARClite\cr
\cr}}
@end tex

Your tape is labeled with @samp{host=@var{platform}} to indicate the
host for that configuration.  To avoid ambiguity, these names use a
three-part naming scheme which identifies the CPU, vendor, and
operating system:

@table @r
@item Sun-3
@code{m68k-sun-sunos411}

@item Sun-4
@code{sparc-sun-sunos411}

@item Solaris 2
@code{sparc-sun-solaris2}

@item DECstation
@code{mips-dec-ultrix}

@item SGI Iris
@code{mips-sgi-irix4}

@item IBM RS6000
@code{rs6000-ibm-aix}

@item HP-700
@code{hppa1.1-hp-hpux}

@item HP-300
@code{m68k-hp-hpux}

@item DOS
@code{i386-gen-dos}
@end table

If you have a cross development tape, the label also indicates
@samp{target=@var{machine}} to identify the target for that
configuration.  A two-part naming scheme identifies CPU and object code
format or cross-development environment:

@table @r
@item Motorola 680x0 family
@code{m68k-aout}---a.out object code format.
@code{m68k-coff}---coff object code format.
@code{m68k-vxworks}---VxWorks environment.

@item Intel 960 family
@code{i960-vxworks}---VxWorks environment.
@code{i960-nindy}---Nindy monitor.

@item AMD 29000 family
@code{a29k-amd-udi}---UDI monitor interface.  (To use the MINIMON
interface, use this configuration with the program @code{MONTIP},
available from AMD at no charge.)

@item SPARC family
@code{sparc-vxworks}---VxWorks environment.
@code{sparc-aout}---a.out object code format.

@item Intel 386 family
@code{i386-aout}---a.out object code format.
@end table

In cross-development configurations, each tool in the Developer's Kit is
named with the identifying string as a prefix.  For example, if the C
compiler is configured to generate COFF format code for the Motorola
680x0 family, the compiler is installed as @file{m68k-coff-gcc}.

@node Versions
@chapter Closest FSF Versions

Cygnus Support devotes much of its effort to integrating and improving
free software.  In fact, Cygnus employees are the primary developers of
several important components of the GNU tool-chain (on behalf of the
Free Software Foundation).  However, for programs whose FSF releases are
issued elsewhere, our releases are often slightly ahead of the nearest
corresponding FSF version.  We reintegrate our sources with the FSF as
frequently as possible without compromising the stability of the
integrated toolchain.

These are the closest corresponding FSF releases of the GNU development
tools:

@table @sc
@item @emph{Program}
@emph{Closest FSF version}
@item gcc/g++
pre-2.3

@item gdb
4.6.5 (maintained at Cygnus)

@item make
3.62.16 (not supplied for DOS hosts)

@item libg++
2.2.2 (maintained at Cygnus)
@end table

For all cross-development configurations, and on Sun-4 (other than
Solaris-2) and Sun-3 native configurations, these supporting programs
are also included:

@table @sc
@item as
1.91

@item ld
1.97.1 (maintained at Cygnus)

@item Binary Utilities
1.97 (maintained at Cygnus)
@end table

@sp 4
A Progressive Release of @sc{gnu} Emacs is also available
separately from Cygnus Support for selected hosts.

@node New
@chapter New in This Release

@table @strong
@item Cross-Development
The focus on cross development in release p3-921001 makes standard
support available for the first time for many embedded systems
applications.  The additional testing, configuration, and cleanup work
required has also made the native configurations even more robust.

@item New Hosts
There is a new native configuration, the Solaris-2 environment (SunOS
5.0), and three new hosts for cross-development only---HP-300, HP-700,
and DOS.

@item C library
We have assembled, improved, and documented a standard C subroutine library
@file{libc.a} and C mathematical subroutine library @file{libm.a}.
These are @emph{not} GNU libraries, so there are no additional
code distribution requirements for programs that use them.

@item C++
@code{g++} and @code{libg++} continue to grow more robust.  You can 
compile many popular applications and class libraries with GNU C++,
including @code{groff} and Rogue Wave.

This release of @code{g++} is still unable to build the entire NIHCL and
InterViews libraries, but the @code{g++} renovation project (underway)
will address these incompatibilities.

@item GDB symbol quoting and completion
The GNU debugger will interactively help you select among similar (or
overloaded) names, with extensions to its command-line completion
facilities to apply completion to symbols, and to allow you to quote
symbols in order to alter the scope of completion.
@end table

@node Limits
@chapter Limitations and Warnings

In this release, some of the supported systems don't run some of the
supporting GNU programs, and one system (the RS/6000) has a number of
special requirements.