Binutils with MCST patches
Go to file
H.J. Lu eda17dc18d Add a test for linker ASSERT.
2011-01-10  H.J. Lu  <hongjiu.lu@intel.com>

	* ld-scripts/assert.exp: Run assert2.

	* ld-scripts/assert2.d: New.
	* ld-scripts/assert2.t: Likewise.
2011-01-10 14:37:40 +00:00
bfd bfd/ 2011-01-10 08:40:19 +00:00
binutils * po/da.po: Updated Danish translation. 2011-01-10 13:51:10 +00:00
config PR target/40125 2010-12-06 01:40:20 +00:00
cpu Fix build with -DDEBUG=7 2010-10-08 14:00:50 +00:00
elfcpp
etc PR other/46202: implement install-strip. 2010-11-20 19:37:58 +00:00
gas * config/tc-i386.c (x86_elf_abi): Only define for targets that use 2011-01-10 10:10:06 +00:00
gdb 2011-01-10 Phil Muldoon <pmuldoon@redhat.com> 2011-01-10 11:00:24 +00:00
gold * script-sections.cc (Sort_output_sections::operator()): Sort TLS 2011-01-04 21:46:06 +00:00
gprof * po/da.po: Updated Danish translation. 2011-01-10 13:51:10 +00:00
include bfd/ 2011-01-10 08:40:19 +00:00
intl merge from gcc 2010-09-27 21:01:18 +00:00
ld Add a test for linker ASSERT. 2011-01-10 14:37:40 +00:00
libdecnumber merge from gcc 2011-01-03 21:05:58 +00:00
libiberty merge from gcc 2011-01-03 21:05:58 +00:00
opcodes * po/da.po: Updated Danish translation. 2011-01-10 13:51:10 +00:00
readline
sim * testutils.inc: Correct comment syntax fallout from 2011-01-05 23:12:37 +00:00
texinfo
.cvsignore
.gitignore start a gitignore 2010-11-17 19:34:59 +00:00
ChangeLog Sync toplevel configure from GCC. 2011-01-02 16:40:07 +00:00
compile
config-ml.in Merge from gcc top-level. 2010-11-19 22:06:27 +00:00
config.guess
config.rpath
config.sub
configure Sync toplevel configure from GCC. 2011-01-02 16:40:07 +00:00
configure.ac Sync toplevel configure from GCC. 2011-01-02 16:40:07 +00:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS 2010-12-18 Jeff Johnston <jjohnstn@redhat.com> 2010-12-17 22:10:05 +00:00
COPYING.NEWLIB 2010-12-02 Jeff Johnston <jjohnstn@redhat.com> 2010-12-02 20:05:11 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def PR other/46020 2010-11-26 04:56:39 +00:00
Makefile.in PR other/46020 2010-11-26 04:56:39 +00:00
Makefile.tpl PR other/46020 2010-11-26 04:56:39 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release 2010-12-10 Tristan Gingold <gingold@adacore.com> 2010-12-10 09:10:49 +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.