Go to file
2001-06-14 00:00:02 +00:00
bfd Only pad the tesxt section if the data section is going to follow it. 2001-06-13 07:58:05 +00:00
binutils * NEWS: Fix a typo. Mention hppa64-elf. Add binutils-2.11 marker. 2001-06-09 02:15:49 +00:00
config
etc
gas Stop sh-coff port from trying to call dwarf2 debug functions 2001-06-13 16:46:05 +00:00
gdb *** empty log message *** 2001-06-14 00:00:02 +00:00
gprof Rebuild after recent change to gprof.texi 2001-06-13 11:26:05 +00:00
include
intl
ld * config/default.exp (AS, GASP, OBJDUMP, NM, NMFLAGS, OBJCOPY, 2001-06-13 03:08:21 +00:00
libiberty merge from gcc 2001-06-12 13:16:43 +00:00
mmalloc
opcodes Add lgh instruction. 2001-06-12 11:50:53 +00:00
readline
sim
texinfo
.cvsignore
ChangeLog Handle GDB's gdb/version.in. 2001-06-13 19:00:22 +00:00
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
COPYING.NEWLIB
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in Handle GDB's gdb/version.in. 2001-06-13 19:00:22 +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
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.