Binutils with MCST patches
Go to file
Stephane Carrez 4f69f9744a * gas/m68hc11/malis.s: New test to verify compliance with Motorola
Assembly Language Input Standard.
	* gas/m68hc11/malis.d: New file.
	* gas/m68hc11/malis-include.s: New file.
	* gas/m68hc11/all.exp: Add the new test.
2001-02-04 13:53:49 +00:00
bfd Fix typo 2001-02-03 00:53:10 +00:00
binutils Another HAVE_DOS_BASED_FILE_SYSTEM check. 2001-01-31 06:02:18 +00:00
config
etc
gas * gas/m68hc11/malis.s: New test to verify compliance with Motorola 2001-02-04 13:53:49 +00:00
gdb * config/djgpp/fnchange.lst: Tweak to make consistent with the 2001-02-04 07:56:38 +00:00
gprof * basic_blocks.c: #include <unistd.h> only if it exists. 2001-01-27 19:54:49 +00:00
include Binutils portion of fix for syntax array elements when max 2001-02-02 23:04:40 +00:00
intl
ld Replace occurances of -oformat with --oformat. 2001-02-01 18:44:43 +00:00
libiberty merge from gcc 2001-02-02 20:08:59 +00:00
mmalloc
opcodes Binutils portion of fix for syntax array elements when max 2001-02-02 23:04:40 +00:00
readline * rltty.c (save_tty_chars): Fix compilation-stopping typo. 2001-01-08 14:57:30 +00:00
sim Add parentheses ready for future conbtribution 2001-02-01 20:56:35 +00:00
texinfo
.cvsignore
ChangeLog Handle hppa64-linux systems. 2001-01-30 02:17:40 +00:00
config-ml.in
config.guess Handle hppa64-linux systems. 2001-01-30 02:17:40 +00:00
config.if
config.sub * config.sub, config.guess: Update from subversions. 2001-01-07 12:04:21 +00:00
configure
configure.in 2001-01-15 Ben Elliston <bje@redhat.com> 2001-01-15 00:19:42 +00:00
COPYING
COPYING.LIB
COPYING.NEWLIB 2001-01-15 Jeff Johnston <jjohnstn@redhat.com> 2001-01-15 18:20:18 +00:00
djunpack.bat
gettext.m4
install-sh
libtool.m4 * ltcf-gcj.sh (lt_simple_link_test_code): Remove stray `(0)'. 2001-01-24 02:27:02 +00:00
ltcf-c.sh * ltcf-c.sh (ld_shlibs) [aix5*]: Disable on unknown CPU types. 2001-01-27 19:22:59 +00:00
ltcf-cxx.sh * ltcf-cxx.sh (ac_cv_prog_cc_pic_works, ac_cv_prog_cc_static_works): 2001-01-27 19:36:45 +00:00
ltcf-gcj.sh * ltcf-c.sh (ld_shlibs) [aix5*]: Disable on unknown CPU types. 2001-01-27 19:22:59 +00:00
ltconfig * ltconfig: Shell portability fix for the tagname validity check. 2001-01-27 19:34:13 +00:00
ltmain.sh * ltmain.sh (TAG disable-shared, TAG disable-static): Make sure we 2001-01-24 20:09:37 +00:00
MAINTAINERS General cleanup. 2001-01-16 05:30:31 +00:00
Makefile.in 2001-01-20 Maciej W. Rozycki <macro@ds2.pg.gda.pl> 2001-01-20 16:57:28 +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
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.