freebsd-skq/contrib/binutils
2000-11-15 21:24:10 +00:00
..
bfd We use the stock version of this file now. 2000-11-15 21:11:53 +00:00
binutils We use the stock version of this file now. 2000-11-15 21:20:56 +00:00
config Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
etc None of these files are used in our build, nor do I really believe 2000-06-20 06:08:35 +00:00
gas Merge conflicts into Binutils 2.10.1. 2000-11-15 21:23:09 +00:00
include This commit was generated by cvs2svn to compensate for changes in r68765, 2000-11-15 20:52:56 +00:00
ld Merge rev 1.2 (FreeBSD configuration support) into Binutils 2.10.1. 2000-11-15 21:24:10 +00:00
libiberty Import of GNU Binutils version 2.10.1. 2000-11-15 20:52:56 +00:00
opcodes Import a virgin (but trimed) Binutils 2.10 release. 2000-06-20 06:20:42 +00:00
ChangeLog Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
config-ml.in Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
config.guess Import of GNU Binutils version 2.10.1. 2000-11-15 20:52:56 +00:00
config.sub Import of GNU Binutils version 2.10.1. 2000-11-15 20:52:56 +00:00
configure Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
configure.in Import of GNU Binutils version 2.10.1. 2000-11-15 20:52:56 +00:00
FREEBSD-deletelist Upgrade to Binutils 2.10.0. 2000-07-06 21:33:51 +00:00
FREEBSD-upgrade Upgrade instructions for the sourceware_binutils-2_10-branch_anoncvs_20000512 2000-06-18 21:32:11 +00:00
FREEBSD-Xlist Remove *mip* and *decstation* from the filter, per FREEBSD-updating. 1999-02-28 23:11:09 +00:00
install-sh Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
install.sh Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
ltconfig Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
ltmain.sh Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
Makefile.in Import of GNU Binutils version 2.10.1. 2000-11-15 20:52:56 +00:00
missing Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
mkinstalldirs Import GNU binutils-2.9.1. This will break things for a few minutes 1998-09-06 22:57:45 +00:00
move-if-change Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
README Import GNU binutils-2.9.1. This will break things for a few minutes 1998-09-06 22:57:45 +00:00
symlink-tree Import GNU binutils-2.9.1. This will break things for a few minutes 1998-09-06 22:57:45 +00:00
ylwrap Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00

		   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.