Binutils with MCST patches
Go to file
gdbadmin 6e29563e70 *** empty log message *** 2009-06-07 00:00:34 +00:00
bfd daily update 2009-06-07 00:00:08 +00:00
binutils * strings.c (main): Delay parsing of decimal digits. 2009-06-04 08:27:54 +00:00
config * plugins.m4: New. 2009-05-27 16:29:55 +00:00
cpu
elfcpp 2009-05-27 Doug Kwan <dougkwan@google.com> 2009-05-27 18:27:42 +00:00
etc bfd: 2009-02-03 15:54:05 +00:00
gas * dep-in.sed: Don't use \n in replacement part of s command. 2009-06-04 06:57:12 +00:00
gdb *** empty log message *** 2009-06-07 00:00:34 +00:00
gold 2009-06-05 Doug Kwan <dougkwan@google.com> 2009-06-05 21:32:57 +00:00
gprof * dep-in.sed: Don't use \n in replacement part of s command. 2009-06-04 06:57:56 +00:00
include Print moxie addresses nicely. 2009-06-06 13:02:21 +00:00
intl
ld bfd/ 2009-06-06 22:39:25 +00:00
libdecnumber merge from gcc 2009-06-01 19:40:44 +00:00
libiberty merge from gcc 2009-05-30 05:18:46 +00:00
opcodes Print moxie addresses nicely. 2009-06-06 13:02:21 +00:00
readline gdb: 2009-04-17 17:44:05 +00:00
sim Add ChangeLog 2009-05-18 13:27:12 +00:00
texinfo * texinfo/texinfo.tex: Update to version 2009-03-28.05. 2009-04-21 12:36:46 +00:00
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog * Makefile.tpl (all): Avoid a trailing backslash. 2009-06-03 05:40:47 +00:00
MAINTAINERS
Makefile.def ChangeLog: 2009-05-12 18:16:01 +00:00
Makefile.in * Makefile.tpl (all): Avoid a trailing backslash. 2009-06-03 05:40:47 +00:00
Makefile.tpl * Makefile.tpl (all): Avoid a trailing backslash. 2009-06-03 05:40:47 +00:00
README
README-maintainer-mode
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2009-06-02 23:00:59 +00:00
config.rpath
config.sub * config.sub, config.guess: Update from upstream sources. 2009-06-02 23:00:59 +00:00
configure 2009-05-28 Doug Kwan <dougkwan@google.com> 2009-05-29 00:15:12 +00:00
configure.ac 2009-05-28 Doug Kwan <dougkwan@google.com> 2009-05-29 00:15:12 +00:00
depcomp
djunpack.bat * djunpack.bat: Use ".." quoting in Sed command, for the sake of 2009-03-27 13:37:09 +00:00
install-sh
libtool.m4 Backport from git Libtool: 2009-03-01 18:57:19 +00:00
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com 2009-05-25 Tristan Gingold <gingold@adacore.com> 2009-05-25 13:31:05 +00:00
src-release
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.