Go to file
Phil Edwards 9a200b0a07 acinclude.m4 (GLIBCPP_CHECK_CTYPE): Tweaks to message texts for public relations purposes.
2000-10-05  Phil Edwards  <pme@sources.redhat.com>

	* acinclude.m4 (GLIBCPP_CHECK_CTYPE):  Tweaks to message texts
	  for public relations purposes.
	* aclocal.m4:  Regenerated.
	* configure:  Regenerated.

	* docs/ext/howto.html:  Additional explanation about hashing.

From-SVN: r36731
2000-10-05 20:15:29 +00:00
boehm-gc configure.in: Define GC_GCJ_SUPPORT. 2000-09-30 10:54:21 +01:00
config
contrib
etc
gcc gcc.c: Move data on prefixes forward in file and reorganize. 2000-10-05 16:07:24 -04:00
include
INSTALL
libchill
libf2c Daily bump. 2000-10-05 01:45:10 -06:00
libffi
libiberty c-decl.c (c_expand_body): Don't generate RTL if flag_syntax_only. 2000-10-01 19:19:30 +00:00
libio
libjava Updated ChangeLog to reflect patch credit 2000-10-03 18:57:21 +00:00
libobjc
libstdc++
libstdc++-v3 acinclude.m4 (GLIBCPP_CHECK_CTYPE): Tweaks to message texts for public relations purposes. 2000-10-05 20:15:29 +00:00
texinfo
zlib
.cvsignore
ChangeLog Makefile.in (bootstrap): avoid recursion if subdir missing 2000-10-04 14:00:37 -04:00
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
djunpack.bat
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in Makefile.in (bootstrap): avoid recursion if subdir missing 2000-10-04 14:00:37 -04:00
missing
mkdep
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.


Check the INSTALL directory for detailed configuration and installation
instructions.


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.