summaryrefslogtreecommitdiff
path: root/binutils/doc
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2009-09-11 11:16:19 +0000
committerNick Clifton <nickc@redhat.com>2009-09-11 11:16:19 +0000
commit79eec5eda1b569595878141a3e37b16a5aa4844f (patch)
tree303ea274d67a1ffb6d1c6c19f2e8779820a242e0 /binutils/doc
parentc2e9312f0828816e70cf926cd41ec1b0a7c12a66 (diff)
downloadbinutils-redhat-79eec5eda1b569595878141a3e37b16a5aa4844f.tar.gz
* obcopy.c (copy_object): New parameter `input_arch', architecture
of input file, if not specified in input file itself; all callers updated; `binary_architecture' hack removed. (copy_archive, copy_file): New parameter `input_arch', for `copy_object' usage. (copy_main): Accept `-B' (`--binary-architecture') option also for any arch-less input ifile format, not only `binary'; remove bfd_external_binary_architecture hack; instead, add `input_arch' to calls to `copy_file'. * windres.c, windmc.c : Obsolete and useless external references to `bfd_external_binary_architecture' or `bfd_external_machine' removed. * binary.c (binary_object_p): Remove bfd_external_binary_architecture hack. objcopy `-B' (`--binary-architecture') option is now handled in a generic way.
Diffstat (limited to 'binutils/doc')
-rw-r--r--binutils/doc/binutils.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/binutils/doc/binutils.texi b/binutils/doc/binutils.texi
index cc01546498..f67ad134ab 100644
--- a/binutils/doc/binutils.texi
+++ b/binutils/doc/binutils.texi
@@ -1134,9 +1134,9 @@ translation. @xref{Target Selection}, for more information.
@item -B @var{bfdarch}
@itemx --binary-architecture=@var{bfdarch}
-Useful when transforming a raw binary input file into an object file.
-In this case the output architecture can be set to @var{bfdarch}. This
-option will be ignored if the input file has a known @var{bfdarch}. You
+Useful when transforming a architecture-less input file into an object file.
+In this case the output architecture can be set to @var{bfdarch}. This
+option will be ignored if the input file has a known @var{bfdarch}. You
can access this binary data inside a program by referencing the special
symbols that are created by the conversion process. These symbols are
called _binary_@var{objfile}_start, _binary_@var{objfile}_end and