freebsd-skq/contrib/binutils
David E. O'Brien c815a20cb2 Change our ELF binary branding to something more acceptable to the Binutils
maintainers.

After we established our branding method of writing upto 8 characters of
the OS name into the ELF header in the padding; the Binutils maintainers
and/or SCO (as USL) decided that instead the ELF header should grow two new
fields -- EI_OSABI and EI_ABIVERSION.  Each of these are an 8-bit unsigned
integer.  SCO has assigned official values for the EI_OSABI field.  In
addition to this, the Binutils maintainers and NetBSD decided that a better
ELF branding method was to include ABI information in a ".note" ELF
section.

With this set of changes, we will now create ELF binaries branded using
both "official" methods.  Due to the complexity of adding a section to a
binary, binaries branded with ``brandelf'' will only brand using the
EI_OSABI method.  Also due to the complexity of pulling a section out of an
ELF file vs. poking around in the ELF header, our image activator only
looks at the EI_OSABI header field.

Note that a new kernel can still properly load old binaries except for
Linux static binaries branded in our old method.

  *
  * For a short period of time, ``ld'' will also brand ELF binaries
  * using our old method.  This is so people can still use kernel.old
  * with a new world.  This support will be removed before 5.0-RELEASE,
  * and may not last anywhere upto the actual release.  My expiration
  * time for this is about 6mo.
  *
2000-04-18 02:39:26 +00:00
..
bfd Change our ELF binary branding to something more acceptable to the Binutils 2000-04-18 02:39:26 +00:00
binutils Restore traditional behaviour by allowing tabs in strings. In deference 1998-12-14 13:27:48 +00:00
config Import files needed to build mips binaries with binutils 2.9.1. 1999-02-28 23:08:24 +00:00
etc
gas This commit was generated by cvs2svn to compensate for changes in r59024, 2000-04-05 04:09:32 +00:00
include Import the Sparc bits of GNU binutils 2.9.1. 2000-04-05 04:09:32 +00:00
ld This commit was generated by cvs2svn to compensate for changes in r59024, 2000-04-05 04:09:32 +00:00
libiberty
opcodes Import the Sparc bits of GNU binutils 2.9.1. 2000-04-05 04:09:32 +00:00
config-ml.in
config.guess
config.sub
configure
configure.in
FREEBSD-upgrade We've been using 2.9.1 tools for some time now, so reflect that in the 1999-02-28 22:31:17 +00:00
FREEBSD-Xlist Remove *mip* and *decstation* from the filter, per FREEBSD-updating. 1999-02-28 23:11:09 +00:00
install-sh
install.sh
ltconfig
ltmain.sh
Makefile.in
missing
mkinstalldirs
move-if-change
README
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.