Binutils with MCST patches
Go to file
2002-03-20 12:03:27 +00:00
bfd Fix problem with linking shared libstdc++-v3 on AIX. 2002-03-20 12:03:27 +00:00
binutils Add AIX 64 shared library support and emulation layer for binutils 2002-03-18 12:46:27 +00:00
config
etc * fdl.texi: New file. 2002-02-28 03:34:36 +00:00
gas * gas/i386/x86-64-opcode.d: More test cases for x86-64 opcodes. 2002-03-19 12:17:58 +00:00
gdb *** empty log message *** 2002-03-20 00:00:08 +00:00
gprof Updated French translations 2002-03-18 09:44:22 +00:00
include Add AIX 64 shared library support and emulation layer for binutils 2002-03-18 12:46:27 +00:00
intl comment typo fixes 2002-01-21 14:03:27 +00:00
ld * ldlang.c (ldlang_add_undef): If the output bfd has been opened, 2002-03-20 07:49:53 +00:00
libiberty merge from gcc 2002-03-18 20:01:35 +00:00
mmalloc
opcodes * i386-dis.c (prefix_name): Fix handling of 32bit address prefix 2002-03-18 20:11:49 +00:00
readline Rename local ChangeLog and ChangeLog.Cygnus files to ChangeLog.gdb. 2002-02-24 20:52:49 +00:00
sim 2002-03-19 Chris Demetriou <cgd@broadcom.com> 2002-03-20 07:24:20 +00:00
texinfo * standards.texi: Import February 14, 2002 version. 2002-02-27 02:13:36 +00:00
.cvsignore
ChangeLog * ltmain.sh (relink_command): Fix typo in previous change. 2002-03-16 14:43:09 +00:00
config-ml.in
config.guess 2002-02-23 Daniel Jacobowitz <drow@mvista.com> 2002-02-24 00:04:00 +00:00
config.if
config.sub 2002-02-23 Daniel Jacobowitz <drow@mvista.com> 2002-02-24 00:04:00 +00:00
configure
configure.in 2002-03-07 H.J. Lu (hjl@gnu.org) 2002-03-07 17:47:03 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB 2002-02-04 Jeff Johnston <jjohnstn@redhat.com> 2002-02-05 00:29:31 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4 2002-01-27 Daniel Jacobowitz <drow@mvista.com> 2002-01-28 04:59:39 +00:00
ltcf-c.sh 2002-01-27 Daniel Jacobowitz <drow@mvista.com> 2002-01-28 04:59:39 +00:00
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig 2002-01-27 Daniel Jacobowitz <drow@mvista.com> 2002-01-28 04:59:39 +00:00
ltmain.sh * ltmain.sh (relink_command): Fix typo in previous change. 2002-03-16 14:43:09 +00:00
MAINTAINERS 2002-01-16 H.J. Lu (hjl@gnu.org) 2002-01-16 23:20:25 +00:00
Makefile.in * Makefile.in (NOTPARALLEL): New. Use it instead of explicit 2002-03-13 01:19:29 +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 gcc adopts symlink-tree, refer more to libiberty. 2001-12-05 10:07:09 +00:00
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.