Binutils with MCST patches
Go to file
Ben Elliston 13f178c0af * gprof.c (main): Clean up some more. 2004-05-26 05:56:22 +00:00
bfd daily update 2004-05-26 00:00:07 +00:00
binutils binutils ChangeLog: 2004-05-17 16:40:01 +00:00
config 2004-05-23 Paolo Bonzini <bonzini@gnu.org> 2004-05-24 10:45:14 +00:00
contrib
cpu Make 'insn' argument of iq2000_cgen_insn_supported be const. 2004-05-15 13:10:30 +00:00
etc
gas Reorganise m68k instruction decoding and improve handling of MAC/EMAC 2004-05-24 14:33:22 +00:00
gdb 2004-05-25 Randolph Chung <tausq@debian.org> 2004-05-26 05:51:39 +00:00
gprof * gprof.c (main): Clean up some more. 2004-05-26 05:56:22 +00:00
include Reorganise m68k instruction decoding and improve handling of MAC/EMAC 2004-05-24 14:33:22 +00:00
intl
ld bfd/ 2004-05-25 06:33:51 +00:00
libiberty merge from gcc 2004-05-25 20:03:59 +00:00
mmalloc
opcodes Reorganise m68k instruction decoding and improve handling of MAC/EMAC 2004-05-24 14:33:22 +00:00
readline Index: ChangeLog 2004-02-19 14:55:26 +00:00
sim * dv-glue.c (hw_glue_finish): Cast result of sizeof to long before 2004-05-18 21:20:07 +00:00
texinfo 2004-02-23 Andrew Cagney <cagney@redhat.com> 2004-02-23 19:37:48 +00:00
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB 2004-02-02 Jeff Johnston <jjohnstn@redhat.com> 2004-02-03 00:05:49 +00:00
ChangeLog * Makefile.tpl (BUILD_EXPORTS, HOST_EXPORTS, GCC_HOST_EXPORTS) 2004-05-25 20:36:50 +00:00
MAINTAINERS Typo fix: s/otheriwse/otherwise/ 2004-04-14 01:26:14 +00:00
Makefile.def 2005-05-24 Paolo Bonzini <bonzini@gnu.org> 2004-05-24 11:08:48 +00:00
Makefile.in * Makefile.tpl (BUILD_EXPORTS, HOST_EXPORTS, GCC_HOST_EXPORTS) 2004-05-25 20:36:50 +00:00
Makefile.tpl * Makefile.tpl (BUILD_EXPORTS, HOST_EXPORTS, GCC_HOST_EXPORTS) 2004-05-25 20:36:50 +00:00
README
README-maintainer-mode
config-ml.in
config.guess Index: ChangeLog 2004-02-19 14:55:26 +00:00
config.if
config.sub Index: ChangeLog 2004-02-19 14:55:26 +00:00
configure 2005-05-24 Paolo Bonzini <bonzini@gnu.org> 2004-05-24 11:08:48 +00:00
configure.in 2005-05-24 Paolo Bonzini <bonzini@gnu.org> 2004-05-24 11:08:48 +00:00
depcomp merge from gcc 2004-05-13 18:14:28 +00:00
djunpack.bat
gettext.m4
install-sh PR bootstrap/11932 2004-02-20 02:05:00 +00:00
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
makefile.vms
missing
mkdep
mkinstalldirs PR bootstrap/11932 2004-02-20 02:05:00 +00:00
move-if-change
setup.com
src-release Remove MPW support, no longer used. 2004-03-25 17:51:10 +00:00
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.