BFD is a an object file library.  It permits applications to use thesame routines to process object files regardless of their format.BFD is used by the GNU debugger, assembler, linker, and the binaryutilities.The documentation on using BFD is scanty and may be occasionallyincorrect.  Pointers to documentation problems, or an entirelyrewritten manual, would be appreciated.There is some BFD internals documentation in doc/bfdint.texi which mayhelp programmers who want to modify BFD.BFD is normally built as part of another package.  See the buildinstructions for that package, probably in a README file in theappropriate directory.BFD supports the following configure options:  --target=TARGET	The default target for which to build the library.  TARGET is	a configuration target triplet, such as sparc-sun-solaris.  --enable-targets=TARGET,TARGET,TARGET...	Additional targets the library should support.  To include	support for all known targets, use --enable-targets=all.  --enable-64-bit-bfd	Include support for 64 bit targets.  This is automatically	turned on if you explicitly request a 64 bit target, but not	for --enable-targets=all.  This requires a compiler with a 64	bit integer type, such as gcc.  --enable-shared	Build BFD as a shared library.  --with-mmap	Use mmap when accessing files.  This is faster on some hosts,	but slower on others.  It may not work on all hosts.Report bugs with BFD to bug-binutils@gnu.org.Patches are encouraged.  When sending patches, always send the outputof diff -u or diff -c from the original file to the new file.  Do notsend default diff output.  Do not make the diff from the new file tothe original file.  Remember that any patch must not break othersystems.  Remember that BFD must support cross compilation from anyhost to any target, so patches which use ``#ifdef HOST'' are notacceptable.  Please also read the ``Reporting Bugs'' section of thegcc manual.Bug reports without patches will be remembered, but they may never getfixed until somebody volunteers to fix them.