summaryrefslogtreecommitdiff
path: root/share/man/man1/aarch64-linux-android-objcopy.1
diff options
context:
space:
mode:
Diffstat (limited to 'share/man/man1/aarch64-linux-android-objcopy.1')
-rw-r--r--share/man/man1/aarch64-linux-android-objcopy.149
1 files changed, 29 insertions, 20 deletions
diff --git a/share/man/man1/aarch64-linux-android-objcopy.1 b/share/man/man1/aarch64-linux-android-objcopy.1
index 870494f..34c0d83 100644
--- a/share/man/man1/aarch64-linux-android-objcopy.1
+++ b/share/man/man1/aarch64-linux-android-objcopy.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
.\"
.\" Standard preamble:
.\" ========================================================================
@@ -38,6 +38,8 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
+. ds C`
+. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
..
-. nr % 0
-. rr F
-.\}
-.el \{\
-. de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+. if \nF \{
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
+. if !\nF==2 \{
+. nr % 0
+. nr F 2
+. \}
+. \}
.\}
+.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -124,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "OBJCOPY 1"
-.TH OBJCOPY 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH OBJCOPY 1 "2014-08-29" "binutils-2.24.0" "GNU Development Tools"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -215,8 +224,8 @@ objcopy [\fB\-F\fR \fIbfdname\fR|\fB\-\-target=\fR\fIbfdname\fR]
\fIinfile\fR [\fIoutfile\fR]
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
-The \s-1GNU\s0 \fBobjcopy\fR utility copies the contents of an object
-file to another. \fBobjcopy\fR uses the \s-1GNU\s0 \s-1BFD\s0 Library to
+The \s-1GNU \s0\fBobjcopy\fR utility copies the contents of an object
+file to another. \fBobjcopy\fR uses the \s-1GNU BFD\s0 Library to
read and write the object files. It can write the destination object
file in a format different from that of the source object file. The
exact behavior of \fBobjcopy\fR is controlled by command-line options.
@@ -448,7 +457,7 @@ not affected). Select which byte in the range begins the copy with
the \fB\-\-byte\fR option. Select the width of the range with the
\&\fB\-\-interleave\-width\fR option.
.Sp
-This option is useful for creating files to program \s-1ROM\s0. It is
+This option is useful for creating files to program \s-1ROM. \s0 It is
typically used with an \f(CW\*(C`srec\*(C'\fR output target. Note that
\&\fBobjcopy\fR will complain if you do not specify the
\&\fB\-\-byte\fR option as well.
@@ -501,7 +510,7 @@ It can be disabled with the \fB\-U\fR option, below.
.PD
Do \fInot\fR operate in \fIdeterministic\fR mode. This is the
inverse of the \fB\-D\fR option, above: when copying archive members
-and writing the archive index, use their actual \s-1UID\s0, \s-1GID\s0, timestamp,
+and writing the archive index, use their actual \s-1UID, GID,\s0 timestamp,
and file mode values.
.Sp
This is the default unless \fIbinutils\fR was configured with
@@ -566,7 +575,7 @@ Set or change the \s-1LMA\s0 address of any sections matching
section will be loaded into memory at program load time. Normally
this is the same as the \s-1VMA\s0 address, which is the address of the
section at program run time, but on some systems, especially those
-where a program is held in \s-1ROM\s0, the two can be different. If \fB=\fR
+where a program is held in \s-1ROM,\s0 the two can be different. If \fB=\fR
is used, the section address is set to \fIval\fR. Otherwise,
\&\fIval\fR is added to or subtracted from the section address. See the
comments under \fB\-\-change\-addresses\fR, above. If
@@ -579,7 +588,7 @@ Set or change the \s-1VMA\s0 address of any section matching
section will be located once the program has started executing.
Normally this is the same as the \s-1LMA\s0 address, which is the address
where the section will be loaded into memory, but on some systems,
-especially those where a program is held in \s-1ROM\s0, the two can be
+especially those where a program is held in \s-1ROM,\s0 the two can be
different. If \fB=\fR is used, the section address is set to
\&\fIval\fR. Otherwise, \fIval\fR is added to or subtracted from the
section address. See the comments under \fB\-\-change\-addresses\fR,
@@ -822,7 +831,7 @@ needed if debugging abilities are required. The suggested procedure
to create these files is as follows:
.RS 4
.IP "1.<Link the executable as normal. Assuming that is is called>" 4
-.IX Item "1.<Link the executable as normal. Assuming that is is called>"
+.IX Item "1.<Link the executable as normal. Assuming that is is called>"
\&\f(CW\*(C`foo\*(C'\fR then...
.ie n .IP "1.<Run ""objcopy \-\-only\-keep\-debug foo foo.dbg"" to>" 4
.el .IP "1.<Run \f(CWobjcopy \-\-only\-keep\-debug foo foo.dbg\fR to>" 4
@@ -847,7 +856,7 @@ optional. You could instead do this:
.PD 0
.ie n .IP "1.<Copy ""foo"" to ""foo.full"">" 4
.el .IP "1.<Copy \f(CWfoo\fR to \f(CWfoo.full\fR>" 4
-.IX Item "1.<Copy foo to foo.full>"
+.IX Item "1.<Copy foo to foo.full>"
.ie n .IP "1.<Run ""objcopy \-\-strip\-debug foo"">" 4
.el .IP "1.<Run \f(CWobjcopy \-\-strip\-debug foo\fR>" 4
.IX Item "1.<Run objcopy --strip-debug foo>"
@@ -871,7 +880,7 @@ basis.
.RE
.IP "\fB\-\-strip\-dwo\fR" 4
.IX Item "--strip-dwo"
-Remove the contents of all \s-1DWARF\s0 .dwo sections, leaving the
+Remove the contents of all \s-1DWARF \s0.dwo sections, leaving the
remaining debugging sections and all symbols intact.
This option is intended for use by the compiler as part of
the \fB\-gsplit\-dwarf\fR option, which splits debug information
@@ -882,7 +891,7 @@ the .dwo file, then the \fB\-\-strip\-dwo\fR option to remove
those sections from the original .o file.
.IP "\fB\-\-extract\-dwo\fR" 4
.IX Item "--extract-dwo"
-Extract the contents of all \s-1DWARF\s0 .dwo sections. See the
+Extract the contents of all \s-1DWARF \s0.dwo sections. See the
\&\fB\-\-strip\-dwo\fR option for more information.
.IP "\fB\-\-file\-alignment\fR \fInum\fR" 4
.IX Item "--file-alignment num"