1
0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-25 11:37:56 +00:00
freebsd/contrib/binutils
Pedro F. Giffuni 8bc5011859 Align text correctly by using tabs instead of spaces.
The text was copy-pasted from the lines that carry the bogus spaces.
This is a non-functional change.
2017-05-27 20:01:50 +00:00
..
bfd Bring some rough support for FreeBSD S/390 to the GNU toolchain. 2017-05-23 16:38:10 +00:00
binutils Generate manpage out of the texinfo files using texi2mdoc 2015-03-02 17:20:34 +00:00
config
etc
gas Fix parsing of 'vmov Q<n>.F32,Q<n>.F32' instruction. 2017-05-10 05:07:41 +00:00
gprof
include Replace local prototype of basename() with an inclusion of <libgen.h>. 2016-05-29 16:10:01 +00:00
ld Align text correctly by using tabs instead of spaces. 2017-05-27 20:01:50 +00:00
libiberty
opcodes Add rfdi opcode to binutils 2017-02-01 02:42:45 +00:00
ChangeLog
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
FREEBSD-deletelist
FREEBSD-upgrade
FREEBSD-Xlist
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
missing
mkinstalldirs
move-if-change
README
README-maintainer-mode
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.