NetBSD/gnu/dist/binutils
christos 2853bbf4b7 use %option instead of #define YY_NO_... 2009-10-29 14:49:02 +00:00
..
bfd Allocate relocation section using bfd_zalloc() to ensure no garbage 2009-05-04 17:56:35 +00:00
binutils The "disabled target" for ar.1 should be NetBSD_DISABLED_ar.1, not 2009-03-08 16:38:32 +00:00
config Resolve conflicts. 2006-02-02 22:03:53 +00:00
cpu Import binutils 2.16.1. 2006-02-02 20:58:06 +00:00
etc Resolve conflicts. 2006-02-02 22:03:53 +00:00
gas Steal code from tc-sparc.[ch] to implement a vax specific "cons" routine. 2007-03-16 22:16:12 +00:00
gprof Remove various dotfiles that wandered their way in. 2006-06-18 08:59:39 +00:00
include Add support for --ignore-unresolved-symbol 2008-04-03 15:40:17 +00:00
intl Import binutils 2.16.1. 2006-02-02 20:58:06 +00:00
ld use %option instead of #define YY_NO_... 2009-10-29 14:49:02 +00:00
libiberty Changed error message of ENOPROTOOPT to "Protocol option not available". 2006-10-31 00:38:06 +00:00
opcodes Do not include sh64 support into sh*-netbsdelf* targets unless 2007-04-20 11:09:00 +00:00
texinfo
COPYING
COPYING.LIB
Makefile.def Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
Makefile.in Resolve conflicts. 2006-02-02 22:03:53 +00:00
Makefile.tpl Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
README
config-ml.in Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
config.guess Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
config.sub Resolve conflicts. 2006-02-02 22:03:53 +00:00
configure Remove gprof from the "native only" list so that it can be cross-built. 2006-09-13 02:42:57 +00:00
configure.in Remove gprof from the "native only" list so that it can be cross-built. 2006-09-13 02:42:57 +00:00
gettext.m4 Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
install-sh Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
libtool.m4 Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
ltcf-c.sh Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
ltcf-cxx.sh Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
ltcf-gcj.sh Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
ltconfig Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
ltmain.sh Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
makefile.vms
md5.sum Resolve conflicts. 2006-02-02 22:03:53 +00:00
missing Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
mkdep
mkinstalldirs Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
move-if-change
setup.com
src-release Import binutils 2.16.1. 2006-02-02 20:37:52 +00:00
symlink-tree
ylwrap

README

		   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.