Go to file
Philipp Thomas 4037042b88 POTFILES.in: Remove config/rs6000/netware.h.
2000-10-21  Philipp Thomas  <pthomas@suse.de>

	* POTFILES.in: Remove config/rs6000/netware.h.
	Remove the files moved out of libgcc and over
	to libsupc++.
	* Makefile.in.in (stamp-check-pot): Rename to stamp-check-po.
	(check-po): New, more intuitive target to check POTFILES.in
	for consistency.

From-SVN: r36997
2000-10-21 19:04:38 +00:00
boehm-gc
config
contrib
etc
gcc POTFILES.in: Remove config/rs6000/netware.h. 2000-10-21 19:04:38 +00:00
include
INSTALL
libchill
libf2c Daily bump. 2000-10-21 01:45:08 -06:00
libffi
libiberty
libio iostream.cc (ends): Release the acquired lock. 2000-10-18 18:52:12 +02:00
libjava From Arno J. Klaassen: 2000-10-20 23:25:57 +00:00
libobjc
libstdc++
libstdc++-v3 [multiple changes] 2000-10-21 16:50:29 +00:00
texinfo
zlib Add changelog for previous commit 2000-10-20 08:54:44 +00:00
.cvsignore
ChangeLog Only create gcc/configargs.h if gcc build directory is present 2000-10-17 03:00:51 +00:00
config-ml.in
config.guess
config.if config.if: Search libstdc++-v3/configure.in for INTERFACE, when configured for libstdc++-v3. 2000-10-16 10:00:43 -06:00
config.sub
configure Only create gcc/configargs.h if gcc build directory is present 2000-10-17 03:00:51 +00:00
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
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.