Binutils with MCST patches
Go to file
Pedro Alves b4d1e8c700 * gnu-nat.c: Include "inf-child.h".
(gnu_mourn_inferior): Use the passed in target_ops
	instead of the gnu_ops global.
	(gnu_create_inferior): Inline `attach_to_child', use the passed in
	target_ops instead of the gnu_ops global.
	(gnu_can_run): Delete.
	(gnu_attach): Use the passed in target_ops instead of the gnu_ops
	global.
	(gnu_detach): Ditto.
	(gnu_prepare_to_store, gnu_open): Delete.
	(gnu_store_registers, gnu_fetch_registers): Delete declarations.
	(gnu_ops): Delete.
	(init_gnu_ops): Delete.
	(gnu_target): New.
	(_initialize_gnu_nat): Don't call init_gnu_ops or add_target here.
	* gnu-nat.h (gnu_target): Declare.
	* i386gnu-nat.c (gnu_fetch_registers, gnu_store_registers): Make
	static.
	(_initialize_i386gnu_nat): New.
2009-07-20 15:18:24 +00:00
bfd daily update 2009-07-20 00:00:07 +00:00
binutils 2009-07-20 H.J. Lu <hongjiu.lu@intel.com> 2009-07-20 13:40:48 +00:00
config PR other/40784 2009-07-17 15:11:33 +00:00
cpu * cpu/simplify.inc (*): One line doc strings don't need \n. 2009-07-16 17:53:25 +00:00
elfcpp
etc
gas 2009-07-17 H.J. Lu <hongjiu.lu@intel.com> 2009-07-17 17:54:51 +00:00
gdb * gnu-nat.c: Include "inf-child.h". 2009-07-20 15:18:24 +00:00
gold PR 10400 2009-07-17 01:07:33 +00:00
gprof
include merge from gcc 2009-07-17 20:20:45 +00:00
intl
ld * ld-mips-elf/pic-and-nonpic-3b.dd: Updated to use new PLT 2009-07-17 13:36:16 +00:00
libdecnumber
libiberty merge from gcc 2009-07-17 20:20:45 +00:00
opcodes PR 10288 2009-07-20 12:11:18 +00:00
readline
sim * common/Make-common.in (CPU_DIR): Define. 2009-07-12 16:59:34 +00:00
texinfo
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog 2009-07-02 Tristan Gingold <gingold@adacore.com> 2009-07-02 08:24:01 +00:00
MAINTAINERS
Makefile.def * Makefile.def (host_modules): Add cgen. 2009-06-26 17:19:07 +00:00
Makefile.in * Makefile.def (host_modules): Add cgen. 2009-06-26 17:19:07 +00:00
Makefile.tpl
README
README-maintainer-mode
compile
config-ml.in
config.guess
config.rpath
config.sub
configure 2009-07-02 Tristan Gingold <gingold@adacore.com> 2009-07-02 08:24:01 +00:00
configure.ac 2009-07-02 Tristan Gingold <gingold@adacore.com> 2009-07-02 08:24:01 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
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.