Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 40f7a55608a1caf8966ae2fdcf3b140bbb6b98f9 authored by Guido van Rossum on 24 October 1996, 18:34:36 UTC, committed by Guido van Rossum on 24 October 1996, 18:34:36 UTC 
Get rid of bogus binding of <Delete> to a function that deletes the next
 
character (this is already a built-in binding now).
1 parent a5a4c2a
Raw File
Tip revision: 40f7a55608a1caf8966ae2fdcf3b140bbb6b98f9 authored by Guido van Rossum on 24 October 1996, 18:34:36 UTC
Get rid of bogus binding of <Delete> to a function that deletes the next
Tip revision: 40f7a55
HPUX-NOTES 
Subject: Dynamic Linking under HP-UX
From: "C. Derek Fields" <derek@gamekeeper.bellcore.com>
Date: Thu, 08 Sep 94 14:14:07 -0400

There are two important points.  First, the python executable must be
linked with the -E option to explicitly export all symbols.  This
works with the vanilla interpreter, but I am not sure how friendly it
will be when I try to embed the interpreter in a larger application.
It may be necessary to hand tune the exports using the -e option.
Anyway, the additional flag to $(CC) is "-Wl,-E", which passes the -E
flag to the compiler.  My link line (from an actual run) looks like
this:

cc config.o -Wl,-E libModules.a  ../Python/libPython.a  ../Objects/libObjects.a ../Parser/libParser.a   -lm  -ldld -o python

Second, the dynamic module must be compiled with the +z option to make
it position independent and then linked into a shared library:

ld -b -o <modName>module.sl <object list>

The -b tells the linker to produce a shared library.
back to top