freebsd-skq/contrib/binutils
David E. O'Brien 79a225640d Merge rev 1.2 into Binutils 2.11[.0].
Teach `ld' how to access FreeBSD's ld ELF hints.
2001-05-28 06:21:27 +00:00
..
bfd CVS is too stupid to realize we use the stock version of this file now. 2001-05-28 05:54:56 +00:00
binutils Return to the vendor's version of this file. 2001-05-28 06:05:28 +00:00
config Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +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 Use the stock version of this file now. 2001-05-28 06:14:37 +00:00
include This commit was generated by cvs2svn to compensate for changes in r77298, 2001-05-28 05:21:37 +00:00
ld Merge rev 1.2 into Binutils 2.11[.0]. 2001-05-28 06:21:27 +00:00
libiberty This commit was generated by cvs2svn to compensate for changes in r77298, 2001-05-28 05:21:37 +00:00
opcodes This commit was generated by cvs2svn to compensate for changes in r77298, 2001-05-28 05:21:37 +00:00
ChangeLog Import of GNU Binutils version 2.10.1. 2000-11-25 10:29:36 +00:00
config-ml.in Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
config.guess Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
config.if Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
config.sub Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
configure Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
configure.in Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
FREEBSD-deletelist Remove MIPS support. 2001-04-11 00:12:48 +00:00
FREEBSD-upgrade Update for the Bintuils 2.10.1 import. 2000-11-23 12:28:19 +00:00
FREEBSD-Xlist Remove MIPS support. 2001-04-11 00:12:48 +00:00
install-sh Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
ltconfig Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
ltmain.sh Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
Makefile.in Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
md5.sum Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +00:00
missing Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
mkinstalldirs
move-if-change Import of Binutils 2.10 snapshot. 2000-05-12 23:15:20 +00:00
README
symlink-tree Import of GNU Binutils version 2.11.0. 2001-05-28 05:21:37 +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.