Hi,

This problem cost me very much time to solve:

After I build Python, all dynamic libraries got dynamically
linked into the Python interpreter (libraries like
zlib and tcl/tk stuff).

I coudn't find out why this is, I only want to load zlib.so
when I do a "import zlib" and not when I start Python.

And this is (I think) the difference between statically and
dynamically build Python libraries, but this isn't explaind
in a clear way.

You can configure the dynamic/static module beheviour in
the Modules/Setup file (afher you did a configure) with
the *shared* flag. 

The dinamic/static module behaviour should at least very
clear described in that file, this is not the case at
this moment.

Best regards,

Jan

Logged In: YES 
user_id=732192

Uuuh when I say "python library" I mean a "python module"

Logged In: YES 
user_id=21627

What do you mean when you say "all dynamic libraries got
dynamically linked into the Python interpreter"? If it means
what I understand it means (i.e. all libraries are passed to
the ld command creating the python binary), then this is not
supposed to happen.

Can you provide a make log to demonstrate this more clearly?

Logged In: YES 
user_id=732192

Hi,

When I build python with zlib and the commented shared flag
"#*shared*". then zlib.so is included in ./python (checked
with ldd ./python).

When I build python with zlib and the  *shared* flag commented
out then is zlib.so not part of the ./python program.

The question is now: is this the difference between shared and
static modules?

or

do I have so weird problem?

Logged In: YES 
user_id=21627

I cannot reproduce this. If I leave # *shared*, but enable
zlib in Modules/Setup, I get no file Modules/zlib.so, only
Modules/zlib.o. This is incorporated into python.

If I also leave zlib commented in Modules/Setup, zlib.so is
build through setup.py in build/lib-somewhere, *after*
python was linked.

Can you provide a complete build log?

Logged In: YES 
user_id=21627

Closing this because of lack of feedback.