/[gnats]/gnats/README
ViewVC logotype

Diff of /gnats/README

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2 by yngves, Wed Nov 28 15:16:46 2001 UTC revision 1.3 by chewie, Mon Oct 31 05:03:16 2005 UTC
# Line 1  Line 1 
                    README for GNU development tools  
1    
2  This directory contains various GNU compilers, assemblers, linkers,                             Installing GNATS
3  debuggers, etc., plus their support routines, definitions, and documentation.                                Version 4
4    
5  If you are receiving this as part of a GDB release, see the file gdb/README.  This is a very brief overview of the installation procedure for GNATS
6  If with a binutils release, see binutils/README;  if with a libg++ release,  version 4.  It is strongly recommended that you refer to the file
7  see libg++/README, etc.  That'll give you info about this  gnats.texi or the online manual currently located at
8  package -- supported targets, how to use it, how to report bugs, etc.  http://sources.redhat.com/gnats/gnats_toc.html, specifically Chapter
9    3, Installing GNATS, before you try to install and operate GNATS.  The
10    items marked `*Note' below refer to sections of chapter 3 in the
11    GNATS manual.
12    
 It is now possible to automatically configure and build a variety of  
 tools with one command.  To build all of the tools contained herein,  
 run the ``configure'' script here, e.g.:  
13    
14          ./configure  Installing GNATS
15          make  ================
16    
17  To install them (by default in /usr/local/bin, /usr/local/lib, etc),  There are several steps you need to follow to fully configure and
18  then do:  install GNATS on your system.  You need `root' access in order to
19          make install  create a new account for the user `gnats' and to install the GNATS
20    utilities.  You may need `root' access on some systems in order to set
21    up mail aliases and to allow this new account access to `cron' and
22    `at'.
23    
24  (If the configure script can't determine your type of computer, give it  If you are updating an older version of GNATS rather than installing
25  the name as an argument, for instance ``./configure sun4''.  You can  from scratch, see the UPGRADING file.
 use the script ``config.sub'' to test whether a name is recognized; if  
 it is, config.sub translates it to a triplet specifying CPU, vendor,  
 and OS.)  
26    
27  If you have more than one compiler on your system, it is often best to  NOTE: You will need to have GNU make and GNU Texinfo (version 4.2 or
28  explicitly set CC in the environment before running configure, and to  newer) in order to install GNATS 4.
 also set CC when running make.  For example (assuming sh/bash/ksh):  
29    
30          CC=gcc ./configure  To build GNATS, you must:
         make  
31    
32  A similar example using csh:     * Run `configure', with correct options if the defaults are
33         unsuitable for your site.  *Note Configuring and compiling the
34         software: Configure and make.  Default installation locations are
35         detailed in *Note Where GNATS lives: Default installation
36         locations.
37    
38          setenv CC gcc     * Compile the GNATS programs on your system.  *Note Configuring and
39          ./configure       compiling the software.
         make  
40    
41  Much of the code and documentation enclosed is copyright by     * Create an initial database by using the `mkdb' command.  *Note
42  the Free Software Foundation, Inc.  See the file COPYING or       Installing the default database.
 COPYING.LIB in the various directories, for a description of the  
 GNU General Public License terms under which you can copy the files.  
43    
44  REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info     * Set up periodic jobs, using cron, to handle Problem Reports
45  on where and how to report problems.       arriving by mail.  *Note Setting up periodic reports.
46    
47       * Set up mail aliases for GNATS.  *Note Setting up mail aliases.
48    
49       * Install the GNATS tools and utilities locally, and install the
50         user tools (`query-pr', `edit-pr', `send-pr') on every machine in
51         your local network.  *Note Installing the user tools.
52    
53       * Install the GNATS network daemon `gnatsd'.  *Note Installing the
54         daemon.
55    
56       * Update the local configuration files
57    
58           dbconfig   categories  submitters  responsible
59           states     classes     addresses   gnatsd.user_access
60    
61         in `DATABASEDIR/gnats-adm', as well as the files
62    
63           gnatsd.host_access    databases
64    
65         in `PREFIX/etc/gnats' (usually /usr/local/etc/gnats).
66    
67         *Note Changing your local configuration: Local configuration.
68    
69       * If you have people outside your organization who will be
70         submitting PRs or who are supposed to be able to query and/or
71         edit PRs, you either need to instruct them to obtain and build
72         the GNATS tools `query-pr', `edit-pr' and `send-pr' for their
73         systems or set up a remote access interface to GNATS, such as
74         Gnatsweb.  *Note Installing the user tools.

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26