2
0
mirror of git://gcc.gnu.org/git/gcc.git synced 2024-12-29 19:25:55 +08:00
Go to file
K. Richard Pixley 9aeba741d9 fixincludes: discard empty C++ comments, as found in sys/time.h on hpux-11.0.
* fixincludes: discard empty C++ comments, as found in sys/time.h
        on hpux-11.0.

From-SVN: r19221
1998-04-15 03:17:24 -06:00
config
contrib/fixinc
etc
gcc fixincludes: discard empty C++ comments, as found in sys/time.h on hpux-11.0. 1998-04-15 03:17:24 -06:00
include
INSTALL
libf2c
libiberty * cplus-dem.c: Sync with gcc. 1998-04-09 18:45:43 -06:00
libio
libstdc++ (__stl_prime_list): Mark last two numbers as unsigned long since they are... 1998-04-07 18:39:16 +00:00
texinfo * configure.in: only set HAVE_LIBZ if zlib.h exists 1998-04-12 14:00:34 -06:00
xiberty
.cvsignore
ChangeLog configure: Define DEFAULT_M4 by searching PATH. 1998-04-14 04:34:37 -06:00
config-ml.in
config.guess
config.sub
configure configure: Define DEFAULT_M4 by searching PATH. 1998-04-14 04:34:37 -06:00
configure.in
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in * Makefile.in (INSTALL_MODULES): Remove texinfo. 1998-04-12 13:58:53 -06:00
missing
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
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.