Go to file
Mark Kettenis a0852bc081 gnu.h: Include <gnu.h> right after <i386/linux.h>...
�
        * config/i386/gnu.h: Include <gnu.h> right after <i386/linux.h>,
        such that we can override its definitions if necessary.
        (CPP_SPEC): New define.  Support processor specific predefines via
        %(cpp_cpu).
        (CC1_SPEC): New define.  Support processor specific compiler
        options via %(cc1_cpu).
        (STARTFILE_SPEC): New define.  Use crt0.o instead of crt1.o for
        -static.

From-SVN: r27406
1999-06-07 15:10:33 -06:00
boehm-gc
config
contrib
etc
gcc gnu.h: Include <gnu.h> right after <i386/linux.h>... 1999-06-07 15:10:33 -06:00
include
INSTALL
libchill
libf2c
libiberty
libio * configure.in: Added DG/UX target fragment 1999-06-01 17:25:17 -06:00
libjava [multiple changes] 1999-06-03 22:29:12 +00:00
libobjc
libstdc++ * std/std_valarray.h: Don't #include unconditionally <alloca.h> 1999-06-05 09:41:22 +00:00
texinfo acconfig.h (libintl.h): Does not include this file here because it will define `NULL' before the system... 1999-06-01 17:52:42 -06:00
zlib
.cvsignore
ChangeLog Cort Dougan <cort@cs.nmt.edu> 1999-05-30 09:05:07 -07:00
config-ml.in
config.guess Cort Dougan <cort@cs.nmt.edu> 1999-05-30 09:05:07 -07:00
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS Added my name to the list, test for write access. 1999-06-01 17:17:25 +00: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.


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.