| 1 | \input cyginfo |
| 2 | @c WARNING!!! |
| 3 | @c THESE INSTALL NOTES ARE NOT YET GENERAL-PURPOSE |
| 4 | @c SINCE THERE IS NO ESTABLISHED INSTALLATION PROCEDURE FOR CYGNUS |
| 5 | @c RELEASES FROM THE DEVELOPMENT DIRECTORIES. |
| 6 | @c THESE NOTES MUST BE EDITED BY HAND FOR EACH RELEASE. |
| 7 | @c $Id$ |
| 8 | @setfilename README.info |
| 9 | @iftex |
| 10 | @c We don't actually want a titlepage; HEADINGSon is usually called by |
| 11 | @c @end titlepage to turn on footers and headers. |
| 12 | @HEADINGSon |
| 13 | @setchapternewpage off |
| 14 | @finalout |
| 15 | @end iftex |
| 16 | @c |
| 17 | @c WARNING: NONSTANDARD USAGE we need \tensf for print, without |
| 18 | @c upsetting info. We weren't using @b in this note, so I redefine it: |
| 19 | @tex |
| 20 | \global\def\b#1{{\tensf #1}} |
| 21 | \global\def\date{November 1991} |
| 22 | \global\def\manvers{release m88k--11--91} |
| 23 | \parindent=0pt |
| 24 | @end tex |
| 25 | |
| 26 | @node Top, Contents, (dir), (dir) |
| 27 | @unnumbered Installation and Release Notes |
| 28 | |
| 29 | |
| 30 | @table @strong |
| 31 | @item Cygnus Support M88K Developer's Kit |
| 32 | @item release m88k--11--91 |
| 33 | @iftex |
| 34 | @item @date |
| 35 | @item {} |
| 36 | @item Contents |
| 37 | @display |
| 38 | @altref |
| 39 | @ref{Contents,,Release Contents}. |
| 40 | @ref{Platforms,,Supported Platforms}. |
| 41 | @ref{Installing,,Installation From Tape}. |
| 42 | @ref{Removing,,Removing the Developer's Kit}. |
| 43 | @ref{Cygnus-FSF,,Cygnus and FSF Releases}. |
| 44 | @ref{Cygnus-Support,,Cygnus Support}. |
| 45 | @altref |
| 46 | @end display |
| 47 | @end iftex |
| 48 | @end table |
| 49 | |
| 50 | @menu |
| 51 | * Contents:: Release Contents |
| 52 | * Platforms:: Supported Platforms |
| 53 | * Disk:: Disk Space |
| 54 | * Installing:: Installation From Tape |
| 55 | * Removing:: Removing the Developer's Kit |
| 56 | * Bugs:: Where to report bugs |
| 57 | * Cygnus-FSF:: Cygnus and FSF Releases |
| 58 | * Cygnus-Support:: Cygnus Support |
| 59 | @end menu |
| 60 | |
| 61 | This note is about the Cygnus M88K Developer's Kit: what's in it and how to |
| 62 | install it. |
| 63 | |
| 64 | @node Contents, Platforms, Top, Top |
| 65 | @unnumberedsec Release Contents |
| 66 | |
| 67 | This Developer's Kit is a Cygnus Support Release: the programs in the |
| 68 | release have been tested both individually and as a coordinated suite of |
| 69 | tools. |
| 70 | |
| 71 | The programs in this Developer's Kit are shipped as binaries, |
| 72 | preconfigured to run on Motorola 88K-based workstations ``out of the |
| 73 | box.'' |
| 74 | |
| 75 | We also include the full source code. |
| 76 | |
| 77 | The individual programs are: |
| 78 | |
| 79 | @itemize @bullet |
| 80 | @item |
| 81 | @sc{gnu emacs} (v18.57), the extensible text editor |
| 82 | @item |
| 83 | @sc{gcc} (v1.95.02), the @sc{gnu} C compiler |
| 84 | @item |
| 85 | @sc{g++} (v1.95.02), the @sc{gnu} C++ compiler |
| 86 | @item |
| 87 | @sc{gdb} (v4.2.2), the @sc{gnu} debugger |
| 88 | @end itemize |
| 89 | |
| 90 | @node Platforms, Disk, Contents, Top |
| 91 | @unnumberedsec Supported Platforms |
| 92 | @table @strong |
| 93 | @item 88open BCS |
| 94 | Release m88k--11--91 of the Cygnus Developer's Kit is supported on any |
| 95 | system running an 88open compliant operating system. |
| 96 | |
| 97 | @item Other Platforms |
| 98 | The Developer's Kit is likely to work when compiled for other machines, |
| 99 | but no other platforms are currently |
| 100 | @iftex |
| 101 | (@date) |
| 102 | @end iftex |
| 103 | supported by Cygnus as part of Release m88k--11--91. @refill |
| 104 | @end table |
| 105 | @node Disk, Installing, Platforms, Top |
| 106 | @unnumberedsec Disk Space |
| 107 | |
| 108 | The total space required to extract and install binaries for |
| 109 | all programs in Release m88k--11--91 is 32 megabytes. |
| 110 | |
| 111 | The software is configured to go in @file{/usr/cygnus}; if you have |
| 112 | space available, but not in the same file system as @file{/usr}, you can |
| 113 | create @file{/usr/cygnus} as a symbolic link to the file system where |
| 114 | you do have the space available. |
| 115 | |
| 116 | @node Installing, Removing, Disk, Top |
| 117 | @unnumberedsec Installation From Tape |
| 118 | |
| 119 | @iftex |
| 120 | This note shows computer output in @code{typewriter font}. User input |
| 121 | is indicated by a @b{sans-serif font}. Comments appear in @i{italic |
| 122 | font}. |
| 123 | @end iftex |
| 124 | In all examples, the system name is assumed to be ``@code{eg};'' we show the |
| 125 | system prompt as @samp{eg$}. |
| 126 | |
| 127 | @menu |
| 128 | * Tape-Reading:: Reading the Tape |
| 129 | * Running:: Running the Programs |
| 130 | @end menu |
| 131 | |
| 132 | @node Tape-Reading, Running, Installing, Installing |
| 133 | @unnumberedsubsec Reading the Tape |
| 134 | |
| 135 | For certification purposes, the M88K Developer's Kit is packaged as two |
| 136 | QIC 150 tapes; one containing only binaries for all programs, and one |
| 137 | containing source. |
| 138 | |
| 139 | Load the Cygnus Support binary tape into your system's tape drive. |
| 140 | You can extract the complete tape contents as follows: |
| 141 | @lisp |
| 142 | @cartouche |
| 143 | eg$ @b{mkdir /usr/cygnus} @i{only if /usr/cygnus did not exist} |
| 144 | eg$ @b{cd /usr/cygnus} |
| 145 | eg$ @b{tar xfv /dev/TAPE} |
| 146 | @end cartouche |
| 147 | @end lisp |
| 148 | |
| 149 | This will create subdirectories @file{bin}, @file{lib}, and @file{man}, |
| 150 | with the conventional meanings. |
| 151 | |
| 152 | If you also want the source, for reference or modification, load the |
| 153 | Cygnus Support source tape into your tape drive, and repeat the |
| 154 | @code{tar} command: |
| 155 | @lisp |
| 156 | @cartouche |
| 157 | eg$ @b{tar xfv /dev/TAPE} |
| 158 | @end cartouche |
| 159 | @end lisp |
| 160 | |
| 161 | @page |
| 162 | @node Running, , Tape-Reading, Installing |
| 163 | @unnumberedsubsec Running the Programs |
| 164 | @c [FIXME-future:] orig includes fixincluded files... "bogus |
| 165 | @c but easiest". In some future release, CUST MUST RUN fixincludes ONCE PER OS! |
| 166 | @c [FIXME] how to select cross vs native compiler? |
| 167 | Any users who wish to run the Cygnus development tools will need to make |
| 168 | sure the @code{PATH} environment variable will find them. For example, |
| 169 | the following should go in a Bourne shell initialization file: |
| 170 | @lisp |
| 171 | @cartouche |
| 172 | @b{PATH=/usr/cygnus/bin:$PATH} |
| 173 | @end cartouche |
| 174 | @end lisp |
| 175 | |
| 176 | To use the Cygnus man pages on line, you'll need to install them in your |
| 177 | system's @file{/usr/catman/u_man/man1} directory. For example, you can |
| 178 | copy them like this: |
| 179 | @lisp |
| 180 | @cartouche |
| 181 | eg$ @b{cp /usr/cygnus/man/man1/* /usr/catman/u@t{_}man/man1} |
| 182 | @end cartouche |
| 183 | @end lisp |
| 184 | |
| 185 | @node Removing, Bugs, Installing, Top |
| 186 | @unnumberedsec Removing the Developer's Kit |
| 187 | To remove this release of the Developer's Kit from your system |
| 188 | (if, eventually, you no longer want it): |
| 189 | @enumerate |
| 190 | @item |
| 191 | remove the man pages for this release from your system's |
| 192 | @file{/usr/catman/u_man/man1} directory, if you had chosen to install |
| 193 | them there. For example, in a Bourne-compatible shell, |
| 194 | @lisp |
| 195 | @cartouche |
| 196 | eg$ @b{cd /usr/cygnus/man/man1} |
| 197 | eg$ @b{for m in *; do} |
| 198 | eg> @b{rm /usr/catman/u@t{_}man/man1/$m} |
| 199 | eg> @b{done} |
| 200 | @end cartouche |
| 201 | @end lisp |
| 202 | @item |
| 203 | delete the directory @file{/usr/cygnus} and all its contents. |
| 204 | @end enumerate |
| 205 | |
| 206 | @node Bugs, Cygnus-FSF, Removing, Top |
| 207 | @unnumberedsec Where to report bugs |
| 208 | If you find a bug in this release, please report it to Cygnus Support. |
| 209 | The easiest way to report a bug is via Internet electronic mail to |
| 210 | @samp{bugs@@cygnus.com}; for other contact methods, |
| 211 | @pxref{Cygnus-Support,,Cygnus Support}. @strong{Do not report these bugs |
| 212 | directly to the GNU project} at the Free Software Foundation! Cygnus is |
| 213 | distributing an early release of advanced versions of the GNU compiler |
| 214 | and development tools, and we therefore have full responsibility for |
| 215 | supporting this release. @strong{The FSF will not respond to bugreports |
| 216 | on this software} until release 2.0 of the compilers. You, the FSF, and |
| 217 | Cygnus will all be best served if you send bugreports directly to Cygnus |
| 218 | Support. |
| 219 | |
| 220 | @page |
| 221 | @node Cygnus-FSF, Cygnus-Support, Bugs, Top |
| 222 | @unnumberedsec Cygnus and FSF Releases |
| 223 | |
| 224 | The tools in this Developer's Kit are originally from the Free Software |
| 225 | Foundation, and versions of all these tools can be obtained from the FSF |
| 226 | as well as from Cygnus. Release m88k--11--91 contains the most current |
| 227 | versions; similar versions of the compilers, in particular, will |
| 228 | eventually be available from the FSF as version 2.00. In general, |
| 229 | Cygnus Releases add to FSF software as follows: |
| 230 | |
| 231 | @itemize @bullet |
| 232 | @item |
| 233 | Commercial support is available. Cygnus adds value to FSF releases in |
| 234 | large measure by offering outstanding support services. |
| 235 | @item |
| 236 | Bug fixes. Cygnus performs necessary repairs to bugs discovered |
| 237 | during testing, and also tracks and includes bug fixes developed for |
| 238 | other Cygnus customers or distributed over the Internet. |
| 239 | @item |
| 240 | Documentation. Cygnus has revised and added to available FSF |
| 241 | documentation to give you better descriptions of all the software tools. |
| 242 | @item |
| 243 | Coordination. The tools in your Developer's Kit are certified to work |
| 244 | together; you need not worry about one tool being ahead of another. |
| 245 | @end itemize |
| 246 | |
| 247 | @tex |
| 248 | @page |
| 249 | @end tex |
| 250 | @node Cygnus-Support, , Cygnus-FSF, Top |
| 251 | @unnumberedsec Cygnus Support |
| 252 | |
| 253 | Cygnus Support was founded in 1989 to provide commercial support for |
| 254 | free software. Cygnus supplies products and services that benefit |
| 255 | advanced development groups by allowing them to @emph{use} |
| 256 | state-of-the-art tools instead of @emph{maintaining} them. With Cygnus |
| 257 | Support, sites that once were forced to do their own tool support can |
| 258 | recover that valuable staff time. Former users of proprietary software |
| 259 | now may choose supported free software, combining the advantages of both |
| 260 | worlds. |
| 261 | |
| 262 | Free software is faster, more powerful, and more portable than its |
| 263 | proprietary counterparts. It evolves faster because users who want to |
| 264 | make improvements are free to do so. Cygnus tracks these |
| 265 | improvements and integrates them into tested, stable versions ready |
| 266 | for commercial use, then backs this software with comprehensive |
| 267 | support. |
| 268 | |
| 269 | With Cygnus Support as your partner, you will have the software and |
| 270 | the support you need to meet your business objectives better. Cygnus |
| 271 | is intimately familiar with this software from extensive experience |
| 272 | using, debugging, and implementing it. You get direct access to the |
| 273 | most qualified support people: the authors of that software. |
| 274 | |
| 275 | We provide ``vintage'' releases---stable versions which have been |
| 276 | though extensive use and testing---or up-to-the minute sources, for |
| 277 | those who need the very latest version. Vintage releases undergo at |
| 278 | least nine months of intensive use before certification as vintage. |
| 279 | |
| 280 | Because all our improvements are also free software, you can |
| 281 | distribute them widely within your organization, or to your customers, |
| 282 | without extra cost. |
| 283 | |
| 284 | @display |
| 285 | Cygnus Support |
| 286 | 814 University Avenue |
| 287 | Palo Alto, CA 94301, USA |
| 288 | |
| 289 | +1 415 322 3811 |
| 290 | |
| 291 | email: @code{info@@cygnus.com} |
| 292 | fax: +1 415 322 3270 |
| 293 | @end display |
| 294 | |
| 295 | @bye |