Go to file
Mike Frysinger 9d13c14365 fix my name
2006-08-06 05:24:32 +00:00
bfd daily update 2006-08-06 00:00:06 +00:00
binutils * readelf.c (dump_relocations): Handle MIPS-specific 2006-08-02 09:45:12 +00:00
config Sync from GCC 2006-07-25 08:39:57 +00:00
cpu * iq2000.cpu: Fix include paths for iq2000m.cpu and iq10.cpu. 2006-05-22 09:07:20 +00:00
elfcpp Initial CVS checkin of gold 2006-08-04 23:10:59 +00:00
etc * texi2pod.pl: Correct handling of absolute @include. 2006-05-31 15:47:48 +00:00
gas bfd/ 2006-08-04 13:13:56 +00:00
gdb *** empty log message *** 2006-08-06 00:00:34 +00:00
gold Include <cassert> 2006-08-04 23:20:34 +00:00
gprof Fix spelling typos 2006-07-24 13:49:50 +00:00
include * ldmain.c (main): Initialise print_gc_sections field of link_info structure. 2006-08-04 14:53:26 +00:00
intl * Makefile.in (install-info, install-dvi, install-ps, install-pdf): 2006-06-07 15:43:36 +00:00
ld fix my name 2006-08-06 05:24:32 +00:00
libiberty merge from gcc 2006-07-27 18:05:31 +00:00
opcodes opcodes/ 2006-07-29 08:55:38 +00:00
readline Readline 5.1 import for HEAD. 2006-05-05 18:26:14 +00:00
sim compile.c (OBITOP): Bit address mask low three bit. 2006-07-19 06:27:04 +00:00
texinfo
.cvsignore
ChangeLog Sync from GCC 2006-07-25 08:39:57 +00:00
compile
config-ml.in 2006-06-08 Jeff Johnston <jjohnstn@redhat.com> 2006-06-08 16:10:12 +00:00
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 Sync from GCC 2006-07-25 08:39:57 +00:00
configure.in Sync from GCC 2006-07-25 08:39:57 +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 ChangeLog: 2006-07-04 20:31:03 +00:00
ltmain.sh
MAINTAINERS 2006-05-22 Steve Ellcey <sje@cup.hp.com> 2006-05-22 15:30:13 +00:00
Makefile.def * Makefile.def: Add dependencies for configure-opcodes 2006-07-17 17:04:21 +00:00
Makefile.in 2006-07-19 Paolo Bonzini <bonzini@gnu.org> 2006-07-19 17:06:06 +00:00
Makefile.tpl 2006-07-19 Paolo Bonzini <bonzini@gnu.org> 2006-07-19 17:06:06 +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.