Binutils with MCST patches
Go to file
Christopher Faylor c4c31f17e8 remove conflict marker 2003-01-30 01:42:01 +00:00
bfd daily update 2003-01-29 23:00:05 +00:00
binutils * readelf.c (dump_relocations): Reorder the r_info field for 2003-01-28 12:51:07 +00:00
config * acx.m4: Name cache variables properly. 2002-12-28 17:57:49 +00:00
contrib
etc 2003-01-02 H.J. Lu <hjl@gnu.org> 2003-01-02 20:51:02 +00:00
gas line_comment_chars: Add '#'. This makes the assembler's handling of 2003-01-29 10:05:52 +00:00
gdb remove conflict marker 2003-01-30 01:42:01 +00:00
gprof oops - omitted from previous delta 2002-12-02 14:03:15 +00:00
include * mips.h (EF_MIPS_XGOT): Define. 2003-01-28 00:01:08 +00:00
intl
ld Add code to prevent importing a dll multiple times. 2003-01-28 11:39:43 +00:00
libiberty * Makefile.in (all-subdir, check-subdir, installcheck-subdir) 2003-01-28 21:53:39 +00:00
mmalloc
opcodes (print_insn_sparc): When examining values added in to rs1, make sure that 2003-01-29 12:51:57 +00:00
readline 2003-01-09 Michael Chastain <mec@shout.net> 2003-01-11 00:43:53 +00:00
sim Missed one... 2003-01-16 20:03:30 +00:00
texinfo
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2002-12-20 Jeff Johnston <jjohnstn@redhat.com> 2002-12-20 21:36:01 +00:00
COPYING.NEWLIB 2002-12-20 Jeff Johnston <jjohnstn@redhat.com> 2002-12-20 21:36:01 +00:00
ChangeLog * configure.in: Revert 24Jan change. 2003-01-27 19:47:23 +00:00
MAINTAINERS
Makefile.def * Makefile.in: Rebuilt. 2002-12-31 22:51:53 +00:00
Makefile.in * configure.in: Substitute TOPLEVEL_CONFIGURE_ARGUMENTS. 2003-01-10 21:43:31 +00:00
Makefile.tpl * configure.in: Substitute TOPLEVEL_CONFIGURE_ARGUMENTS. 2003-01-10 21:43:31 +00:00
README
README-maintainer-mode
config-ml.in
config.guess [ ChangeLog ] 2003-01-08 22:09:32 +00:00
config.if
config.sub [ ChangeLog ] 2003-01-08 22:09:32 +00:00
configure * configure.in: Revert 24Jan change. 2003-01-27 19:47:23 +00:00
configure.in * configure.in: Revert 24Jan change. 2003-01-27 19:47:23 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh 2002-12-01 Nathanael Nerode <neroden@gcc.gnu.org> 2002-12-01 12:01:26 +00:00
ltcf-cxx.sh
ltcf-gcj.sh 2002-12-01 Nathanael Nerode <neroden@gcc.gnu.org> 2002-12-01 12:01:26 +00:00
ltconfig
ltmain.sh
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-README
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
setup.com
src-release * src-release (ETC_SUPPORT): Add fdl.texi and texi2pod.pl. 2003-01-02 00:50:57 +00:00
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.