GDB that can debug Mach-Os on Linux
Go to file
2006-04-25 15:41:16 +00:00
bfd daily update 2006-04-25 00:00:06 +00:00
binutils 2006-04-25 H.J. Lu <hongjiu.lu@intel.com> 2006-04-25 14:06:10 +00:00
config 2006-02-14 Paolo Bonzini <bonzini@gnu.org> 2006-02-14 09:22:15 +00:00
cpu * m32c.opc (parse_unsigned_bitbase): Take a new parameter which 2006-04-10 21:19:14 +00:00
etc 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
gas * config/xtensa-relax.c (XCHAL_HAVE_WIDE_BRANCHES): Provide default. 2006-04-25 15:41:16 +00:00
gdb Remove spurious entry 2006-04-25 00:18:25 +00:00
gprof bfd/ 2006-04-19 02:06:15 +00:00
include merge from gcc 2006-04-12 18:42:01 +00:00
intl 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
ld * ldlang.c (wild): Tidy default_common_section loop. 2006-04-19 02:10:43 +00:00
libiberty * floatformat.c (floatformat_to_double): Fix (biased) exponent=0 case. 2006-04-24 21:34:41 +00:00
mmalloc
opcodes * Makefile.am: Run "make dep-am". 2006-04-19 12:10:21 +00:00
readline touched all sources to ease import of readline-5.1 2006-04-20 20:13:20 +00:00
sim * Makefile.in (tmp-ld-decode): Fix dependencies. 2006-04-23 14:54:42 +00:00
texinfo
.cvsignore
ChangeLog * configure.in (m32c): Build libstdc++-v3. Pass flags to 2006-04-19 00:57:59 +00:00
compile
config-ml.in
config.guess Sync top level config files from the master config repository 2006-01-16 17:34:37 +00:00
config.sub Sync top level config files from the master config repository 2006-01-16 17:34:37 +00:00
configure * configure.in (m32c): Build libstdc++-v3. Pass flags to 2006-04-19 00:57:59 +00:00
configure.in * configure.in (m32c): Build libstdc++-v3. Pass flags to 2006-04-19 00:57:59 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh 2006-03-01 H.J. Lu <hongjiu.lu@intel.com> 2006-03-01 17:40:34 +00:00
MAINTAINERS Update information about: config-ml.in; makefile.vms; mkdep; setup.com; 2006-03-01 10:25:01 +00:00
Makefile.def 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
Makefile.in 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +00:00
Makefile.tpl 2006-04-06 Carlos O'Donell <carlos@codesourcery.com> 2006-04-06 21:49:35 +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.