GDB that can debug Mach-Os on Linux
Go to file
Daniel Jacobowitz e017c81f1f 2002-01-13 Daniel Jacobowitz <drow@mvista.com>
* gdb.c++/demangle.exp: Accept slightly dubious v2 demangler result
        for slightly dubious v2 mangled string.
2002-01-13 23:54:10 +00:00
bfd daily update 2002-01-13 23:00:04 +00:00
binutils include/elf: 2002-01-09 18:59:11 +00:00
config
etc
gas * tc-arm.c ((do_ldst): Fix handling an immediate expression pseudo 2002-01-11 18:00:17 +00:00
gdb 2002-01-13 Daniel Jacobowitz <drow@mvista.com> 2002-01-13 23:54:10 +00:00
gprof Add spanish translation files 2002-01-07 17:37:59 +00:00
include include/elf: 2002-01-09 18:59:11 +00:00
intl * Import GNU gettext 0.10.35. 2001-11-29 03:38:59 +00:00
ld * emulparams/avr1200.sh (DATA_START): Define as 0x60. 2002-01-12 20:22:19 +00:00
libiberty merge from gcc 2002-01-03 00:25:57 +00:00
mmalloc
opcodes [cgen/ChangeLog] 2002-01-11 07:24:59 +00:00
readline
sim * Makefile.in (tmp-igen): Pass -I $(srcdir) to igen. 2002-01-12 10:21:12 +00:00
texinfo
.cvsignore
ChangeLog Add ia64-hpux target. LD and GDB are not currently supported. 2002-01-11 09:29:18 +00:00
config-ml.in
config.guess * config.sub: Import latest version. 2001-12-18 07:20:15 +00:00
config.if
config.sub * config.sub: Import latest version. 2001-12-18 07:20:15 +00:00
configure When build != host, create libiberty for the build machine. 2001-11-28 19:55:01 +00:00
configure.in Add ia64-hpux target. LD and GDB are not currently supported. 2002-01-11 09:29:18 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB 2002-01-07 Jeff Johnston <jjohnstn@redhat.com> 2002-01-07 19:44:59 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltcf-cxx.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltcf-gcj.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltconfig 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
ltmain.sh 2001-11-13 Jeff Holcomb <jeffh@redhat.com> 2001-11-14 06:24:41 +00:00
MAINTAINERS * MAINTAINERS: Update URL for config.* scripts. 2002-01-02 21:44:52 +00:00
Makefile.in When build != host, create libiberty for the build machine. 2001-11-28 19:55:01 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode
setup.com
symlink-tree gcc adopts symlink-tree, refer more to libiberty. 2001-12-05 10:07:09 +00:00
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.