From dcf9797836522e0728188fcd4b703f7bde69cf8c Mon Sep 17 00:00:00 2001 From: hjl Date: Wed, 27 Nov 2002 19:42:09 +0000 Subject: [PATCH] 2002-11-27 H.J. Lu * ld.texinfo: Add the missing `;' to sample version scripts. --- ld/ChangeLog | 4 ++++ ld/ld.texinfo | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/ld/ChangeLog b/ld/ChangeLog index 564633bdd9..5d654fbf08 100644 --- a/ld/ChangeLog +++ b/ld/ChangeLog @@ -1,3 +1,7 @@ +2002-11-27 H.J. Lu + + * ld.texinfo: Add the missing `;' to sample version scripts. + 2002-11-20 Alan Modra * emulparams/elf64ppc.sh (SEGMENT_SIZE): Don't define. diff --git a/ld/ld.texinfo b/ld/ld.texinfo index 03702dc6c7..961dead347 100644 --- a/ld/ld.texinfo +++ b/ld/ld.texinfo @@ -3743,7 +3743,7 @@ and @samp{bar2} are bound to the version node @samp{VERS_2.0}. When the linker finds a symbol defined in a library which is not specifically bound to a version node, it will effectively bind it to an unspecified base version of the library. You can bind all otherwise -unspecified symbols to a given version node by using @samp{global: *} +unspecified symbols to a given version node by using @samp{global: *;}; somewhere in the version script. The names of the version nodes have no specific meaning other than what @@ -3757,7 +3757,7 @@ symbols, only selects which symbols will be globally visible out and which won't. @smallexample -@{ global: foo; bar; local: *; @} +@{ global: foo; bar; local: *; @}; @end smallexample When you link an application against a shared library that has versioned -- 2.11.0