1OBJCOPY(1) GNU Development Tools OBJCOPY(1)
2
6 objcopy - copy and translate object files
7
9 objcopy [-F bfdname|--target=bfdname]
10 [-I bfdname|--input-target=bfdname]
11 [-O bfdname|--output-target=bfdname]
12 [-B bfdarch|--binary-architecture=bfdarch]
13 [-S|--strip-all]
14 [-g|--strip-debug]
15 [-K symbolname|--keep-symbol=symbolname]
16 [-N symbolname|--strip-symbol=symbolname]
17 [--strip-unneeded-symbol=symbolname]
18 [-G symbolname|--keep-global-symbol=symbolname]
19 [--localize-hidden]
20 [-L symbolname|--localize-symbol=symbolname]
21 [--globalize-symbol=symbolname]
22 [-W symbolname|--weaken-symbol=symbolname]
23 [-w|--wildcard]
24 [-x|--discard-all]
25 [-X|--discard-locals]
26 [-b byte|--byte=byte]
27 [-i [breadth]|--interleave[=breadth]]
28 [--interleave-width=width]
29 [-j sectionname|--only-section=sectionname]
30 [-R sectionname|--remove-section=sectionname]
31 [-p|--preserve-dates]
32 [--debugging]
33 [--gap-fill=val]
34 [--pad-to=address]
35 [--set-start=val]
36 [--adjust-start=incr]
37 [--change-addresses=incr]
38 [--change-section-address section{=,+,-}val]
39 [--change-section-lma section{=,+,-}val]
40 [--change-section-vma section{=,+,-}val]
41 [--change-warnings] [--no-change-warnings]
42 [--set-section-flags section=flags]
43 [--add-section sectionname=filename]
44 [--rename-section oldname=newname[,flags]]
45 [--long-section-names {enable,disable,keep}]
46 [--change-leading-char] [--remove-leading-char]
47 [--reverse-bytes=num]
48 [--srec-len=ival] [--srec-forceS3]
49 [--redefine-sym old=new]
50 [--redefine-syms=filename]
51 [--weaken]
52 [--keep-symbols=filename]
53 [--strip-symbols=filename]
54 [--strip-unneeded-symbols=filename]
55 [--keep-global-symbols=filename]
56 [--localize-symbols=filename]
57 [--globalize-symbols=filename]
58 [--weaken-symbols=filename]
59 [--alt-machine-code=index]
60 [--prefix-symbols=string]
61 [--prefix-sections=string]
62 [--prefix-alloc-sections=string]
63 [--add-gnu-debuglink=path-to-file]
64 [--keep-file-symbols]
65 [--only-keep-debug]
66 [--extract-symbol]
67 [--writable-text]
68 [--readonly-text]
69 [--pure]
70 [--impure]
71 [--file-alignment=num]
72 [--heap=size]
73 [--image-base=address]
74 [--section-alignment=num]
75 [--stack=size]
76 [--subsystem=which:major.minor]
77 [--compress-debug-sections]
78 [--decompress-debug-sections]
79 [-v|--verbose]
80 [-V|--version]
81 [--help] [--info]
82 infile [outfile]
83
85 The GNU objcopy utility copies the contents of an object file to
86 another. objcopy uses the GNU BFD Library to read and write the object
87 files. It can write the destination object file in a format different
88 from that of the source object file. The exact behavior of objcopy is
89 controlled by command-line options. Note that objcopy should be able
90 to copy a fully linked file between any two formats. However, copying a
91 relocatable object file between any two formats may not work as
92 expected.
93 objcopy creates temporary files to do its translations and deletes them
95 afterward. objcopy uses BFD to do all its translation work; it has
96 access to all the formats described in BFD and thus is able to
97 recognize most formats without being told explicitly.
98 objcopy can be used to generate S-records by using an output target of
100 srec (e.g., use -O srec).
101 objcopy can be used to generate a raw binary file by using an output
103 target of binary (e.g., use -O binary). When objcopy generates a raw
104 binary file, it will essentially produce a memory dump of the contents
105 of the input object file. All symbols and relocation information will
106 be discarded. The memory dump will start at the load address of the
107 lowest section copied into the output file.
108 When generating an S-record or a raw binary file, it may be helpful to
110 use -S to remove sections containing debugging information. In some
111 cases -R will be useful to remove sections which contain information
112 that is not needed by the binary file.
113 Note---objcopy is not able to change the endianness of its input files.
115 If the input format has an endianness (some formats do not), objcopy
116 can only copy the inputs into file formats that have the same
117 endianness or which have no endianness (e.g., srec). (However, see the
118 --reverse-bytes option.)
119
121 infile
122 outfile
123 The input and output files, respectively. If you do not specify
124 outfile, objcopy creates a temporary file and destructively renames
125 the result with the name of infile.
126 -I bfdname
128 --input-target=bfdname
129 Consider the source file's object format to be bfdname, rather than
130 attempting to deduce it.
131 -O bfdname
133 --output-target=bfdname
134 Write the output file using the object format bfdname.
135 -F bfdname
137 --target=bfdname
138 Use bfdname as the object format for both the input and the output
139 file; i.e., simply transfer data from source to destination with no
140 translation.
141 -B bfdarch
143 --binary-architecture=bfdarch
144 Useful when transforming a architecture-less input file into an
145 object file. In this case the output architecture can be set to
146 bfdarch. This option will be ignored if the input file has a known
147 bfdarch. You can access this binary data inside a program by
148 referencing the special symbols that are created by the conversion
149 process. These symbols are called _binary_objfile_start,
150 _binary_objfile_end and _binary_objfile_size. e.g. you can
151 transform a picture file into an object file and then access it in
152 your code using these symbols.
153 -j sectionname
155 --only-section=sectionname
156 Copy only the named section from the input file to the output file.
157 This option may be given more than once. Note that using this
158 option inappropriately may make the output file unusable.
159 -R sectionname
161 --remove-section=sectionname
162 Remove any section named sectionname from the output file. This
163 option may be given more than once. Note that using this option
164 inappropriately may make the output file unusable.
165 -S
167 --strip-all
168 Do not copy relocation and symbol information from the source file.
169 -g
171 --strip-debug
172 Do not copy debugging symbols or sections from the source file.
173 --strip-unneeded
175 Strip all symbols that are not needed for relocation processing.
176 -K symbolname
178 --keep-symbol=symbolname
179 When stripping symbols, keep symbol symbolname even if it would
180 normally be stripped. This option may be given more than once.
181 -N symbolname
183 --strip-symbol=symbolname
184 Do not copy symbol symbolname from the source file. This option
185 may be given more than once.
186 --strip-unneeded-symbol=symbolname
188 Do not copy symbol symbolname from the source file unless it is
189 needed by a relocation. This option may be given more than once.
190 -G symbolname
192 --keep-global-symbol=symbolname
193 Keep only symbol symbolname global. Make all other symbols local
194 to the file, so that they are not visible externally. This option
195 may be given more than once.
196 --localize-hidden
198 In an ELF object, mark all symbols that have hidden or internal
199 visibility as local. This option applies on top of symbol-specific
200 localization options such as -L.
201 -L symbolname
203 --localize-symbol=symbolname
204 Make symbol symbolname local to the file, so that it is not visible
205 externally. This option may be given more than once.
206 -W symbolname
208 --weaken-symbol=symbolname
209 Make symbol symbolname weak. This option may be given more than
210 once.
211 --globalize-symbol=symbolname
213 Give symbol symbolname global scoping so that it is visible outside
214 of the file in which it is defined. This option may be given more
215 than once.
216 -w
218 --wildcard
219 Permit regular expressions in symbolnames used in other command
220 line options. The question mark (?), asterisk (*), backslash (\)
221 and square brackets ([]) operators can be used anywhere in the
222 symbol name. If the first character of the symbol name is the
223 exclamation point (!) then the sense of the switch is reversed for
224 that symbol. For example:
225 -w -W !foo -W fo*
227 would cause objcopy to weaken all symbols that start with "fo"
229 except for the symbol "foo".
230 -x
232 --discard-all
233 Do not copy non-global symbols from the source file.
234 -X
236 --discard-locals
237 Do not copy compiler-generated local symbols. (These usually start
238 with L or ..)
239 -b byte
241 --byte=byte
242 If interleaving has been enabled via the --interleave option then
243 start the range of bytes to keep at the byteth byte. byte can be
244 in the range from 0 to breadth-1, where breadth is the value given
245 by the --interleave option.
246 -i [breadth]
248 --interleave[=breadth]
249 Only copy a range out of every breadth bytes. (Header data is not
250 affected). Select which byte in the range begins the copy with the
251 --byte option. Select the width of the range with the
252 --interleave-width option.
253 This option is useful for creating files to program ROM. It is
255 typically used with an "srec" output target. Note that objcopy
256 will complain if you do not specify the --byte option as well.
257 The default interleave breadth is 4, so with --byte set to 0,
259 objcopy would copy the first byte out of every four bytes from the
260 input to the output.
261 --interleave-width=width
263 When used with the --interleave option, copy width bytes at a time.
264 The start of the range of bytes to be copied is set by the --byte
265 option, and the extent of the range is set with the --interleave
266 option.
267 The default value for this option is 1. The value of width plus
269 the byte value set by the --byte option must not exceed the
270 interleave breadth set by the --interleave option.
271 This option can be used to create images for two 16-bit flashes
273 interleaved in a 32-bit bus by passing -b 0 -i 4
274 --interleave-width=2 and -b 2 -i 4 --interleave-width=2 to two
275 objcopy commands. If the input was '12345678' then the outputs
276 would be '1256' and '3478' respectively.
277 -p
279 --preserve-dates
280 Set the access and modification dates of the output file to be the
281 same as those of the input file.
282 --debugging
284 Convert debugging information, if possible. This is not the
285 default because only certain debugging formats are supported, and
286 the conversion process can be time consuming.
287 --gap-fill val
289 Fill gaps between sections with val. This operation applies to the
290 load address (LMA) of the sections. It is done by increasing the
291 size of the section with the lower address, and filling in the
292 extra space created with val.
293 --pad-to address
295 Pad the output file up to the load address address. This is done
296 by increasing the size of the last section. The extra space is
297 filled in with the value specified by --gap-fill (default zero).
298 --set-start val
300 Set the start address of the new file to val. Not all object file
301 formats support setting the start address.
302 --change-start incr
304 --adjust-start incr
305 Change the start address by adding incr. Not all object file
306 formats support setting the start address.
307 --change-addresses incr
309 --adjust-vma incr
310 Change the VMA and LMA addresses of all sections, as well as the
311 start address, by adding incr. Some object file formats do not
312 permit section addresses to be changed arbitrarily. Note that this
313 does not relocate the sections; if the program expects sections to
314 be loaded at a certain address, and this option is used to change
315 the sections such that they are loaded at a different address, the
316 program may fail.
317 --change-section-address section{=,+,-}val
319 --adjust-section-vma section{=,+,-}val
320 Set or change both the VMA address and the LMA address of the named
321 section. If = is used, the section address is set to val.
322 Otherwise, val is added to or subtracted from the section address.
323 See the comments under --change-addresses, above. If section does
324 not exist in the input file, a warning will be issued, unless
325 --no-change-warnings is used.
326 --change-section-lma section{=,+,-}val
328 Set or change the LMA address of the named section. The LMA
329 address is the address where the section will be loaded into memory
330 at program load time. Normally this is the same as the VMA
331 address, which is the address of the section at program run time,
332 but on some systems, especially those where a program is held in
333 ROM, the two can be different. If = is used, the section address
334 is set to val. Otherwise, val is added to or subtracted from the
335 section address. See the comments under --change-addresses, above.
336 If section does not exist in the input file, a warning will be
337 issued, unless --no-change-warnings is used.
338 --change-section-vma section{=,+,-}val
340 Set or change the VMA address of the named section. The VMA
341 address is the address where the section will be located once the
342 program has started executing. Normally this is the same as the
343 LMA address, which is the address where the section will be loaded
344 into memory, but on some systems, especially those where a program
345 is held in ROM, the two can be different. If = is used, the
346 section address is set to val. Otherwise, val is added to or
347 subtracted from the section address. See the comments under
348 --change-addresses, above. If section does not exist in the input
349 file, a warning will be issued, unless --no-change-warnings is
350 used.
351 --change-warnings
353 --adjust-warnings
354 If --change-section-address or --change-section-lma or
355 --change-section-vma is used, and the named section does not exist,
356 issue a warning. This is the default.
357 --no-change-warnings
359 --no-adjust-warnings
360 Do not issue a warning if --change-section-address or
361 --adjust-section-lma or --adjust-section-vma is used, even if the
362 named section does not exist.
363 --set-section-flags section=flags
365 Set the flags for the named section. The flags argument is a comma
366 separated string of flag names. The recognized names are alloc,
367 contents, load, noload, readonly, code, data, rom, share, and
368 debug. You can set the contents flag for a section which does not
369 have contents, but it is not meaningful to clear the contents flag
370 of a section which does have contents--just remove the section
371 instead. Not all flags are meaningful for all object file formats.
372 --add-section sectionname=filename
374 Add a new section named sectionname while copying the file. The
375 contents of the new section are taken from the file filename. The
376 size of the section will be the size of the file. This option only
377 works on file formats which can support sections with arbitrary
378 names.
379 --rename-section oldname=newname[,flags]
381 Rename a section from oldname to newname, optionally changing the
382 section's flags to flags in the process. This has the advantage
383 over usng a linker script to perform the rename in that the output
384 stays as an object file and does not become a linked executable.
385 This option is particularly helpful when the input format is
387 binary, since this will always create a section called .data. If
388 for example, you wanted instead to create a section called .rodata
389 containing binary data you could use the following command line to
390 achieve it:
391 objcopy -I binary -O <output_format> -B <architecture> \
393 --rename-section .data=.rodata,alloc,load,readonly,data,contents \
394 <input_binary_file> <output_object_file>
395 --long-section-names {enable,disable,keep}
397 Controls the handling of long section names when processing "COFF"
398 and "PE-COFF" object formats. The default behaviour, keep, is to
399 preserve long section names if any are present in the input file.
400 The enable and disable options forcibly enable or disable the use
401 of long section names in the output object; when disable is in
402 effect, any long section names in the input object will be
403 truncated. The enable option will only emit long section names if
404 any are present in the inputs; this is mostly the same as keep, but
405 it is left undefined whether the enable option might force the
406 creation of an empty string table in the output file.
407 --change-leading-char
409 Some object file formats use special characters at the start of
410 symbols. The most common such character is underscore, which
411 compilers often add before every symbol. This option tells objcopy
412 to change the leading character of every symbol when it converts
413 between object file formats. If the object file formats use the
414 same leading character, this option has no effect. Otherwise, it
415 will add a character, or remove a character, or change a character,
416 as appropriate.
417 --remove-leading-char
419 If the first character of a global symbol is a special symbol
420 leading character used by the object file format, remove the
421 character. The most common symbol leading character is underscore.
422 This option will remove a leading underscore from all global
423 symbols. This can be useful if you want to link together objects
424 of different file formats with different conventions for symbol
425 names. This is different from --change-leading-char because it
426 always changes the symbol name when appropriate, regardless of the
427 object file format of the output file.
428 --reverse-bytes=num
430 Reverse the bytes in a section with output contents. A section
431 length must be evenly divisible by the value given in order for the
432 swap to be able to take place. Reversing takes place before the
433 interleaving is performed.
434 This option is used typically in generating ROM images for
436 problematic target systems. For example, on some target boards,
437 the 32-bit words fetched from 8-bit ROMs are re-assembled in
438 little-endian byte order regardless of the CPU byte order.
439 Depending on the programming model, the endianness of the ROM may
440 need to be modified.
441 Consider a simple file with a section containing the following
443 eight bytes: 12345678.
444 Using --reverse-bytes=2 for the above example, the bytes in the
446 output file would be ordered 21436587.
447 Using --reverse-bytes=4 for the above example, the bytes in the
449 output file would be ordered 43218765.
450 By using --reverse-bytes=2 for the above example, followed by
452 --reverse-bytes=4 on the output file, the bytes in the second
453 output file would be ordered 34127856.
454 --srec-len=ival
456 Meaningful only for srec output. Set the maximum length of the
457 Srecords being produced to ival. This length covers both address,
458 data and crc fields.
459 --srec-forceS3
461 Meaningful only for srec output. Avoid generation of S1/S2
462 records, creating S3-only record format.
463 --redefine-sym old=new
465 Change the name of a symbol old, to new. This can be useful when
466 one is trying link two things together for which you have no
467 source, and there are name collisions.
468 --redefine-syms=filename
470 Apply --redefine-sym to each symbol pair "old new" listed in the
471 file filename. filename is simply a flat file, with one symbol
472 pair per line. Line comments may be introduced by the hash
473 character. This option may be given more than once.
474 --weaken
476 Change all global symbols in the file to be weak. This can be
477 useful when building an object which will be linked against other
478 objects using the -R option to the linker. This option is only
479 effective when using an object file format which supports weak
480 symbols.
481 --keep-symbols=filename
483 Apply --keep-symbol option to each symbol listed in the file
484 filename. filename is simply a flat file, with one symbol name per
485 line. Line comments may be introduced by the hash character. This
486 option may be given more than once.
487 --strip-symbols=filename
489 Apply --strip-symbol option to each symbol listed in the file
490 filename. filename is simply a flat file, with one symbol name per
491 line. Line comments may be introduced by the hash character. This
492 option may be given more than once.
493 --strip-unneeded-symbols=filename
495 Apply --strip-unneeded-symbol option to each symbol listed in the
496 file filename. filename is simply a flat file, with one symbol
497 name per line. Line comments may be introduced by the hash
498 character. This option may be given more than once.
499 --keep-global-symbols=filename
501 Apply --keep-global-symbol option to each symbol listed in the file
502 filename. filename is simply a flat file, with one symbol name per
503 line. Line comments may be introduced by the hash character. This
504 option may be given more than once.
505 --localize-symbols=filename
507 Apply --localize-symbol option to each symbol listed in the file
508 filename. filename is simply a flat file, with one symbol name per
509 line. Line comments may be introduced by the hash character. This
510 option may be given more than once.
511 --globalize-symbols=filename
513 Apply --globalize-symbol option to each symbol listed in the file
514 filename. filename is simply a flat file, with one symbol name per
515 line. Line comments may be introduced by the hash character. This
516 option may be given more than once.
517 --weaken-symbols=filename
519 Apply --weaken-symbol option to each symbol listed in the file
520 filename. filename is simply a flat file, with one symbol name per
521 line. Line comments may be introduced by the hash character. This
522 option may be given more than once.
523 --alt-machine-code=index
525 If the output architecture has alternate machine codes, use the
526 indexth code instead of the default one. This is useful in case a
527 machine is assigned an official code and the tool-chain adopts the
528 new code, but other applications still depend on the original code
529 being used. For ELF based architectures if the index alternative
530 does not exist then the value is treated as an absolute number to
531 be stored in the e_machine field of the ELF header.
532 --writable-text
534 Mark the output text as writable. This option isn't meaningful for
535 all object file formats.
536 --readonly-text
538 Make the output text write protected. This option isn't meaningful
539 for all object file formats.
540 --pure
542 Mark the output file as demand paged. This option isn't meaningful
543 for all object file formats.
544 --impure
546 Mark the output file as impure. This option isn't meaningful for
547 all object file formats.
548 --prefix-symbols=string
550 Prefix all symbols in the output file with string.
551 --prefix-sections=string
553 Prefix all section names in the output file with string.
554 --prefix-alloc-sections=string
556 Prefix all the names of all allocated sections in the output file
557 with string.
558 --add-gnu-debuglink=path-to-file
560 Creates a .gnu_debuglink section which contains a reference to
561 path-to-file and adds it to the output file.
562 --keep-file-symbols
564 When stripping a file, perhaps with --strip-debug or
565 --strip-unneeded, retain any symbols specifying source file names,
566 which would otherwise get stripped.
567 --only-keep-debug
569 Strip a file, removing contents of any sections that would not be
570 stripped by --strip-debug and leaving the debugging sections
571 intact. In ELF files, this preserves all note sections in the
572 output.
573 The intention is that this option will be used in conjunction with
575 --add-gnu-debuglink to create a two part executable. One a
576 stripped binary which will occupy less space in RAM and in a
577 distribution and the second a debugging information file which is
578 only needed if debugging abilities are required. The suggested
579 procedure to create these files is as follows:
580 1.<Link the executable as normal. Assuming that is is called>
582 "foo" then...
583 1.<Run "objcopy --only-keep-debug foo foo.dbg" to>
585 create a file containing the debugging info.
586 1.<Run "objcopy --strip-debug foo" to create a>
588 stripped executable.
589 1.<Run "objcopy --add-gnu-debuglink=foo.dbg foo">
591 to add a link to the debugging info into the stripped
592 executable.
593 Note---the choice of ".dbg" as an extension for the debug info file
595 is arbitrary. Also the "--only-keep-debug" step is optional. You
596 could instead do this:
597 1.<Link the executable as normal.>
599 1.<Copy "foo" to "foo.full">
600 1.<Run "objcopy --strip-debug foo">
601 1.<Run "objcopy --add-gnu-debuglink=foo.full foo">
602 i.e., the file pointed to by the --add-gnu-debuglink can be the
604 full executable. It does not have to be a file created by the
605 --only-keep-debug switch.
606 Note---this switch is only intended for use on fully linked files.
608 It does not make sense to use it on object files where the
609 debugging information may be incomplete. Besides the gnu_debuglink
610 feature currently only supports the presence of one filename
611 containing debugging information, not multiple filenames on a one-
612 per-object-file basis.
613 --file-alignment num
615 Specify the file alignment. Sections in the file will always begin
616 at file offsets which are multiples of this number. This defaults
617 to 512. [This option is specific to PE targets.]
618 --heap reserve
620 --heap reserve,commit
621 Specify the number of bytes of memory to reserve (and optionally
622 commit) to be used as heap for this program. [This option is
623 specific to PE targets.]
624 --image-base value
626 Use value as the base address of your program or dll. This is the
627 lowest memory location that will be used when your program or dll
628 is loaded. To reduce the need to relocate and improve performance
629 of your dlls, each should have a unique base address and not
630 overlap any other dlls. The default is 0x400000 for executables,
631 and 0x10000000 for dlls. [This option is specific to PE targets.]
632 --section-alignment num
634 Sets the section alignment. Sections in memory will always begin
635 at addresses which are a multiple of this number. Defaults to
636 0x1000. [This option is specific to PE targets.]
637 --stack reserve
639 --stack reserve,commit
640 Specify the number of bytes of memory to reserve (and optionally
641 commit) to be used as stack for this program. [This option is
642 specific to PE targets.]
643 --subsystem which
645 --subsystem which:major
646 --subsystem which:major.minor
647 Specifies the subsystem under which your program will execute. The
648 legal values for which are "native", "windows", "console", "posix",
649 "efi-app", "efi-bsd", "efi-rtd", "sal-rtd", and "xbox". You may
650 optionally set the subsystem version also. Numeric values are also
651 accepted for which. [This option is specific to PE targets.]
652 --extract-symbol
654 Keep the file's section flags and symbols but remove all section
655 data. Specifically, the option:
656 *<removes the contents of all sections;>
658 *<sets the size of every section to zero; and>
659 *<sets the file's start address to zero.>
660 This option is used to build a .sym file for a VxWorks kernel. It
662 can also be a useful way of reducing the size of a --just-symbols
663 linker input file.
664 --compress-debug-sections
666 Compress DWARF debug sections using zlib.
667 --decompress-debug-sections
669 Decompress DWARF debug sections using zlib.
670 -V
672 --version
673 Show the version number of objcopy.
674 -v
676 --verbose
677 Verbose output: list all object files modified. In the case of
678 archives, objcopy -V lists all members of the archive.
679 --help
681 Show a summary of the options to objcopy.
682 --info
684 Display a list showing all architectures and object formats
685 available.
686 @file
688 Read command-line options from file. The options read are inserted
689 in place of the original @file option. If file does not exist, or
690 cannot be read, then the option will be treated literally, and not
691 removed.
692 Options in file are separated by whitespace. A whitespace
694 character may be included in an option by surrounding the entire
695 option in either single or double quotes. Any character (including
696 a backslash) may be included by prefixing the character to be
697 included with a backslash. The file may itself contain additional
698 @file options; any such options will be processed recursively.
699
701 ld(1), objdump(1), and the Info entries for binutils.
702
704 Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
705 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free
706 Software Foundation, Inc.
707 Permission is granted to copy, distribute and/or modify this document
709 under the terms of the GNU Free Documentation License, Version 1.3 or
710 any later version published by the Free Software Foundation; with no
711 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
712 Texts. A copy of the license is included in the section entitled "GNU
713 Free Documentation License".
714binutils-2.21 2010-12-08 OBJCOPY(1)