Binutils with MCST patches
Go to file
Nick Clifton 3b6ed320ba Do not expect the compilation unit tag to be unit 1 2000-06-19 01:05:41 +00:00
bfd 2000-06-18 Ulf Carlsson <ulfc@engr.sgi.com> 2000-06-19 00:18:58 +00:00
binutils Do not expect the compilation unit tag to be unit 1 2000-06-19 01:05:41 +00:00
config Add IBM 370 support. 2000-02-23 13:52:23 +00:00
etc
gas Use bfd_octets_per_byte instead of OCTETS_PER_BYTE 2000-06-19 01:01:04 +00:00
gdb Re-do multi-line tests using gdb_expect_list(). 2000-06-18 03:45:35 +00:00
gprof 2000-06-13 H.J. Lu <hjl@gnu.org> 2000-06-13 19:11:54 +00:00
include Changed values of MODSYNC and CRCCON as suggest by Russ Magee <rmagee@home.com> 2000-06-18 23:29:02 +00:00
intl
ld Correctly set SEC_READONLY for .text section. 2000-06-15 09:09:13 +00:00
libiberty Synced with libiberty in the gcc repository. 2000-06-15 20:56:25 +00:00
mmalloc * mmalloc/Makefile.in (install-info): Make sure $(infodir) exists. 2000-05-17 11:45:56 +00:00
opcodes * disassemble.c (disassembler): Refer to the PowerPC 620 using 2000-06-16 20:46:47 +00:00
readline Remove generated file. 2000-04-19 01:59:39 +00:00
sim Add strongarm tests 2000-06-19 00:56:04 +00:00
texinfo Import texinfo.tex from texinfo-4.0. 2000-05-31 10:18:58 +00:00
.cvsignore
COPYING
COPYING.LIB
ChangeLog new file - notes about using --enable-maintainer-mode 2000-06-07 21:31:48 +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
README
README-maintainer-mode 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
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 * ltconfig, ltmain.sh: Update to libtool 1.3.4. 2000-02-27 16:46:19 +00:00
ltmain.sh 2000-05-13 Alexandre Oliva <oliva@lsd.ic.unicamp.br> 2000-05-13 21:19:50 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-README
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
setup.com
symlink-tree
ylwrap

README

		   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.