Binutils with MCST patches
Go to file
Jim Blandy e7c9ff0185 2004-02-17 Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Committed by Jim Blandy  <jimb@redhat.com>.

	* gdb.base/float.exp: Support s390*-*-* targets.
2004-02-18 04:13:43 +00:00
bfd daily update 2004-02-17 23:00:05 +00:00
binutils Use bfd_cache_close, instead of accessing bfd->iostream directly. 2004-02-15 02:24:53 +00:00
config * gettext.m4: Quote names of macros to be defined by AC_DEFUN 2004-01-14 13:41:37 +00:00
contrib
cpu cpu/ 2004-01-14 10:05:00 +00:00
etc
gas 2004-02-13 Hannes Reinecke <hare@suse.de> 2004-02-13 16:12:47 +00:00
gdb 2004-02-17 Ulrich Weigand <Ulrich.Weigand@de.ibm.com> 2004-02-18 04:13:43 +00:00
gprof Split ChangeLog files. 2004-01-02 11:16:21 +00:00
include Add support for relaxing the 32bit ldc/stc instructions. 2004-02-09 12:15:57 +00:00
intl
ld bfd/ 2004-02-17 10:19:24 +00:00
libiberty merge from gcc 2004-02-17 02:11:39 +00:00
mmalloc
opcodes * m32r-dis.c: Regenerate. 2004-02-13 03:21:49 +00:00
readline 2004-01-27 Elena Zannoni <ezannoni@redhat.com> 2004-01-27 22:25:15 +00:00
sim 2004-02-02 Michael Snyder <msnyder@redhat.com> 2004-02-13 00:01:19 +00:00
texinfo
.cvsignore
ChangeLog * configure.in (powerpc-*-aix*): Add target-libada to noconfigdirs. 2004-02-11 17:52:06 +00:00
config-ml.in * config-ml.in: Don't mess with the cache file. 2004-01-05 00:42:16 +00:00
config.guess
config.if
config.sub
configure * configure.in (powerpc-*-aix*): Add target-libada to noconfigdirs. 2004-02-11 17:52:06 +00:00
configure.in * configure.in (powerpc-*-aix*): Add target-libada to noconfigdirs. 2004-02-11 17:52:06 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB 2004-02-02 Jeff Johnston <jjohnstn@redhat.com> 2004-02-03 00:05:49 +00:00
djunpack.bat
gettext.m4 * gettext.m4: Quote names of macros to be defined by AC_DEFUN 2004-01-14 13:41:37 +00:00
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.def 2004-02-10 Arnaud Charlet <charlet@act-europe.fr>, 2004-02-10 17:57:02 +00:00
Makefile.in 2004-02-10 Arnaud Charlet <charlet@act-europe.fr>, 2004-02-10 17:57:02 +00:00
Makefile.tpl * Makefile.def (target_modules) [libtermcap, libiberty, zlib]: Stage. 2004-01-14 21:13:34 +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
src-release 2004-01-15 Andrew Cagney <cagney@redhat.com> 2004-01-15 23:24:29 +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.