No description
Find a file
Stan Shebs 7517f04bc4 * remote.c: Pacify --enable-build-warnings, reformat code
to conform to standards, fix spelling errors.
	(ishex, stubhex, record_currthread, etc): Declare.
	(ishex, stubhex): Declare char arg as int.
	(pack_string): Comment out, never used but possibly useful.
	(threadref_to_int, remote_get_threadinfo, etc): Make static.
1999-01-06 20:14:30 +00:00
bfd 1999-01-04 Jason Molenda (jsm@bugshack.cygnus.com) 1999-01-05 00:27:19 +00:00
binutils This commit was manufactured by cvs2svn to create branch 'FSF'. 1998-12-21 20:06:34 +00:00
config * configure.in: makefile stub for cygwin target is probably 1998-12-31 01:37:06 +00:00
gas * Test for PR 18665, from sky branch. 1999-01-06 12:47:21 +00:00
gdb * remote.c: Pacify --enable-build-warnings, reformat code 1999-01-06 20:14:30 +00:00
gprof This commit was manufactured by cvs2svn to create branch 'FSF'. 1998-12-21 20:06:34 +00:00
include * cgen.h (CGEN_ATTR_VALUE_TYPE): New typedef. 1999-01-05 21:55:55 +00:00
intl
ld (Ugh. Last checkin was supposed to have been aborted. Oops.) 1999-01-03 23:55:33 +00:00
mmalloc
opcodes * Fix for PR 18665, from sky branch. 1999-01-06 12:50:58 +00:00
readline * configure.in: Use LOCAL_CFLAGS rather than CFLAGS for 1999-01-06 17:26:06 +00:00
sim * Makefile.in (MAIN_INCLUDE_DEPS): Delete. 1999-01-06 03:04:25 +00:00
.cvsignore
.Sanitize This commit was manufactured by cvs2svn to create branch 'FSF'. 1998-12-21 20:06:34 +00:00
Build-A-Release.mk
ChangeLog * configure.in: libtermcap.a should be built when cygwin is the 1998-12-30 06:18:02 +00:00
config-ml.in
config.guess
config.if
config.sub This commit was manufactured by cvs2svn to create branch 'FSF'. 1998-12-21 20:06:34 +00:00
configure This commit was manufactured by cvs2svn to create branch 'FSF'. 1998-12-21 20:06:34 +00:00
configure.bat
configure.in * configure.in: makefile stub for cygwin target is probably 1998-12-31 01:37:06 +00:00
COPYING
COPYING.LIB
DOC.Sanitize This commit was manufactured by cvs2svn to create branch 'FSF'. 1998-12-21 20:06:34 +00:00
install-sh
install-texi.in
Install.in
intro.texi
ltconfig
ltmain.sh
makeall.bat
Makefile.in This commit was manufactured by cvs2svn to create branch 'FSF'. 1998-12-21 20:06:34 +00:00
makefile.vms
mdate-sh
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
Pack-A-Progressive
README
setup.com
symlink-tree
tape-labels-tex.in
test-build.mk
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.