[Python-Dev] problems building Python 2.1a1 on QNX 4.25

Andrew M. Kuchling akuchlin@mems-exchange.org
Fri, 26 Jan 2001 17:01:01 -0500

On Fri, Jan 26, 2001 at 04:46:13PM -0500, Goodger, David wrote:
>    ImportError: No module named string

The 'import string' in setup.py actually seems to be redundant now,
since nothing seems to actually refer to the string module.  I've
removed it from CVS.

>The QNX node number prefix '//5' (machine or host number, equivalent to a
>'hostname:' prefix for network paths) is being reduced somehow (path
>normalization?) to '/5', so paths don't resolve. 2 slashes ('//') are
>required at the head of the path. Is this something that can be fixed?

Ooh, very likely:
>>> os.path.normpath('//5/foo/bar')

Isn't // at the root a Unix convention of some sort for some 
network filesystems?  Probably normpath() should just leave it alone.

>QNX doesn't have an 'ld' command. Is configure not getting its info to
>setup.py? (Is it supposed to?)

setup.py should be parsing the Makefile.  The old QNX instructions say
Modules/Makefile should be edited, but with Neil's non-recursive
Makefile patch (committed after alpha1's release), editing
Modules/Makefile will have no effect.  Try editing just the top-level
Makefile, which should affect setup.py.