Binutils with MCST patches
Go to file
Andrew Cagney 93021b7d08 * Makefile.in (remote_sim_h): Replace remote-sim_h.
(remote-sim.o): Update dependencies.
(d10v-tdep.o): Specify dependencies.
(sim_d10v_h): Define.
2002-05-14 22:19:49 +00:00
bfd daily update 2002-05-14 00:00:05 +00:00
binutils Add Joasn Thorpe as VAX maintainer 2002-05-09 12:43:46 +00:00
config * mh-apollo68: remove unused HDEFINES setting. 2002-05-13 21:14:19 +00:00
etc * fdl.texi: New file. 2002-02-28 03:34:36 +00:00
gas Remove redundant call to listing_prev_line 2002-05-14 20:40:30 +00:00
gdb * Makefile.in (remote_sim_h): Replace remote-sim_h. 2002-05-14 22:19:49 +00:00
gprof Do not attempt to create a .gmo file if the sources are read-only. 2002-05-02 08:15:00 +00:00
include 2002-05-10 Elena Zannoni <ezannoni@redhat.com> 2002-05-10 22:53:56 +00:00
intl
ld XCOFF64 fixes. For setting arch/mach and for R_BR relocations. 2002-05-10 21:20:16 +00:00
libiberty merge from gcc 2002-05-13 20:01:19 +00:00
mmalloc From 2002-03-05 Scott Pakin <pakin@uiuc.edu> 2002-04-07 17:58:57 +00:00
opcodes * configure.in (shle-*-*elf*): Include sh64 support. 2002-05-13 15:39:44 +00:00
readline Rename local ChangeLog and ChangeLog.Cygnus files to ChangeLog.gdb. 2002-02-24 20:52:49 +00:00
sim Uses sim callback interface for system calls in RedBoot SWI support. 2002-05-09 10:29:08 +00:00
texinfo * standards.texi: Import February 14, 2002 version. 2002-02-27 02:13:36 +00:00
.cvsignore
ChangeLog * configure.in: simplify makefile fragment collection. 2002-05-13 21:19:04 +00:00
config-ml.in
config.guess * config.guess: Updated to 2002-04-26's version. 2002-04-30 17:40:45 +00:00
config.if
config.sub * config.guess: Updated to 2002-04-26's version. 2002-04-30 17:40:45 +00:00
configure * configure: move some logic to configure.in 2002-05-13 20:55:25 +00:00
configure.in * configure.in: simplify makefile fragment collection. 2002-05-13 21:19:04 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2002-05-07 Jeff Johnston <jjohnstn@redhat.com> 2002-05-07 17:52:36 +00:00
COPYING.NEWLIB
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh * ltmain.sh (relink_command): Fix typo in previous change. 2002-03-16 14:43:09 +00:00
MAINTAINERS * MAINTAINERS: Update dejagnu/ 2002-04-07 19:17:07 +00:00
Makefile.in Honour DESTDIR 2002-05-07 17:22:20 +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
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.