Binutils with MCST patches
Go to file
Jason Thorpe a074e149a5 * config/tc-sh64.h (MD_PCREL_FROM_SECTION): Undef before redefining. 2002-06-04 02:45:51 +00:00
bfd * elf.c (setup_group): Set SEC_LINK_ONCE on GRP_COMDAT groups. 2002-06-04 01:05:21 +00:00
binutils * objdump.c: Fix formatting. 2002-06-03 13:02:04 +00:00
config * acinclude.m4: Allow for PWDCMD to override hardcoded pwd. 2002-05-22 21:06:53 +00:00
etc * fdl.texi: New file. 2002-02-28 03:34:36 +00:00
gas * config/tc-sh64.h (MD_PCREL_FROM_SECTION): Undef before redefining. 2002-06-04 02:45:51 +00:00
gdb *** empty log message *** 2002-06-04 00:00:06 +00:00
gprof Do not attempt to create a .gmo file if the sources are read-only. 2002-05-02 08:15:00 +00:00
include include/elf/ 2002-06-02 02:28:45 +00:00
intl
ld * ldlang.c (section_already_linked): Call bfd_discard_group. Typo fix. 2002-06-04 01:07:29 +00:00
libiberty merge from gcc 2002-05-13 20:01:19 +00:00
mmalloc From 2002-03-05 Scott Pakin <pakin@uiuc.edu> 2002-04-07 17:58:57 +00:00
opcodes 2002-05-31 Chris G. Demetriou <cgd@broadcom.com> 2002-05-31 20:46:07 +00:00
readline
sim 2002-06-03 Chris Demetriou <cgd@broadcom.com> 2002-06-04 01:35:23 +00:00
texinfo * standards.texi: Import February 14, 2002 version. 2002-02-27 02:13:36 +00:00
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2002-05-07 Jeff Johnston <jjohnstn@redhat.com> 2002-05-07 17:52:36 +00:00
COPYING.NEWLIB
ChangeLog * Makefile.in: Replace HOST_PREFIX, HOST_PREFIX_1 with BUILD_PREFIX, 2002-05-31 20:09:45 +00:00
MAINTAINERS * MAINTAINERS: Update dejagnu/ 2002-04-07 19:17:07 +00:00
Makefile.in * Makefile.in: Replace HOST_PREFIX, HOST_PREFIX_1 with BUILD_PREFIX, 2002-05-31 20:09:45 +00:00
README
README-maintainer-mode
config-ml.in * config-ml.in: Propogate DESTDIR also. 2002-05-31 19:30:32 +00:00
config.guess * config.guess: Update to 2002-05-22 version. 2002-05-22 18:36:13 +00:00
config.if
config.sub Add DLX target 2002-05-28 17:56:42 +00:00
configure * Makefile.in: Replace HOST_PREFIX, HOST_PREFIX_1 with BUILD_PREFIX, 2002-05-31 20:09:45 +00:00
configure.in * Makefile.in: Eliminate version-specific references to tcl8.1, tk8.1. 2002-05-31 19:42:41 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh * ltmain.sh (relink_command): Fix typo in previous change. 2002-03-16 14:43:09 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-README
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
setup.com
symlink-tree
ylwrap

README

		   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.