Binutils with MCST patches
Go to file
Christopher Faylor caad770612 white space
2003-02-15 03:24:54 +00:00
bfd daily update 2003-02-14 23:00:05 +00:00
binutils For N_SLINE only include function_start_offset if the symbol is within a 2003-02-13 10:38:37 +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 * write.c (TC_FORCE_RELOCATION_SUB_SAME): Revert last change. 2003-02-12 23:21:08 +00:00
gdb white space 2003-02-15 03:24:54 +00:00
gprof oops - omitted from previous delta 2002-12-02 14:03:15 +00:00
include Add support for marking ARM ELF binaries as support the Cirrus EP9312 Maverick 2003-02-10 10:44:48 +00:00
intl
ld bfd/ 2003-02-13 22:14:11 +00:00
libiberty merge from gcc 2003-02-13 18:52:46 +00:00
mmalloc 2002-11-28 Elena Zannoni <ezannoni@redhat.com> 2002-11-28 16:46:31 +00:00
opcodes 003-02-12 Dave Brolley <brolley@redhat.com> 2003-02-12 22:33:59 +00:00
readline 2003-01-09 Michael Chastain <mec@shout.net> 2003-01-11 00:43:53 +00:00
sim Commit Sh2E addition 2003-02-06 10:42:33 +00:00
texinfo
.cvsignore
ChangeLog * Makefile.tpl (RANLIB): Define. 2003-02-14 21:15:37 +00:00
config-ml.in
config.guess [ ChangeLog ] 2003-01-08 22:09:32 +00:00
config.if * config.if: Copy from GCC. 2003-01-30 11:59:17 +00:00
config.sub [ ChangeLog ] 2003-01-08 22:09:32 +00:00
configure Source Navigator is now on sourceforge... 2003-02-06 20:36:19 +00:00
configure.in Source Navigator is now on sourceforge... 2003-02-06 20:36:19 +00:00
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
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
MAINTAINERS
Makefile.def Source Navigator is now on sourceforge... 2003-02-06 20:36:19 +00:00
Makefile.in * Makefile.tpl (RANLIB): Define. 2003-02-14 21:15:37 +00:00
Makefile.tpl * Makefile.tpl (RANLIB): Define. 2003-02-14 21:15:37 +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
src-release * src-release (ETC_SUPPORT): Add fdl.texi and texi2pod.pl. 2003-01-02 00:50:57 +00:00
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.