Python2.0 beta 2 on MacOSX/Darwin
Martin von Loewis
loewis at informatik.hu-berlin.de
Sun Oct 1 05:22:22 EDT 2000
Johann Hibschman <johann at physics.berkeley.edu> writes:
> Yes, I've been getting this same error. If anyone has any idea how to
> get around this, I'd appreciate any information. Python's not doing
> me much good if I have to statically link all my extensions
I've been studying quite a few mailing lists recently. I don't have
MacOS X myself, so I can't really try any of my theories.
A. You can suppress undefined symbols. So instead of linking with
'-bundle -prebind', try '-bundle -undefined suppress'. This is
what Apache 1.3 does to build its extension modules (there is
also conflicting information on -prebind - the linker of MacOS X
does not seem to like it for bundles).
B. An alternative is to link extension modules with the Python bundle.
It seems configure.in already has an option --with-next-framework,
which generates some files through libtool(1) (whatever that is),
and links these files into extension modules.
I don't know whether these approaches works, or, if they work both,
which is the right one. I'd appreciate if anybody with MacOS X could
try, though.
Regards,
Martin
More information about the Python-list
mailing list