Binutils with MCST patches
Go to file
Paul Brook 336becc779 2007-03-01 Paul Brook <paul@codesourcery.com>
* MAINTAINERS: Update my entry.
2007-03-01 16:06:28 +00:00
bfd bfd: 2007-03-01 15:48:36 +00:00
binutils 2007-03-01 Paul Brook <paul@codesourcery.com> 2007-03-01 16:06:28 +00:00
config * mt-spu (all-ld): Depend on all-binutils. 2007-02-27 09:02:43 +00:00
cpu
elfcpp Generate version information. 2006-12-06 00:02:36 +00:00
etc 2006-12-19 Paolo Bonzini <bonzini@gnu.org> 2006-12-19 14:01:25 +00:00
gas bfd: 2007-03-01 15:48:36 +00:00
gdb *** empty log message *** 2007-03-01 00:00:33 +00:00
gold Don't emit symbols seen only in dynamic object, don't read duplicate 2006-12-06 06:28:56 +00:00
gprof bfd: 2007-03-01 15:48:36 +00:00
include * spu-insns.h: Add soma double-float insns. 2007-03-01 11:17:41 +00:00
intl merge from gcc 2006-09-27 15:03:38 +00:00
ld bfd: 2007-03-01 15:48:36 +00:00
libiberty PR other/16513 2007-03-01 15:32:57 +00:00
opcodes * s390-opc.c (INSTR_SS_L2RDRD): New. 2007-02-22 21:01:59 +00:00
readline 2006-11-13 Denis Pilat <denis.pilat@st.com> 2006-11-13 09:33:30 +00:00
sim * mips.igen (MFHI, MFLO, MTHI, MTLO): Restore support for mips32 2007-03-01 14:29:26 +00:00
texinfo
.cvsignore add autom4te.cache to .cvsignore 2007-02-13 15:25:58 +00:00
ChangeLog * mt-spu (all-ld): Depend on all-binutils. 2007-02-27 09:02:43 +00:00
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2006-12-11 04:12:46 +00:00
config.rpath
config.sub 2007-02-05 Dave Brolley <brolley@redhat.com> 2007-02-05 19:10:45 +00:00
configure * configure.ac: Adjust for loop syntax. 2007-02-19 17:24:25 +00:00
configure.ac * configure.ac: Adjust for loop syntax. 2007-02-19 17:24:25 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2007-02-08 Jeff Johnston <jjohnstn@redhat.com> 2007-02-08 21:32:33 +00:00
COPYING.NEWLIB 2007-02-08 Jeff Johnston <jjohnstn@redhat.com> 2007-02-08 21:32:33 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.def 2007-02-09 Paolo Bonzini <bonzini@gnu.org> 2007-02-09 19:24:42 +00:00
Makefile.in 2007-02-09 Paolo Bonzini <bonzini@gnu.org> 2007-02-09 19:24:42 +00:00
Makefile.tpl 2007-02-09 Paolo Bonzini <bonzini@gnu.org> 2007-02-09 19:24:42 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release * Makefile.tpl (build_alias, host_alias, target_alias): Use 2007-02-09 15:15:38 +00:00
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.