Go to file
Ben Elliston 11010f5a82 * corefile.c (core_init): Report that the executable is not in the
expected executable format rather than "a.out" format.
2006-03-22 03:51:02 +00:00
bfd daily update 2006-03-21 23:00:06 +00:00
binutils * BRANCHES: Remove binutils-csl-arm-2006q1-branch. Document 2006-03-20 18:53:48 +00:00
config
contrib
cpu
etc
gas 2006-03-21 Paul Brook <paul@codesourcery.com> 2006-03-21 22:52:06 +00:00
gdb *** empty log message *** 2006-03-22 00:00:33 +00:00
gprof * corefile.c (core_init): Report that the executable is not in the 2006-03-22 03:51:02 +00:00
include * hppa.h (SHF_HP_TLS, SHF_HP_NEAR_SHARED, SHF_HP_FAR_SHARED, 2006-03-20 01:07:29 +00:00
intl
ld
libiberty
mmalloc
opcodes
readline * histfile.c (read_history_range): Remove '\r' character from 2006-03-21 14:58:24 +00:00
sim
texinfo
.cvsignore
ChangeLog
compile
config-ml.in
config.guess
config.sub
configure
configure.in
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
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
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.