NetBSD/gnu/dist/binutils
skrll c0d9bc63a5 Check that a .rodata section description has been provided before putting
orphan sections in it.

Closes PR/33129.
2006-04-17 07:05:17 +00:00
..
bfd Fix merge botch. 2006-02-03 09:24:20 +00:00
binutils Pull in my readelf fix from binutils-current for the new EF_SH* flags. 2006-02-17 13:14:25 +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 We want "traditional" abi on mips. 2006-02-04 12:08:22 +00:00
gprof Resolve conflicts. 2006-02-02 22:03:55 +00:00
include Resolve conflicts. 2006-02-02 22:03:55 +00:00
intl Import binutils 2.16.1. 2006-02-02 20:58:06 +00:00
ld Check that a .rodata section description has been provided before putting 2006-04-17 07:05:17 +00:00
libiberty Resolve conflicts. 2006-02-02 22:03:55 +00:00
opcodes Resolve conflicts. 2006-02-02 22:03:55 +00:00
texinfo initial import of binutils 2.15 branch (20041204) 2004-12-08 09:52:50 +00:00
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 Resolve conflicts. 2006-02-02 22:03:53 +00:00
configure.in Resolve conflicts. 2006-02-02 22:03:53 +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 initial import of binutils 2.15 branch (20041204) 2004-12-08 09:52:50 +00:00
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.