NetBSD/gnu/dist/binutils
christos 25a293877a Don't be pedantic about requiring things to be ordinary files. Handle
character special devices specially so that eg. nm /dev/ksyms works.
2005-05-16 03:24:44 +00:00
..
bfd Use the tradmips 64bit vectors/emulations. 2005-01-14 07:41:42 +00:00
binutils Don't be pedantic about requiring things to be ordinary files. Handle 2005-05-16 03:24:44 +00:00
config
contrib
cpu
etc bfd/elflink.c 2004-12-08 14:57:53 +00:00
gas Switch MIPS from using the "littlemips" and "bigmips" vectors to the 2005-01-09 12:58:00 +00:00
gprof bfd/elflink.c 2004-12-08 14:57:53 +00:00
include
intl
ld hppaelf_create_output_section_statements is valid for the NetBSD hppa 2005-01-19 12:49:30 +00:00
libiberty
opcodes Apply patch from the RedHat CVS tree. Avoids issue with -O3 using the 2005-04-24 23:53:18 +00:00
texinfo
.cvsignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
ChangeLog
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
README
README-maintainer-mode
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
gettext.m4
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com
src-release
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.