Binutils with MCST patches
Go to file
2001-02-01 00:14:40 +00:00
bfd (elf64_hppa_object_p): Set architecture and machine from elf header flags. 2001-01-31 13:28:50 +00:00
binutils Another HAVE_DOS_BASED_FILE_SYSTEM check. 2001-01-31 06:02:18 +00:00
config
etc
gas Fix a null-pointer dereference and some range checks. 2001-01-30 13:13:29 +00:00
gdb 2001-01-31 David Smith <dsmith@redhat.com> 2001-01-31 15:46:36 +00:00
gprof * basic_blocks.c: #include <unistd.h> only if it exists. 2001-01-27 19:54:49 +00:00
include Fix swapgs instruction. 2001-01-24 07:32:34 +00:00
intl
ld (lang_leave_overlay): Don't set lma_region when load_base is specified. 2001-01-25 02:31:42 +00:00
libiberty Remove extraneous tab from the blank line after the most recent entry 2001-01-27 17:28:11 +00:00
mmalloc
opcodes Adds assembly and dis-assembly support for the HPPA wide 2001-01-14 05:14:45 +00:00
readline * rltty.c (save_tty_chars): Fix compilation-stopping typo. 2001-01-08 14:57:30 +00:00
sim Detect installation of SWI vector by running program as well as loading program. 2001-02-01 00:14:40 +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.