> You could also look at the wscript file if it needs some changes to tell > gcc link libpython static.
I know you did some work. But I will still need my changes in the bootloader. Otherwise, the bootloader cannot get to the symbols in the library. However, that leads to a bigger problem, for as long as I cannot build the bootloader (as waf requires something more than Python 2.2), I cannot produce a bootloader that links in a static libpython2.2. (A catch 22 situation.) The only other solution I see is to distribute the libpython2.6.a (shared lib) from the machine where the bootloader is built, along with the bootloader. But maybe it is too much work to make it work for Python 2.2 on AIX. > > I think I will call it the day for now, and have a look at it after > > the weekend. > > Or we could just state: > > "Pyinstaller works on AIX 6.1, created executables should work on > 5.2/5.3. PyInstaller does not work on 5.x. Something like that, but this is really not a 5.x problem, but rather a Python 2.2 problem on AIX as: * libpython2.2.a is static on AIX (at least on my machine) * I cannot build a bootloader on Python 2.2 (because of waf). Maybe the option I added could be altered to give the full path to the dynamic lib I want the bootloader to load. (I'll look into that on Monday.) Anyways, the fix mentioned above, changing line 527 in Build.py from: if typ == 'BINARY' and name in fnm: to if typ == 'BINARY' and fnm.find(name) != -1: should be applied. Otherwise, PyInstaller is potentially broken on Python 2.2 on any *NIX platform. /Martin -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
