Change 25459 by [EMAIL PROTECTED] on 2005/09/18 10:12:51
Controlling what the GNU linker exports from a shared library would
be a useful thing TODO
Affected files ...
... //depot/perl/pod/perltodo.pod#114 edit
Differences ...
==== //depot/perl/pod/perltodo.pod#114 (text) ====
Index: perl/pod/perltodo.pod
--- perl/pod/perltodo.pod#113~25457~ Sun Sep 18 02:38:59 2005
+++ perl/pod/perltodo.pod Sun Sep 18 03:12:51 2005
@@ -245,6 +245,18 @@
It would be good if someone were able to track down the causes of these
problems, so that parallel builds worked properly.
+=head2 linker specification files
+
+Some platforms mandate that you provide a list of a shared library's external
+symbols to the linker, so the core already has the infrastructure in place to
+do this for generating shared perl libraries. My understanding is that the
+GNU toolchain can accept an optional linker specification file, and restrict
+visibility just to symbols declared in that file. It would be good to extend
+F<makedef.pl> to support this format, and to provide a means within
+C<Configure> to enable it. This would allow Unix users to test that the
+export list is correct, and to build a perl that does not pollute the global
+namespace with private symbols.
+
End of Patch.
