freebsd-skq/contrib/binutils
John Polstra 12df71b07c Configuration changes to support FreeBSD. The linker only works for
ELF, not a.out.  But all the other tools support both.  I'm not so
sure about the assembler -- it might need more work.
1998-03-01 23:26:32 +00:00
..
bfd Configuration changes to support FreeBSD. The linker only works for 1998-03-01 23:26:32 +00:00
binutils Fix the output format of "nm" so that it works properly for FreeBSD's 1998-03-01 23:20:03 +00:00
config Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
etc Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
gas Configuration changes to support FreeBSD. The linker only works for 1998-03-01 23:26:32 +00:00
include Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
ld Configuration changes to support FreeBSD. The linker only works for 1998-03-01 23:26:32 +00:00
libiberty Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
opcodes Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
config-ml.in Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
config.guess Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
config.sub Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
configure Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
configure.in Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
FREEBSD-upgrade Add upgrade instructions and helper file. 1998-03-01 23:13:26 +00:00
FREEBSD-Xlist Add upgrade instructions and helper file. 1998-03-01 23:13:26 +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
Makefile.in Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
move-if-change Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
README Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +00:00
symlink-tree Initial import of GNU binutils version 2.8.1. Believe it or not, 1998-03-01 22:58:51 +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 CC=gcc

A similar example using csh:

	setenv CC gcc
	./configure
	make CC=gcc

See etc/cfg-paper.texi, etc/configure.texi, and/or the README files in
various subdirectories, for more details.

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.