Binutils with MCST patches
Go to file
2002-01-26 10:32:21 +00:00
bfd Copy only as much information as possible to avoid stack corruption. 2002-01-26 10:32:21 +00:00
binutils Add --totals option to size 2002-01-25 15:37:04 +00:00
config
etc
gas Updated French translation 2002-01-26 08:53:50 +00:00
gdb *** empty log message *** 2002-01-26 00:00:04 +00:00
gprof Updated French translation 2002-01-26 08:53:50 +00:00
include [ include/opcode/ChangeLog ] 2002-01-22 21:45:36 +00:00
intl comment typo fixes 2002-01-21 14:03:27 +00:00
ld Updated French translation 2002-01-26 08:53:50 +00:00
libiberty * configure.in (variable detection): Use arrays of unspecified 2002-01-22 22:32:35 +00:00
mmalloc
opcodes Updated French version 2002-01-26 08:52:51 +00:00
readline * rluser.texinfo (Sample Init File): Prevent overfull hboxes. 2002-01-20 11:27:37 +00:00
sim 2002-01-20 Ben Elliston <bje@redhat.com> 2002-01-20 04:09:23 +00:00
texinfo
.cvsignore
ChangeLog Import StrongARM and XScale target_configdirs from FSF GCC version. 2002-01-23 16:40:51 +00:00
config-ml.in
config.guess 2002-01-16 H.J. Lu (hjl@gnu.org) 2002-01-16 23:20:25 +00:00
config.if
config.sub 2002-01-16 H.J. Lu (hjl@gnu.org) 2002-01-16 23:20:25 +00:00
configure When build != host, create libiberty for the build machine. 2001-11-28 19:55:01 +00:00
configure.in Import StrongARM and XScale target_configdirs from FSF GCC version. 2002-01-23 16:40:51 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB 2002-01-07 Jeff Johnston <jjohnstn@redhat.com> 2002-01-07 19:44:59 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltcf-cxx.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltcf-gcj.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltconfig 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltmain.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
MAINTAINERS 2002-01-16 H.J. Lu (hjl@gnu.org) 2002-01-16 23:20:25 +00:00
Makefile.in When build != host, create libiberty for the build machine. 2001-11-28 19:55:01 +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
symlink-tree gcc adopts symlink-tree, refer more to libiberty. 2001-12-05 10:07:09 +00:00
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.