Go to file
Zack Weinberg c334349bda gcc.c (execute): If a subprocess gets a fatal signal...
* gcc.c (execute): If a subprocess gets a fatal signal, report
	strsignal() of the signal number, and ask for a bug report.
	Do not do this for SIGPIPE if there's already been an error.

	* tradcpp.c: Don't include signal.h.  Don't catch SIGPIPE.
	Delete pipe_closed.

From-SVN: r35006
2000-07-13 04:43:47 +00:00
boehm-gc
config
contrib gcc_update (files_and_dependencies): Remove generated YACC files. 2000-07-12 07:12:56 +00:00
etc
gcc gcc.c (execute): If a subprocess gets a fatal signal... 2000-07-13 04:43:47 +00:00
include
INSTALL
libchill
libf2c Daily bump. 2000-07-12 01:45:07 -06:00
libffi
libiberty cplus-dem.c (main): fflush() after emitting last char before waiting for input. 2000-07-07 13:50:49 +00:00
libio
libjava Add missing imports. 2000-07-12 22:24:00 +01:00
libobjc
libstdc++ stl_function.h (bind1st, bind2nd): Rename __opr to __oper, as __opr is used internally by egcs. 2000-07-10 17:04:22 -04:00
libstdc++-v3 docs: Update sourceware->sources in every HTML file. 2000-07-11 21:45:08 +00:00
texinfo
zlib
.cvsignore
ChangeLog * symlink-tree: Check number of arguments. 2000-07-07 07:18:48 -06:00
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in Fix CXX_FOR_TARGET to add -L libstdc++ 2000-07-06 00:50:01 +00:00
missing
mkinstalldirs
move-if-change
README
symlink-tree * symlink-tree: Check number of arguments. 2000-07-07 07:18:48 -06:00
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.