Binutils with MCST patches
Go to file
Jakub Jelinek 25263aad5c * section.c (_bfd_strip_section_from_output): Don't count
SEC_EXCLUDE sections as references.  Set SEC_EXCLUDE.
2001-10-18 08:22:44 +00:00
bfd * section.c (_bfd_strip_section_from_output): Don't count 2001-10-18 08:22:44 +00:00
binutils support multiple options to the -w switch 2001-10-13 10:00:30 +00:00
config
etc
gas [gas/testsuite/ChangeLog] 2001-10-18 01:42:16 +00:00
gdb * README: Mention problems with HP/UX. 2001-10-18 04:35:35 +00:00
gprof Regenerate configure to include the gettext.m4 change. Update 2001-10-03 13:46:35 +00:00
include 2001-10-17 Chris Demetriou <cgd@broadcom.com> 2001-10-18 01:50:26 +00:00
intl
ld * po/POTFILES.in: Regenerate. 2001-10-17 05:41:53 +00:00
libiberty merge from gcc 2001-10-17 22:35:28 +00:00
mmalloc
opcodes [gas/testsuite/ChangeLog] 2001-10-18 01:42:16 +00:00
readline Clone src/config.guess. Mention in MAINTAINERS. 2001-07-20 20:08:08 +00:00
sim Removed a section of code that didn't do anything, but left values in 2001-08-02 00:50:38 +00:00
texinfo
.cvsignore
ChangeLog * gettext.m4: Test po/POTFILES.in exists before trying to read. 2001-10-03 01:46:25 +00:00
config-ml.in
config.guess * config.sub, config.guess: Import latest from subversions. 2001-09-28 21:04:51 +00:00
config.if
config.sub * config.sub, config.guess: Import latest from subversions. 2001-09-28 21:04:51 +00:00
configure
configure.in 2001-09-19 Ben Elliston <bje@redhat.com> 2001-09-19 06:07:36 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB
djunpack.bat
gettext.m4 * gettext.m4: Test po/POTFILES.in exists before trying to read. 2001-10-03 01:46:25 +00:00
install-sh
libtool.m4 * ltconfig, ltmain.sh, libtool.m4, ltcf-c.sh, ltcf-cxx.sh, 2001-05-20 19:02:56 +00:00
ltcf-c.sh * ltcf-c.sh (archive_cmds, archive_expsym_cmds) [solaris, 2001-06-04 19:33:12 +00:00
ltcf-cxx.sh * ltcf-cxx.sh (osf3/osf4/osf5): Support creation of C++ shared 2001-05-28 21:05:35 +00:00
ltcf-gcj.sh * ltconfig, ltmain.sh, libtool.m4, ltcf-c.sh, ltcf-cxx.sh, 2001-05-20 19:02:56 +00:00
ltconfig * ltconfig, ltmain.sh: Upgrade to libtool 1.4a 1.641.2.256. 2001-05-28 20:56:20 +00:00
ltmain.sh * ltconfig, ltmain.sh: Upgrade to libtool 1.4a 1.641.2.256. 2001-05-28 20:56:20 +00:00
MAINTAINERS * MAINTAINERS: Clarify libiberty merge rules and procedures. 2001-07-26 14:20:05 +00:00
Makefile.in * Makefile.in (configure-target-gperf): Depend on $(ALL_GCC_CXX). 2001-09-29 19:38:32 +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.