Binutils with MCST patches
Go to file
Bob Wilson a7284bf13b * config/tc-xtensa.c (xtensa_sanity_check): Check for RELAX_IMMED
as the first slot_subtype, not the frag subtype.
2006-11-27 23:58:39 +00:00
bfd daily update 2006-11-27 23:00:08 +00:00
binutils 2006-10-30 Paul Brook <paul@codesourcery.com> 2006-10-31 20:21:57 +00:00
config * tls.m4 (GCC_CHECK_TLS): Fall back to a link test. 2006-11-14 03:32:36 +00:00
cpu
elfcpp Snapshot. Includes first cut at output relocation sections. 2006-11-16 00:38:25 +00:00
etc
gas * config/tc-xtensa.c (xtensa_sanity_check): Check for RELAX_IMMED 2006-11-27 23:58:39 +00:00
gdb * gdb.base/ending-run.exp: Flatten expect script stepping out of 2006-11-27 15:09:54 +00:00
gold Snapshot. Includes first cut at output relocation sections. 2006-11-16 00:38:25 +00:00
gprof Updated Malay translation 2006-11-27 14:11:10 +00:00
include Remove entries checked in by accident. 2006-11-27 22:05:26 +00:00
intl merge from gcc 2006-09-27 15:03:38 +00:00
ld bfd/ 2006-11-27 20:14:53 +00:00
libiberty merge from gcc 2006-11-08 19:09:26 +00:00
opcodes opcodes/ 2006-11-22 17:45:57 +00:00
readline 2006-11-13 Denis Pilat <denis.pilat@st.com> 2006-11-13 09:33:30 +00:00
sim * basic.exp: Fix spelling in comment. Use canonical form of target 2006-11-08 12:00:11 +00:00
texinfo
.cvsignore
ChangeLog 2006-11-16 Paolo Bonzini <bonzini@gnu.org> 2006-11-17 10:35:45 +00:00
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2006-09-26 05:22:50 +00:00
config.rpath
config.sub * config.sub, config.guess: Update from upstream sources. 2006-09-26 05:22:50 +00:00
configure * Makefile.tpl (clean-stage*): Sync with GCC (clean). 2006-11-14 23:26:39 +00:00
configure.in * Makefile.tpl (clean-stage*): Sync with GCC (clean). 2006-11-14 23:26:39 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2006-10-27 Jeff Johnston <jjohnstn@redhat.com> 2006-10-27 23:00:35 +00:00
COPYING.NEWLIB 2006-10-27 Jeff Johnston <jjohnstn@redhat.com> 2006-10-27 22:57:03 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.def 2006-10-17 Brooks Moses <bmoses@stanford.edu> 2006-10-17 04:23:49 +00:00
Makefile.in 2006-11-16 Paolo Bonzini <bonzini@gnu.org> 2006-11-17 10:35:45 +00:00
Makefile.tpl 2006-11-16 Paolo Bonzini <bonzini@gnu.org> 2006-11-17 10:35:45 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
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.