freebsd-dev/contrib/binutils
David E. O'Brien 35754f3b83 Revert this file back to its FSF/Cygnus virgin state.
With jb's rev 1.2 commit to usr.bin/lorder/lorder.sh we don't depend on
the 4.4BSD's ``nm -o'' behavior.

Previous to 4.3BSD-Reno, ``nm -o'' did not output the .o's filename on a
line by itself.  The change occurred between CSRG's nm.c rev 4.8 (1987) and
rev 5.1 (in 1989), which was "new version from Hans Huebner hans@garp.mit.edu,
huebner@db0tui6.BITNET".  The Binutils maintainers would rather cater to
a loud boisterous user of 4.3BSD VAXen which has its own native toolchain,
rather than a modern Unix with multiple orders of magnitude more users
and in which Binutils *is* the native toolchain.
2000-04-20 08:58:04 +00:00
..
bfd Rev 1.3 which resolved conflicts in the 2.9.1 import, used a comment from 2000-04-18 21:00:17 +00:00
binutils Revert this file back to its FSF/Cygnus virgin state. 2000-04-20 08:58:04 +00:00
config
etc
gas Import the Sparc bits of GNU binutils 2.9.1. 2000-04-05 04:09:32 +00:00
include Header file gotten from the Cygnus Sourceware Binutils anoncvs repository 2000-04-18 02:42:12 +00:00
ld Import the Sparc bits of GNU binutils 2.9.1. 2000-04-05 04:09:32 +00:00
libiberty Import GNU binutils-2.9.1. This will break things for a few minutes 1998-09-06 22:57:45 +00:00
opcodes Vendor import of the 19990502 Cygnus Sourceware version of sparc-ops.c. 2000-04-19 17:30:18 +00:00
config-ml.in
config.guess
config.sub
configure
configure.in
FREEBSD-upgrade
FREEBSD-Xlist
install-sh
install.sh
ltconfig
ltmain.sh Import GNU binutils-2.9.1. This will break things for a few minutes 1998-09-06 22:57:45 +00:00
Makefile.in Import GNU binutils-2.9.1. This will break things for a few minutes 1998-09-06 22:57:45 +00:00
missing
mkinstalldirs
move-if-change
README
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.