This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
[RFA:] Update docs about ld -r format restrictions
- To: binutils at sources dot redhat dot com
- Subject: [RFA:] Update docs about ld -r format restrictions
- From: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Date: Wed, 20 Jun 2001 00:32:35 +0200
Here's an update to the documentation for what we painstakingly changed
back and forth recently. ;-)
BTW, I really think bfdint.texi deserves to be built and installed by
default; it shouldn't be hidden the way it is now.
Ok to commit?
ld:
* ld.texinfo (Options) <-r>: Mention restrictions when using
different object formats.
bfd/doc:
* bfdint.texi (BFD relocation functions) <different formats>:
Mention that the GNU linker is aware of input-output format
restrictions when generating relocatable output. Make new
paragraph for final-link case.
Index: ld.texinfo
===================================================================
RCS file: /cvs/src/src/ld/ld.texinfo,v
retrieving revision 1.40
diff -p -c -r1.40 ld.texinfo
*** ld.texinfo 2001/06/19 15:22:39 1.40
--- ld.texinfo 2001/06/19 20:49:12
*************** END-INFO-DIR-ENTRY
*** 52,58 ****
@ifinfo
This file documents the @sc{gnu} linker LD version @value{VERSION}.
! Copyright (C) 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software Foundation, Inc.
@ignore
--- 52,59 ----
@ifinfo
This file documents the @sc{gnu} linker LD version @value{VERSION}.
! Copyright (C) 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000,
! 2001 Free Software Foundation, Inc.
@ignore
*************** magic numbers, this option also sets the
*** 700,705 ****
--- 701,712 ----
If this option is not specified, an absolute file is produced. When
linking C++ programs, this option @emph{will not} resolve references to
constructors; to do that, use @samp{-Ur}.
+
+ When an input file does not have the same format as the output file,
+ partial linking is only supported if that input file does not contain any
+ relocations. Different output formats can have further restrictions; for
+ example some @code{a.out}-based formats do not support partial linking
+ with input files in other formats at all.
This option does the same thing as @samp{-i}.
Index: bfdint.texi
===================================================================
RCS file: /cvs/src/src/bfd/doc/bfdint.texi,v
retrieving revision 1.8
diff -p -c -r1.8 bfdint.texi
*** bfdint.texi 2001/05/23 08:23:27 1.8
--- bfdint.texi 2001/06/19 22:16:02
*************** doing a link in which the output object
*** 1291,1300 ****
@item
Using the linker to generate relocateable output in a different object
file format is impossible in the general case, so you generally don't
! have to worry about that. Linking input files of different object file
! formats together is quite unusual, but if you're really dedicated you
! may want to consider testing this case, both when the output object file
! format is the same as your format, and when it is different.
@end itemize
@node BFD relocation codes
--- 1291,1303 ----
@item
Using the linker to generate relocateable output in a different object
file format is impossible in the general case, so you generally don't
! have to worry about that. The GNU linker makes sure to stop that from
! happening when an input file in a different format has relocations.
!
! Linking input files of different object file formats together is quite
! unusual, but if you're really dedicated you may want to consider testing
! this case, both when the output object file format is the same as your
! format, and when it is different.
@end itemize
@node BFD relocation codes
brgds, H-P