Binutils with MCST patches
Go to file
Nick Clifton ddbb8a31d5 * lexsup.c: Rename --add-needed to --copy-dt-needed-entries.
* ldlang.h (struct lang_input_statement_struct): Rename add_needed
        to add_DT_NEEDED_for_dynamic.  Rename as_needed to
        add_DT_NEEDED_for_regular.
        * ldlang.c: Likewise.
        * ldlang.h: Likewise.
        * ldlang.c: Use the new variable names.
        * ldgram.y: Likewise.
        * emultempl/elf32.em: Likewise.
        * ld.texinfo: Document the renamed option.  Also mention its
        affect on the resolution of dynamic symbols.
        * NEWS: Mention the changed option name.
2009-11-05 15:35:50 +00:00
bfd * elflink.c (elf_link_add_object_symbols): Improve error 2009-11-05 15:34:18 +00:00
binutils 2009-11-05 Kai Tietz <kai.tietz@onevision.com> 2009-11-05 09:49:07 +00:00
config
cpu cpu/ 2009-10-24 00:17:08 +00:00
elfcpp * elfcpp.h: Remove trailing commas from enum definitions. 2009-11-03 15:12:03 +00:00
etc
gas * gas/i386/i386.exp (space1): Move test inside check for x86 2009-11-05 11:02:16 +00:00
gdb *** empty log message *** 2009-11-05 00:00:04 +00:00
gold PR 10880 2009-11-05 06:24:39 +00:00
gprof
include [opcodes] 2009-11-05 00:38:45 +00:00
intl 2009-10-15 Jim Blandy <jimb@red-bean.com> 2009-10-15 09:41:35 +00:00
ld * lexsup.c: Rename --add-needed to --copy-dt-needed-entries. 2009-11-05 15:35:50 +00:00
libdecnumber
libiberty merge from gcc 2009-10-09 04:49:52 +00:00
opcodes [opcodes] 2009-11-05 02:31:40 +00:00
readline
sim * arch.c: Regenerate. 2009-11-04 05:42:21 +00:00
texinfo
.cvsignore
ChangeLog Fix toplevel 'config.status --recheck' for --enable-lto. 2009-10-13 03:32:18 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Fix toplevel 'config.status --recheck' for --enable-lto. 2009-10-13 03:32:18 +00:00
configure.ac Fix toplevel 'config.status --recheck' for --enable-lto. 2009-10-13 03:32:18 +00:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def Sync with gcc repository. 2009-10-07 05:57:49 +00:00
Makefile.in Sync with gcc repository. 2009-10-07 05:57:49 +00:00
Makefile.tpl Sync with gcc repository. 2009-10-07 05:57:49 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
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.