Go to file
Mark Kettenis a7769679c2 * config/i386/tm-i386.h: Add forward declaration of `struct value'.
(FIX_CALL_DUMMY): Redefined to call i386_fix_call_dummy.
(i386_fix_call_dummy): Add prototype.
* i386-tdep.c (i386_fix_call_dummy): New function based on the
code from the old FIX_CALL_DUMMY macro.
2000-06-12 01:44:35 +00:00
bfd * configure.in (VERSION): Update to show this is the CVS mainline. 2000-06-08 19:00:02 +00:00
binutils * configure.in (VERSION): Update to show this is the CVS mainline. 2000-06-08 19:00:02 +00:00
config
etc
gas Don't treat `;' as a line separator by default. 2000-06-09 00:00:04 +00:00
gdb * config/i386/tm-i386.h: Add forward declaration of `struct value'. 2000-06-12 01:44:35 +00:00
gprof * configure.in (VERSION): Update to show this is the CVS mainline. 2000-06-08 19:00:02 +00:00
include * avr.h: clr,lsl,rol, ... moved after add,adc, ... 2000-06-09 18:02:05 +00:00
intl
ld * configure.in (VERSION): Update to show this is the CVS mainline. 2000-06-08 19:00:02 +00:00
libiberty * Makefile.in: add EXTRA_INCS 2000-06-06 17:52:20 +00:00
mmalloc * mmalloc/Makefile.in (install-info): Make sure $(infodir) exists. 2000-05-17 11:45:56 +00:00
opcodes * avr-dis.c (avr_operand): Bugfix for jmp/call address. 2000-06-09 17:58:33 +00:00
readline
sim sh-dsp support, simulator speedup by using host byte order: 2000-06-07 14:59:16 +00:00
texinfo Import texinfo.tex from texinfo-4.0. 2000-05-31 10:18:58 +00:00
.cvsignore
ChangeLog new file - notes about using --enable-maintainer-mode 2000-06-07 21:31:48 +00:00
config-ml.in
config.guess * config.sub: Import CVS version 1.167 Tue May 30 09:00:07 2000. 2000-05-30 09:08:59 +00:00
config.if
config.sub * config.sub: Import CVS version 1.167 Tue May 30 09:00:07 2000. 2000-05-30 09:08:59 +00:00
configure 20000-05-21 H.J. Lu (hjl@gnu.org) 2000-05-21 16:57:14 +00:00
configure.in * configure.in (hppa*64*-*-*): Do build ld for this configuration. 2000-05-18 16:58:06 +00:00
COPYING
COPYING.LIB
djunpack.bat * djunpack.bat: Change the Sed script to replace @V@ in fnchange.lst 2000-05-08 15:13:30 +00:00
install-sh
ltconfig
ltmain.sh 2000-05-13 Alexandre Oliva <oliva@lsd.ic.unicamp.br> 2000-05-13 21:19:50 +00:00
MAINTAINERS Typo. bfd@sourceware -> binutils@sourceware. 2000-05-18 00:29:13 +00:00
Makefile.in 20000-05-21 H.J. Lu (hjl@gnu.org) 2000-05-21 16:57:14 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode new file - notes about using --enable-maintainer-mode 2000-06-07 21:31:48 +00:00
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.