Binutils with MCST patches
Go to file
Ben Elliston 2aa9814eac PR binutils/249
* doc/binutils.texi (def file format): New node.
	(dlltool): Use the tool name as the @chapter name, like all the
	other binutils.  Use @file{.def} throughout for consistency.
2004-12-06 21:20:50 +00:00
bfd daily update 2004-12-05 23:00:04 +00:00
binutils PR binutils/249 2004-12-06 21:20:50 +00:00
config Introduce config/gxx-include-dir.m4. 2004-12-03 10:47:07 +00:00
contrib
cpu
etc
gas * Makefile.am (TARG_ENV_HFILES): Add te-armlinuxeabi.h. 2004-12-03 01:22:15 +00:00
gdb 2004-12-05 Randolph Chung <tausq@debian.org> 2004-12-06 03:36:38 +00:00
gprof
include
intl
ld 2004-12-03 H.J. Lu <hongjiu.lu@intel.com> 2004-12-03 17:06:28 +00:00
libiberty
mmalloc
opcodes 2004-12-05 Tomer Levi <Tomer.Levi@nsc.com> 2004-12-05 12:29:04 +00:00
readline
sim Bah, forgot to commit the trivial fix I pointed out myself after applying patch for previous change 2004-12-03 23:34:55 +00:00
texinfo
.cvsignore
ChangeLog Introduce config/gxx-include-dir.m4. 2004-12-03 10:47:07 +00:00
compile
config-ml.in
config.guess
config.sub
configure Introduce config/gxx-include-dir.m4. 2004-12-03 10:47:07 +00:00
configure.in Introduce config/gxx-include-dir.m4. 2004-12-03 10:47:07 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS Remove config.if. 2004-12-03 10:30:13 +00:00
Makefile.def
Makefile.in 2004-12-02 Eric Christopher <echristo@redhat.com> 2004-12-02 23:50:22 +00:00
Makefile.tpl 2004-12-02 Eric Christopher <echristo@redhat.com> 2004-12-02 23:50:22 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release Remove config.if. 2004-12-03 10:30:13 +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.