Binutils with MCST patches
Go to file
2012-09-06 20:14:13 +00:00
bfd daily update 2012-09-06 00:00:05 +00:00
binutils * doc/binutils.texi (nm): Alpha-sort the option descriptions. 2012-09-06 15:41:30 +00:00
config Sync toplevel files with GCC tree 2012-08-26 14:34:40 +00:00
cpu cpu/ 2012-02-27 06:57:57 +00:00
elfcpp elfcpp/ 2012-08-14 02:22:32 +00:00
etc
gas 2012-09-06 Andreas Krebbel <Andreas.Krebbel@de.ibm.com> 2012-09-06 08:23:25 +00:00
gdb * python/py-newobjfileevent.c (create_new_objfile_event_object): 2012-09-06 20:14:13 +00:00
gold Add .got.plt output section statement 2012-09-06 04:46:18 +00:00
gprof Updated Vietnamese translation. 2012-08-09 14:46:44 +00:00
include Add Intel Itanium Series 9500 support 2012-09-04 13:52:06 +00:00
intl
ld Don't optimize relocation against _DYNAMIC 2012-09-01 02:50:14 +00:00
libdecnumber config/: 2011-12-20 17:01:30 +00:00
libiberty Replace malloc with xmalloc 2012-08-29 01:02:41 +00:00
opcodes Add Intel Itanium Series 9500 support 2012-09-04 13:52:06 +00:00
readline * signals.c (_rl_block_sigwinch, _rl_release_sigwinch): Add 2012-02-24 17:14:43 +00:00
sim 2012-09-03 Joel Sherrill <joel.sherrill@oarcorp.com> 2012-09-04 21:40:46 +00:00
texinfo
.cvsignore
.gitignore
ChangeLog Don't set HOST_LIB_PATH_bfd/HOST_LIB_PATH_opcodes 2012-08-26 14:41:28 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub Update config.sub to 2012-04-18 version. 2012-04-25 15:53:25 +00:00
configure Sync toplevel files with GCC tree 2012-08-26 14:34:40 +00:00
configure.ac Sync toplevel files with GCC tree 2012-08-26 14:34:40 +00:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS 2012-03-09 Jeff Johnston <jjohnstn@redhat.com> 2012-03-09 20:31:34 +00:00
COPYING.NEWLIB 2012-03-09 Jeff Johnston <jjohnstn@redhat.com> 2012-03-09 20:31:34 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4 Sync libtool.m4 with GCC tree 2012-08-26 14:09:08 +00:00
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS MAINTAINERS: clarify policy with config/ (and other top level files) 2012-05-12 03:10:17 +00:00
Makefile.def Don't set HOST_LIB_PATH_bfd/HOST_LIB_PATH_opcodes 2012-08-26 14:41:28 +00:00
Makefile.in Don't set HOST_LIB_PATH_bfd/HOST_LIB_PATH_opcodes 2012-08-26 14:41:28 +00:00
Makefile.tpl Sync toplevel files with GCC tree 2012-08-26 14:34:40 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release Include the <root>/cpu/ dir in GDB releases 2011-08-19 15:48:36 +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.