1
0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-20 11:11:24 +00:00
freebsd/contrib/binutils
David E. O'Brien 89b2e0c349 Merge rev 1.2 (FreeBSD a.out configuration support) into the
Binutils 2.12_20020622 snap.
2002-07-05 20:44:29 +00:00
..
bfd We use the stock version of this file. 2002-07-05 20:34:21 +00:00
binutils We use the stock version of this file as in rev 1.4. 2002-07-05 20:35:38 +00:00
config Import of Binutils from the FSF 2.12 branch (just post-.1 release). 2002-07-05 20:16:34 +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. 2002-07-05 20:37:36 +00:00
include This commit was generated by cvs2svn to compensate for changes in r99461, 2002-07-05 20:16:34 +00:00
ld Merge rev 1.2 (FreeBSD a.out configuration support) into the 2002-07-05 20:44:29 +00:00
libiberty Import of Binutils from the FSF 2.12 branch (pre-.0 release). 2002-02-22 04:18:42 +00:00
opcodes This commit was generated by cvs2svn to compensate for changes in r99461, 2002-07-05 20:16:34 +00:00
ChangeLog Import of Binutils from the FSF 2.12 branch (just post-.0 release). 2002-03-20 21:37:13 +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 Binutils from the FSF 2.12 branch (just post-.0 release). 2002-03-20 21:37:13 +00:00
config.if Enlist the FreeBSD-CURRENT users as testers of what is to become Binutils 2002-01-27 12:00:11 +00:00
config.sub Import of Binutils from the FSF 2.12 branch (just post-.0 release). 2002-03-20 21:37:13 +00:00
configure Import of Binutils from the FSF 2.12 branch (pre-.0 release). 2002-02-22 04:18:42 +00:00
configure.in Import of Binutils from the FSF 2.12 branch (pre-.0 release). 2002-02-22 04:18:42 +00:00
FREEBSD-deletelist Explain how I did the binutils_2_12_anoncvs_20020221 import. 2002-02-22 05:11:49 +00:00
FREEBSD-upgrade Add note about genscripts.sh. 2002-03-13 07:16:00 +00:00
FREEBSD-Xlist Update for the Bintuils 2.11.0 import. 2001-05-28 17:48:04 +00:00
install-sh
libtool.m4 Import of Binutils from the FSF 2.12 branch (pre-.0 release). 2002-02-22 04:18:42 +00:00
ltcf-c.sh Import of Binutils from the FSF 2.12 branch (pre-.0 release). 2002-02-22 04:18:42 +00:00
ltcf-cxx.sh Enlist the FreeBSD-CURRENT users as testers of what is to become Binutils 2002-01-27 12:00:11 +00:00
ltcf-gcj.sh Enlist the FreeBSD-CURRENT users as testers of what is to become Binutils 2002-01-27 12:00:11 +00:00
ltconfig Import of Binutils from the FSF 2.12 branch (pre-.0 release). 2002-02-22 04:18:42 +00:00
ltmain.sh Enlist the FreeBSD-CURRENT users as testers of what is to become Binutils 2002-01-27 12:00:11 +00:00
MAINTAINERS Enlist the FreeBSD-CURRENT users as testers of what is to become Binutils 2002-01-27 12:00:11 +00:00
Makefile.in Import of Binutils from the FSF 2.12 branch (pre-.0 release). 2002-02-22 04:18:42 +00:00
md5.sum Import of GNU Binutils version 2.11.2. 2001-06-26 16:57:43 +00:00
missing
mkinstalldirs
move-if-change
README
README-maintainer-mode Import of Binutils from the FSF 2.11 branch [checked out 19-July-2001]. 2001-07-20 03:29:51 +00:00
symlink-tree Enlist the FreeBSD-CURRENT users as testers of what is to become Binutils 2002-01-27 12:00:11 +00:00
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.