Go to file
Craig Burley e67ac8e6ee gcc.c: Fix commentary describing %g, %u, %U, and %O.
* gcc.c: Fix commentary describing %g, %u, %U, and %O.
        * gcc.c (do_spec_1): Fix support for %O so the
        temporary file name made for it the first time
        gets reused subsequently.

From-SVN: r21449
1998-07-28 15:33:41 -06:00
config
contrib * compare_tests: New script. 1998-07-27 15:12:03 -06:00
etc
gcc gcc.c: Fix commentary describing %g, %u, %U, and %O. 1998-07-28 15:33:41 -06:00
include
INSTALL Fix typo. 1998-07-18 15:48:44 +00:00
libf2c Makefile.in (s-libe77, [...]): Rely on VPATH, dropping explicit use of $(srcdir) in various places. 1998-07-25 05:38:51 +00:00
libiberty cplus-dem.c (type_kind_t): New type. 1998-07-28 11:45:32 +00:00
libio
libstdc++ tmap.cc: Use less<int>. 1998-07-16 21:30:01 -04:00
texinfo
xiberty
.cvsignore
ChangeLog config.guess: (*-pc-sco3.2v5) Add detection for Pentium II. 1998-07-19 18:00:52 -06:00
config-ml.in
config.guess config.guess: (*-pc-sco3.2v5) Add detection for Pentium II. 1998-07-19 18:00:54 -06:00
config.sub
configure
configure.in
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS Add myself as jump.c maintainer. 1998-07-14 14:20:43 -07:00
Makefile.in
missing
mkinstalldirs
move-if-change
README
symlink-tree
ylwrap

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.

If you are receiving this as part of a GDB release, see the file gdb/README.
If with a binutils release, see binutils/README;  if with a libg++ release,
see libg++/README, etc.  That'll give you info about this
package -- supported targets, how to use it, how to report bugs, etc.

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.:

	./configure 
	make

To install them (by default in /usr/local/bin, /usr/local/lib, etc),
then do:
	make install

(If the configure script can't determine your type of computer, give it
the name as an argument, for instance ``./configure sun4''.  You can
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.)

If you have more than one compiler on your system, it is often best to
explicitly set CC in the environment before running configure, and to
also set CC when running make.  For example (assuming sh/bash/ksh):

	CC=gcc ./configure
	make

A similar example using csh:

	setenv CC gcc
	./configure
	make

Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.