I create a one-dir package on a 32-bit Linux (Ubuntu 12) using the development pyinstaller.
The code executes properly in that system. I go to a 64-bit version of Ubuntu 12 and attempt to execute the identical package (literally the identical bits, both systems access it via Dropbox) and it does not run. Should it? Or must I make separate 32- and 64-bit versions? If it is supposed to work, here is the very strange error I get, under gdb so you can see it really comes out of the program. | $ gdb ppqt | GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04 | This GDB was configured as "x86_64-linux-gnu". | Reading symbols from /home/dcortesi/Dropbox/David/PPQT/ppqt-linux/dist/ppqt/ppqt...done. | (gdb) run | Starting program: /home/dcortesi/Dropbox/David/PPQT/ppqt-linux/dist/ppqt/ppqt | /bin/bash: /home/dcortesi/Dropbox/David/PPQT/ppqt-linux/dist/ppqt/ppqt: No such file or directory | During startup program exited with code 127. | (gdb) break main | Breakpoint 1 at 0x804bfb8 | (gdb) run | Starting program: /home/dcortesi/Dropbox/David/PPQT/ppqt-linux/dist/ppqt/ppqt | /bin/bash: /home/dcortesi/Dropbox/David/PPQT/ppqt-linux/dist/ppqt/ppqt: No such file or directory | During startup program exited with code 127. As you see, the program exists (gdb can load it) but before it reaches "main", the shell says it does not exist. Why is bash running at this point? Why can't it find the program? (If you google "bash no such file or directory" you find many people puzzled by that message in a variety of circumstances. It's a bash thing.) Thanks for your attention. -- 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.
