Go to file
2006-06-05 00:00:04 +00:00
bfd daily update 2006-06-05 00:00:04 +00:00
binutils binutils: 2006-06-02 23:08:12 +00:00
config Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
cpu * iq2000.cpu: Fix include paths for iq2000m.cpu and iq10.cpu. 2006-05-22 09:07:20 +00:00
etc * texi2pod.pl: Correct handling of absolute @include. 2006-05-31 15:47:48 +00:00
gas binutils: 2006-06-02 23:08:12 +00:00
gdb *** empty log message *** 2006-06-04 00:00:03 +00:00
gprof Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
include merge from gcc 2006-06-01 14:57:50 +00:00
intl merge from gcc 2006-05-24 02:02:46 +00:00
ld * emultempl/elf32.em (global_found): Make it a pointer. 2006-06-03 02:45:26 +00:00
libiberty merge from gcc 2006-06-02 15:37:03 +00:00
opcodes Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
readline Readline 5.1 import for HEAD. 2006-05-05 18:26:14 +00:00
sim Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
texinfo
.cvsignore
ChangeLog Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2006-05-14 00:51:19 +00:00
config.rpath 2006-05-22 Steve Ellcey <sje@cup.hp.com> 2006-05-22 15:30:13 +00:00
config.sub * config.sub, config.guess: Update from upstream sources. 2006-05-14 00:51:19 +00:00
configure Enable gprof for cross builds. 2006-05-24 13:55:10 +00:00
configure.in Enable gprof for cross builds. 2006-05-24 13:55:10 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
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 2006-05-22 Steve Ellcey <sje@cup.hp.com> 2006-05-22 15:30:13 +00:00
Makefile.def Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
Makefile.in Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
Makefile.tpl 2006-05-25 Paolo Bonzini <bonzini@gnu.org> 2006-05-25 08:01:03 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release Configury changes: update src repository (binutils, gdb, and rda) to use 2006-05-31 15:14:46 +00:00
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.