Binutils with MCST patches
Go to file
Alan Modra f9f32305f7 * elflink.h (elf_link_input_bfd): Complain about all relocs
against local syms from discarded sections.
	(elf_reloc_symbol_deleted_p): Don't try to swap in external syms.
2001-11-15 09:31:25 +00:00
bfd * elflink.h (elf_link_input_bfd): Complain about all relocs 2001-11-15 09:31:25 +00:00
binutils * binutils-all/readelf.exp: powerpc-*-eabi* is an ELF target. 2001-11-15 01:11:09 +00:00
config
etc
gas revert last change. 2001-11-15 09:16:46 +00:00
gdb * TODO (register_buffer): Delete. 2001-11-15 06:43:10 +00:00
gprof Add translations 2001-11-02 19:09:06 +00:00
include binutils/ChangeLog 2001-11-15 01:08:53 +00:00
intl
ld 2001-11-14 H.J. Lu <hjl@gnu.org> 2001-11-15 07:12:48 +00:00
libiberty merge from gcc 2001-11-13 03:54:15 +00:00
mmalloc
opcodes binutils/ChangeLog 2001-11-15 01:08:53 +00:00
readline Clone src/config.guess. Mention in MAINTAINERS. 2001-07-20 20:08:08 +00:00
sim when #size-cells is zero, don't expect a size. 2001-11-14 19:54:59 +00:00
texinfo
.cvsignore Add MMIX support 2001-10-30 15:20:14 +00:00
ChangeLog 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
config-ml.in
config.guess * config.sub, config.guess: Import latest from subversions. 2001-09-28 21:04:51 +00:00
config.if
config.sub * config.sub, config.guess: Import latest from subversions. 2001-09-28 21:04:51 +00:00
configure
configure.in * configure.in (--enable-languages): Be more permissive about 2001-11-09 02:21:21 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB 2001-11-12 Hans-Peter Nilsson <hp@bitrange.com> 2001-11-12 21:07:42 +00:00
djunpack.bat
gettext.m4 * gettext.m4: Test po/POTFILES.in exists before trying to read. 2001-10-03 01:46:25 +00:00
install-sh
libtool.m4
ltcf-c.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltcf-cxx.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltcf-gcj.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltconfig 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltmain.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
MAINTAINERS * MAINTAINERS: Clarify libiberty merge rules and procedures. 2001-07-26 14:20:05 +00:00
Makefile.in 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 05:49:24 +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.