Python.so

It’s incredible we need shared library and you provide static version
for the mostly provided products!

Is it possible to get it somewhere?

Alain.

Alain Bonnefoy wrote:

It’s incredible we need shared library and you provide static version
for the mostly provided products!

Is it possible to get it somewhere?

If you mean the Python-2.0 version downloadable from TUCOWS, that
version is the base version of Python … it includes just thread
support, no support of IDLE, Tkinter a.s.o.

I have tried to build a shared lib version of Python-2.1 … but it
was a nigthmare and it ended up again with a static linked version
:frowning:

BTW, the version 2.1 compiles absolutely flawless. If you have the
time … try to build a shared library version :slight_smile:

Armin

Armin Steinhoff a écrit :

Alain Bonnefoy wrote:

It’s incredible we need shared library and you provide static version
for the mostly provided products!

Is it possible to get it somewhere?

If you mean the Python-2.0 version downloadable from TUCOWS, that
version is the base version of Python … it includes just thread
support, no support of IDLE, Tkinter a.s.o.

I have tried to build a shared lib version of Python-2.1 … but it
was a nigthmare and it ended up again with a static linked version
:frowning:

BTW, the version 2.1 compiles absolutely flawless. If you have the
time … try to build a shared library version > :slight_smile:

Armin

I tried but I stopped!
Alain.

“Armin Steinhoff” <A-Steinhoff@web_.de> wrote in message
news:3B03D865.B3D836CB@web_.de…

Alain Bonnefoy wrote:

It’s incredible we need shared library and you provide static version
for the mostly provided products!

Is it possible to get it somewhere?

If you mean the Python-2.0 version downloadable from TUCOWS, that
version is the base version of Python … it includes just thread
support, no support of IDLE, Tkinter a.s.o.

I have tried to build a shared lib version of Python-2.1 … but it
was a nigthmare and it ended up again with a static linked version
:frowning:

BTW, the version 2.1 compiles absolutely flawless. If you have the
time … try to build a shared library version > :slight_smile:

Armin

I’m trying (2nd night at trying now) to get python 2.1 compiled in shared
library mode.

I’ve got it to compile (like you said no problems there) and I think I
have all the
shared linker and compiler flags turned on. However, after it compiles
everything
including all the modules, I try to do a ‘make test’ and it core dumps on
the very
first test.

I’ve tracked it down to when python tries to import a module so I’m thinking
the shared library stuff isn’t working. I used these flags (all changes
were made
in the configure script):

~Line 2943, Added (for the LDSHARED setup)
QNX*/6*) LDSHARED=“qcc -shared”;;

~Line 2990, Added (for the CCSHARED setup)
QNX*/6*) CCSHARED="-shared";;

~Line 3026, Added (for the LINKFORSHARED setup)
QNX*/6*) LINKFORSHARED="-Xlinker -export-dynamic";;

I figured these out through trial and error, but something is still wrong
with one of
them, because I can’t load shared libraries in python without core dumping.

From the 2.1 neutrino docs it looks like the linker links dynamicaly by
default so there
may not be a need for that last option I put in (LINKFORSHARED). I’m almost
positive (well 50% anyway hehe) the LDSHARED option is right, along with the
CCSHARED option. I could however be missing an option too.

With those options it will compile and link fine, it just can’t load dynamic
libs. Hopefully
someone can point out what I am doing wrong here.

Shane Warren