aboutsummaryrefslogtreecommitdiff
path: root/ld
diff options
context:
space:
mode:
authorIan Lance Taylor <ian@airs.com>1998-04-03 17:55:04 +0000
committerIan Lance Taylor <ian@airs.com>1998-04-03 17:55:04 +0000
commitf8cf2baa85e03844b0411d11faa57ac748b4a999 (patch)
treed2f22d8fd48ca50723ea7a216e38136ab18fd567 /ld
parent72a08ce565ebcc1e71ec20055dc1ae585f58532c (diff)
downloadgdb-f8cf2baa85e03844b0411d11faa57ac748b4a999.zip
gdb-f8cf2baa85e03844b0411d11faa57ac748b4a999.tar.gz
gdb-f8cf2baa85e03844b0411d11faa57ac748b4a999.tar.bz2
tweak
Diffstat (limited to 'ld')
-rw-r--r--ld/ld.texinfo29
1 files changed, 21 insertions, 8 deletions
diff --git a/ld/ld.texinfo b/ld/ld.texinfo
index 5acea12..3c5de96 100644
--- a/ld/ld.texinfo
+++ b/ld/ld.texinfo
@@ -1293,14 +1293,8 @@ line option. When you do this, your linker script will replace the
default linker script.
You may also use linker scripts implicitly by naming them as input files
-to the linker, as though they were files to be linked. If the linker
-opens a file which it can not recognize as an object file or as an
-archive file, it will try to read it as a linker script. If the file
-can not be parsed as a linker script, the linker will report an error.
-
-An implicit linker script will not replace the default linker script.
-Typically an implicit linker script would contain only the @code{INPUT},
-@code{GROUP}, or @code{VERSION} commands.
+to the linker, as though they were files to be linked. @xref{Implicit
+Linker Scripts}.
@menu
* Basic Script Concepts:: Basic Linker Script Concepts
@@ -1313,6 +1307,7 @@ Typically an implicit linker script would contain only the @code{INPUT},
* PHDRS:: PHDRS Command
* VERSION:: VERSION Command
* Expressions:: Expressions in Linker Scripts
+* Implicit Linker Scripts:: Implicit Linker Scripts
@end menu
@node Basic Script Concepts
@@ -3431,6 +3426,24 @@ you must define the program headers yourself using the @code{PHDRS}
command (@pxref{PHDRS}).
@end table
+@node Implicit Linker Scripts
+@section Implicit Linker Scripts
+@cindex implicit linker scripts
+If you specify a linker input file which the linker can not recognize as
+an object file or an archive file, it will try to read the file as a
+linker script. If the file can not be parsed as a linker script, the
+linker will report an error.
+
+An implicit linker script will not replace the default linker script.
+
+Typically an implicit linker script would contain only symbol
+assignments, or the @code{INPUT}, @code{GROUP}, or @code{VERSION}
+commands.
+
+Any input files read because of an implicit linker script will be read
+at the position in the command line where the implicit linker script was
+read. This can affect archive searching.
+
@ifset GENERIC
@node Machine Dependent
@chapter Machine Dependent Features