Python2.2

QNX Newsgroups (Archives) qdn.public.qnxrtp.porting
1

Does anybody succeded to build the libpython2.2.so and the corresponding
python shell.
I get a ‘segmentation violation’ at start.

I’m a little bit confused with the ‘-fPIC’ flag because I first built
the tcl8.3 on 6.0 with this flag and I had to remove it on 6.1 in order
that wish run without a ‘segmentation violation’.

any idea?

Alain.

2

Alain Bonnefoy wrote:

Does anybody succeded to build the libpython2.2.so and the corresponding
python shell.

Yes … you can download it from http://www.sf.net/projects/PyQNX

I get a ‘segmentation violation’ at start.

I’m a little bit confused with the ‘-fPIC’ flag because I first built
the tcl8.3 on 6.0 with this flag and I had to remove it on 6.1 in order
that wish run without a ‘segmentation violation’.

My experience is that tcl8.3 works instable as a DLL version … so I
link
that stuff always statically with python.

Armin

any idea?

Alain.

3

Armin Steinhoff a écrit :

Alain Bonnefoy wrote:

Does anybody succeded to build the libpython2.2.so and the corresponding
python shell.

Yes … you can download it from > http://www.sf.net/projects/PyQNX

This link is unreachable!?
I tried to find it at sourceforge.net, I found some words about it but not the
project.

I don’t know if we have downloaded the wrong package but I got the
Python-2.2-qnx6.1.tar.gz and it only contains a libpython.2.2.a.
I’ve generated a .so from that static lib and relink python and I’m still
blocked on the ‘segmentation violation’.

I get a ‘segmentation violation’ at start.

I’m a little bit confused with the ‘-fPIC’ flag because I first built
the tcl8.3 on 6.0 with this flag and I had to remove it on 6.1 in order
that wish run without a ‘segmentation violation’.

My experience is that tcl8.3 works instable as a DLL version … so I
link
that stuff always statically with python.

Maybe it’s the reason why I get this message!

Armin

any idea?

Alain.

Thanks,
Alain.

4

Alain Bonnefoy wrote:

Armin Steinhoff a écrit :

Alain Bonnefoy wrote:

Does anybody succeded to build the libpython2.2.so and the corresponding
python shell.

Yes … you can download it from > http://www.sf.net/projects/PyQNX


This link is unreachable!?
I tried to find it at sourceforge.net, I found some words about it but not the
project.

Curious … if you search for QNX at sourceforge, the second entry of
the search result is pyqnx. (Sorry the link doesn’t work wit PyQNX …
you have to use pyqnx)

I don’t know if we have downloaded the wrong package but I got the
Python-2.2-qnx6.1.tar.gz and it only contains a libpython.2.2.a.

Yes … besides the sources is a running core python, dynamic modules and
the static lib
libpython2.2.a included, but not the dynamic lib libpython2.2.so.

The libpython.2.2.so will only be build for DG/UX, UnixWare and BeOS !!

I’ve generated a .so from that static lib

Why you don’t need a dynamic lib … the core of python will be build
using the static lib.

and relink python and I’m still blocked on the ‘segmentation violation’.

Well … it depends on what you have linked together. At which point does
the segment violation happen?

However … the archive contains a running version of python 2.2 which
doesn’t ‘segment violations’. We are using the same base and have on top
running wxPython and its huge demo, PyCrust, Pyro, the message passing
module and other apps without problems.

There is also a shell script at pyqnx which allows you to do your own
configure with the original source tar ball … you can take take it and
you can create your own initial version with it.

Regards

Armin

I get a ‘segmentation violation’ at start.

I’m a little bit confused with the ‘-fPIC’ flag because I first built
the tcl8.3 on 6.0 with this flag and I had to remove it on 6.1 in order
that wish run without a ‘segmentation violation’.

My experience is that tcl8.3 works instable as a DLL version … so I
link
that stuff always statically with python.


Maybe it’s the reason why I get this message!


Armin

any idea?

Alain.

Thanks,
Alain.

5

Armin Steinhoff a écrit :

Alain Bonnefoy wrote:

Armin Steinhoff a écrit :

Alain Bonnefoy wrote:

Does anybody succeded to build the libpython2.2.so and the corresponding
python shell.

Yes … you can download it from > http://www.sf.net/projects/PyQNX


This link is unreachable!?
I tried to find it at sourceforge.net, I found some words about it but not the
project.

Curious … if you search for QNX at sourceforge, the second entry of
the search result is pyqnx. (Sorry the link doesn’t work wit PyQNX …
you have to use pyqnx)

I don’t know if we have downloaded the wrong package but I got the
Python-2.2-qnx6.1.tar.gz and it only contains a libpython.2.2.a.

Yes … besides the sources is a running core python, dynamic modules and
the static lib
libpython2.2.a included, but not the dynamic lib libpython2.2.so.

The libpython.2.2.so will only be build for DG/UX, UnixWare and BeOS !!

I’ve generated a .so from that static lib

Why you don’t need a dynamic lib … the core of python will be build
using the static lib.

and relink python and I’m still blocked on the ‘segmentation violation’.

Well … it depends on what you have linked together. At which point does
the segment violation happen?

However … the archive contains a running version of python 2.2 which
doesn’t ‘segment violations’. We are using the same base and have on top
running wxPython and its huge demo, PyCrust, Pyro, the message passing
module and other apps without problems.

There is also a shell script at pyqnx which allows you to do your own
configure with the original source tar ball … you can take take it and
you can create your own initial version with it.

Regards

Armin



I get a ‘segmentation violation’ at start.

I’m a little bit confused with the ‘-fPIC’ flag because I first built
the tcl8.3 on 6.0 with this flag and I had to remove it on 6.1 in order
that wish run without a ‘segmentation violation’.

My experience is that tcl8.3 works instable as a DLL version … so I
link
that stuff always statically with python.


Maybe it’s the reason why I get this message!


Armin

any idea?

Alain.

Thanks,
Alain.

Thanks Armin, I haven’t enough time to continue on this subject. I will go back to
Python later.

Alain.