NetBSD/gnu/dist/toolchain
kristerw 66cf1d6099 Handle comments in macros when the -C flag is specified to the
pre-processor.

This makes code of the form

   #define FOO(X) (BAR(X))
   #define BAR(X) (X)
   #define BAZ    23 /* comment, comment. */
   int foo(void) { return FOO(BAZ); }

be output as expected. (The old behaviour got confused by the ','
within the comment.)
2003-05-26 00:03:50 +00:00
..
bfd elf_fake_sections: fix cast sh_name. 2003-05-09 22:15:17 +00:00
binutils Some e.g. cleanup: replace "eg" with "e.g.,". From Igor Sobrado in PR 19692. 2003-04-07 06:56:38 +00:00
config
contrib
etc
gas
gcc Handle comments in macros when the -C flag is specified to the 2003-05-26 00:03:50 +00:00
gdb Make sure to supply the PS_REGNUM (as a fixed value) so that 2003-04-25 20:13:47 +00:00
gprof
include
install
intl
ld
libchill
libf2c
libiberty
libio Include <string.h>. From Ian Lance Taylor. 2003-05-06 02:31:06 +00:00
libobjc
libstdc++
mmalloc
opcodes
readline
sim
texinfo
.brik
ChangeLog
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
FAQ
faq.html
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in
makefile.vms
md5.sum
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
setup.com
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.