Binutils with MCST patches
Go to file
2000-07-20 16:56:18 +00:00
bfd Fix typo in CRIS entry 2000-07-20 16:35:18 +00:00
binutils 2000-07-19 H.J. Lu <hjl@gnu.org> 2000-07-20 02:45:36 +00:00
config 2000-06-19 Syd Polk <spolk@redhat.com> 2000-06-27 21:50:33 +00:00
etc
gas 2000-07-19 H.J. Lu <hjl@gnu.org> 2000-07-19 17:47:08 +00:00
gdb * thread.c (free_thread): New function. 2000-07-19 21:03:06 +00:00
gprof add MAINTAINERS files 2000-07-05 19:28:06 +00:00
include common.h (EM_CRIS): New machine number. 2000-07-20 15:44:56 +00:00
intl
ld 2000-07-20 H.J. Lu <hjl@gnu.org> 2000-07-20 16:13:26 +00:00
libiberty * testsuite/regress-demangle (failed test): Show result and 2000-07-17 10:45:54 +00:00
mmalloc * mmalloc/Makefile.in (install-info): Make sure $(infodir) exists. 2000-05-17 11:45:56 +00:00
opcodes Revert spurious unrelated changes from last commit. Oops. 2000-07-20 16:56:18 +00:00
readline A few tweaks required to use Readline as part of the DJGPP port of GDB. 2000-07-10 15:22:16 +00:00
sim * m16.igen (break): Call SignalException not sim_engine_halt. 2000-07-20 00:02:22 +00:00
texinfo Update texinfo.tex to version 2000-05-28.15. 2000-07-06 05:39:36 +00:00
.cvsignore Applied Stephane Carrez <Stephane.Carrez@worldnet.fr> patches to add support 2000-06-19 01:22:44 +00:00
ChangeLog * symlink-tree: Check number of arguments. 2000-07-07 13:21:39 +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 TI C54x target added. 2000-06-20 13:59:03 +00:00
configure 20000-05-21 H.J. Lu (hjl@gnu.org) 2000-05-21 16:57:14 +00:00
configure.in TI C54x target added. 2000-06-20 13:59:03 +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 2000-07-01 Koundinya K <kk@ddeorg.soft.net> 2000-07-02 01:14:54 +00:00
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 * symlink-tree: Check number of arguments. 2000-07-07 13:21:39 +00:00
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.