Binutils with MCST patches
Go to file
Pierre Muller 621791b854 PR stabs/11479.
* stabsread.c (set_length_in_type_chain): New function.
	(read_struct_type): Call set_length_in_type_chain function.
	(read_enum_type): Idem.
2010-04-22 12:30:55 +00:00
bfd bfd/ 2010-04-22 01:51:01 +00:00
binutils Updated French translation. 2010-04-20 09:28:15 +00:00
config Sync from gcc mainline. 2010-02-15 10:37:55 +00:00
cpu * m32r.cpu (HASH-PREFIX): Delete. 2010-02-12 04:38:21 +00:00
elfcpp include: 2010-03-05 21:04:59 +00:00
etc
gas Remove i386_is_register. 2010-04-22 03:10:48 +00:00
gdb PR stabs/11479. 2010-04-22 12:30:55 +00:00
gold 2010-04-15 Andrew Haley <aph@redhat.com> 2010-04-21 16:32:31 +00:00
gprof * configure: Regenerate. 2010-04-07 07:20:51 +00:00
include gas/testsuite: 2010-04-21 18:56:45 +00:00
intl merge from gcc 2010-04-05 18:02:22 +00:00
ld bfd/ 2010-04-22 01:51:01 +00:00
libdecnumber merge from gcc 2010-04-05 18:02:22 +00:00
libiberty merge from gcc 2010-04-07 21:16:24 +00:00
opcodes Remove extra breack. 2010-04-16 21:37:08 +00:00
readline
sim sim: profile: implement --profile-file backend 2010-04-22 02:18:32 +00:00
texinfo
.cvsignore
ChangeLog 2010-04-14 Tristan Gingold <gingold@adacore.com> 2010-04-14 09:28:48 +00:00
compile
config-ml.in
config.guess * config.sub: Update to version 2010-03-22. 2010-03-23 14:27:19 +00:00
config.rpath
config.sub * config.sub: Update to version 2010-03-22. 2010-03-23 14:27:19 +00:00
configure 2010-04-14 Tristan Gingold <gingold@adacore.com> 2010-04-14 09:28:48 +00:00
configure.ac 2010-04-14 Tristan Gingold <gingold@adacore.com> 2010-04-14 09:28:48 +00:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
lt~obsolete.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltgcc.m4
ltmain.sh Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltoptions.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltsugar.m4
ltversion.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
MAINTAINERS
Makefile.def Merge from gcc: 2010-03-14 16:00:37 +00:00
Makefile.in Merge from gcc: 2010-03-14 16:00:37 +00:00
Makefile.tpl * Makefile.tpl: Use "-exec rm {}" rather than "-delete" to delete 2010-02-17 11:02:54 +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.