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