Binutils with MCST patches
Go to file
Nick Clifton ec68b08387 * po/ru.po: New Russian translation.
* configure.in (ALL_LINGUAS): Add ru.
        * configure: Regenerate.
2009-06-15 08:52:20 +00:00
bfd * po/ru.po: New Russian translation. 2009-06-15 08:52:20 +00:00
binutils * corefile.c (num_of_syms_in): New function - computes the number 2009-06-12 15:33:30 +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
gas bfd/ 2009-06-14 01:39:46 +00:00
gdb *** empty log message *** 2009-06-15 00:00:33 +00:00
gold 2009-06-05 Doug Kwan <dougkwan@google.com> 2009-06-05 21:32:57 +00:00
gprof * corefile.c (core_create_syms_from): Use BFD_VMA_FMT when 2009-06-15 08:48:49 +00:00
include Add PC-relative branch instructions to moxie port. 2009-06-11 11:27:58 +00:00
intl
ld bfd/ 2009-06-14 22:13:30 +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 * cgen.sh: Handle multiple simultaneous runs for parallel makes. 2009-06-14 16:36:56 +00:00
readline gdb: 2009-04-17 17:44:05 +00:00
sim Add PC-relative branch support to moxie sim. 2009-06-11 11:36:14 +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
install-sh
libtool.m4
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.