1 | README for GNU development tools |
---|
2 | |
---|
3 | This directory contains various GNU compilers, assemblers, linkers, |
---|
4 | debuggers, etc., plus their support routines, definitions, and documentation. |
---|
5 | |
---|
6 | If you are receiving this as part of a GDB release, see the file gdb/README. |
---|
7 | If with a binutils release, see binutils/README; if with a libg++ release, |
---|
8 | see libg++/README, etc. That'll give you info about this |
---|
9 | package -- supported targets, how to use it, how to report bugs, etc. |
---|
10 | |
---|
11 | It is now possible to automatically configure and build a variety of |
---|
12 | tools with one command. To build all of the tools contained herein, |
---|
13 | run the ``configure'' script here, e.g.: |
---|
14 | |
---|
15 | ./configure |
---|
16 | make |
---|
17 | |
---|
18 | To install them (by default in /usr/local/bin, /usr/local/lib, etc), |
---|
19 | then do: |
---|
20 | make install |
---|
21 | |
---|
22 | (If the configure script can't determine your type of computer, give it |
---|
23 | the name as an argument, for instance ``./configure sun4''. You can |
---|
24 | use the script ``config.sub'' to test whether a name is recognized; if |
---|
25 | it is, config.sub translates it to a triplet specifying CPU, vendor, |
---|
26 | and OS.) |
---|
27 | |
---|
28 | If you have more than one compiler on your system, it is often best to |
---|
29 | explicitly set CC in the environment before running configure, and to |
---|
30 | also set CC when running make. For example (assuming sh/bash/ksh): |
---|
31 | |
---|
32 | CC=gcc ./configure |
---|
33 | make |
---|
34 | |
---|
35 | A similar example using csh: |
---|
36 | |
---|
37 | setenv CC gcc |
---|
38 | ./configure |
---|
39 | make |
---|
40 | |
---|
41 | Much of the code and documentation enclosed is copyright by |
---|
42 | the Free Software Foundation, Inc. See the file COPYING or |
---|
43 | COPYING.LIB in the various directories, for a description of the |
---|
44 | GNU General Public License terms under which you can copy the files. |
---|
45 | |
---|
46 | REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info |
---|
47 | on where and how to report problems. |
---|