Binutils with MCST patches
Go to file
Alan Modra 40cf2291a7 * scripttempl/elf.sc: Ensure that crtbegin and crtend entries will
not match random object files in a path containing "crtbegin" or
	"crtend" as part of a directory name.
	* scripttempl/armbpabi.sc: Likewise.
	* scripttempl/crisaout.sc: Likewise.
	* scripttempl/elf32crx.sc: Likewise.
	* scripttempl/elf32sh-symbian.sc: Likewise.
	* scripttempl/elf_chaos.sc: Likewise.
	* scripttempl/elfd10v.sc: Likewise.
	* scripttempl/elfd30v.sc: Likewise.
	* scripttempl/elfxtensa.sc: Likewise.
	* scripttempl/iq2000.sc: Likewise.
	* scripttempl/mmo.sc: Likewise.
	* scripttempl/xstormy16.sc: Likewise.
2006-08-28 01:52:56 +00:00
bfd daily update 2006-08-28 00:00:02 +00:00
binutils bfd 2006-08-21 08:12:46 +00:00
config Sync from GCC 2006-07-25 08:39:57 +00:00
cpu
elfcpp Another snapshot of the current state of the sources. Gets to the 2006-08-18 22:29:20 +00:00
etc
gas * config/tc-xtensa.c (xtensa_mark_literal_pool_location): Do not check 2006-08-25 19:59:31 +00:00
gdb *** empty log message *** 2006-08-28 00:00:03 +00:00
gold Another snapshot of the current state of the sources. Gets to the 2006-08-18 22:29:20 +00:00
gprof Fix spelling typos 2006-07-24 13:49:50 +00:00
include * ldmain.c (main): Initialise print_gc_sections field of link_info structure. 2006-08-04 14:53:26 +00:00
intl
ld * scripttempl/elf.sc: Ensure that crtbegin and crtend entries will 2006-08-28 01:52:56 +00:00
libiberty merge from gcc 2006-08-28 00:56:25 +00:00
opcodes 2006-08-23 H.J. Lu <hongjiu.lu@intel.com> 2006-08-23 14:48:49 +00:00
readline
sim Add myself as mips maintainer. 2006-08-25 18:06:21 +00:00
texinfo
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
ChangeLog [ ChangeLog ] 2006-08-15 18:23:11 +00:00
MAINTAINERS
Makefile.def * Makefile.def: Add dependencies for configure-opcodes 2006-07-17 17:04:21 +00:00
Makefile.in 2006-07-19 Paolo Bonzini <bonzini@gnu.org> 2006-07-19 17:06:06 +00:00
Makefile.tpl 2006-07-19 Paolo Bonzini <bonzini@gnu.org> 2006-07-19 17:06:06 +00:00
README
README-maintainer-mode
compile
config-ml.in
config.guess
config.rpath
config.sub [ ChangeLog ] 2006-08-15 18:23:11 +00:00
configure Sync from GCC 2006-07-25 08:39:57 +00:00
configure.in Sync from GCC 2006-07-25 08:39:57 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com
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.