darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

2001-06-19 H.J. Lu <hjl@gnu.org>

Browse source 
* ld.texinfo (-E, --export-dynamic): Mention --version-script.
	(--version-script): Mention the language support.
This commit is contained in:
H.J. Lu 2001-06-19 15:22:39 +00:00
parent 9bf03accc3
commit cb840a31ad
2 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ld/ChangeLog
View file

@ -1,3 +1,8 @@
2001-06-19 H.J. Lu <hjl@gnu.org>
* ld.texinfo (-E, --export-dynamic): Mention --version-script.
(--version-script): Mention the language support.
2001-06-19 H.J. Lu <hjl@gnu.org>
* ldlang.c (lang_check): Revert the change mode on 2001-06-15.

15
ld/ld.texinfo
View file

@ -444,6 +444,10 @@ back to the symbols defined by the program, rather than some other
dynamic object, then you will probably need to use this option when
linking the program itself.
You can also use the version script to control what symbols should
be added to the dynamic symbol table if the output format supports it.
See the description of @samp{--version-script} in @ref{VERSION}.
@cindex big-endian objects
@cindex endianness
@kindex -EB
@ -3537,6 +3541,17 @@ within the shared library, you can use the aliases of convenience
(i.e. @samp{old_foo}), or you can use the @samp{.symver} directive to
specifically bind to an external version of the function in question.
You can also specify the language in the version script:
@smallexample
VERSION extern "lang" @{ version-script-commands @}
@end smallexample
The supported @samp{lang}s are @samp{C}, @samp{C++}, and @samp{Java}.
The linker will iterate over the list of symbols at the link time and
demangle them according to @samp{lang} before matching them to the
patterns specified in @samp{version-script-commands}.
@node Expressions
@section Expressions in Linker Scripts
@cindex expressions