Binutils with MCST patches
Go to file
1999-02-09 02:19:18 +00:00
bfd Mon Feb 8 11:18:14 1999 Andreas Schwab <schwab@issan.cs.uni-dortmund.de> 1999-02-08 16:19:20 +00:00
binutils m32rx -> cygnus sanitization change. 1999-02-05 17:34:40 +00:00
config * configure.in: makefile stub for cygwin target is probably 1998-12-31 01:37:06 +00:00
gas Fix tests to pass on ARM targets 1999-02-08 17:29:05 +00:00
gdb * NEWS: Mention new X packet and PowerPC variant support. 1999-02-09 02:19:18 +00:00
gprof * gprof.texi (Symspecs): Mention that you have to add any 1998-12-07 02:58:45 +00:00
include m32rx -> cygnus sanitization change. 1999-02-05 17:20:25 +00:00
intl
ld Add support for StrongARM target. 1999-02-08 12:47:01 +00:00
mmalloc
opcodes * Makefile.am: Rebuild dependencies. 1999-02-05 05:36:07 +00:00
readline new dir cross-build needs to be kept. 1999-01-20 15:18:32 +00:00
sim Add support for StrongARM target 1999-02-08 12:44:13 +00:00
.cvsignore
.Sanitize m32rx -> cygnus sanitization changes. 1999-02-05 17:49:42 +00:00
Build-A-Release.mk
ChangeLog Add support for strongarm target. 1999-02-08 12:35:29 +00:00
config-ml.in
config.guess
config.if
config.sub Add support for strongarm target. 1999-02-08 12:35:29 +00:00
configure
configure.bat
configure.in Add support for strongarm target. 1999-02-08 12:35:29 +00:00
COPYING
COPYING.LIB
DOC.Sanitize
install-sh
install-texi.in
Install.in
intro.texi
ltconfig
ltmain.sh
makeall.bat
Makefile.in Merge egcs-19990112. 1999-01-15 08:19:02 +00:00
makefile.vms
mdate-sh
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
Pack-A-Progressive
README
setup.com
symlink-tree
tape-labels-tex.in
test-build.mk
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.