Binutils with MCST patches
Go to file
Joel Brobecker 496c0e1ba7 Allow disabling of gdbserver build (--enable-gdbserver=yes/no/auto).
This patch adds a new --enable-gdbserver=yes/no/auto command-line switch
in gdb/configure.  The primary purpose is to allow a user to disable the
build & install of gdbserver when not desired.  It also allows the user
to request gdbserver in which case the configure script will abort if
automatic building of gdbserver is not supported for that configuration.

The default keeps things as is: We automatically build gdbserver if
building for a native configuration and if gdbserver is supported for
that configuration.

gdb/ChangeLog:

        * configure.ac: Add support for --enable-gdbserver.
        * configure: Regenerate.

At AdaCore, this is mostly intended for ia64-linux, where we currently
do not want to distribute gdbserver.  This will be useful in the context
of I417-033, where we are now using "make install" to determine what
needs to be packaged inside the GNAT Pro package.
2010-09-22 16:15:01 +00:00
bfd 2010-09-22 Kai Tietz <kai.tietz@onevision.com> 2010-09-22 14:19:35 +00:00
binutils Fix date. 2010-09-18 00:43:39 +00:00
config Sync bootstrap-lto.mk and dfp.m4 with gcc. 2010-09-06 15:46:09 +00:00
cpu
elfcpp
etc
gas * gas/config/tc-arm.c (arm_cpus): Correct canonical names for Cortex CPUs. 2010-09-20 16:33:24 +00:00
gdb Allow disabling of gdbserver build (--enable-gdbserver=yes/no/auto). 2010-09-22 16:15:01 +00:00
gold * testsuite/Makefile.am (memory_test.o): New target. 2010-09-18 00:34:58 +00:00
gprof
include opcodes: blackfin: strip trailing whitespace 2010-09-21 06:04:21 +00:00
intl
ld 2010-09-22 Kai Tietz <kai.tietz@onevision.com> 2010-09-22 14:20:24 +00:00
libdecnumber merge from gcc 2010-09-10 23:17:28 +00:00
libiberty 2010-09-10 James Lyon <jameslyon0@googlemail.com> 2010-09-10 22:42:05 +00:00
opcodes 2010-09-17 Tejas Belagod <tejas.belagod@arm.com> 2010-09-17 10:13:41 +00:00
readline
sim
texinfo
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
README
README-maintainer-mode
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
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.