Yes, that is possible. However I run it on a 64-bit linux system with no troubles. Perhaps there is some i386 compatibility library that you need to install that will make it runnable for you? I seem to recall needing something like that in the past for something else so I probably still have that installed. I build the sip binary in a 32-bit chroot so I can save some time and not have to worry about two builds, with the expectation that it should run on both.
If you're not able to find a compatibility package then you can build sip yourself and set the SIP environment variable to the full path of your binary. You'll want to make sure that you build at least close to the same version I'm using since some new features have been added specifically for Phoenix and so a version that is too old will not generate some of the code correctly (from Phoenix's perspective anyway.) When the current version listed in build.py is a snapshot build like currently, then you can use the hash number part of the version as the revision to fetch from sip's mercurial repository. However since there has been an official sip release since that snapshot build then that will probably work fine too.
···
On 9/26/12 6:44 PM, pyvert wrote:
I'm hoping someone can hello with this. I recently built phoenix on my 32 bit ubuntu 12.10 for py3.2 from svn without any issue. So I moved on to my 12.10 64 bit desktop and everything goes well until it gets to sip. It downloads the sip binary attempts to execute it and it fails saying "/bin/sh: 1: (sip filename) command not found. I get the same error if I try running it manually. Could this be a conflict between a 32 bit sip binary and a 64 bit machine? Any help would be greatly appreciated. Ive been a big fan of wxpython for a lot of years and its the only thing keeping me from moving to python 3.2
Thanks
On ubuntu I think the package you need is called 'ia32-libs'. It rally
confused me the first time I saw that
"What do you mean command not found, it's right there!"
Sam
···
On 27 September 2012 04:37, Robin Dunn <robin@alldunn.com> wrote:
On 9/26/12 6:44 PM, pyvert wrote:
I'm hoping someone can hello with this. I recently built phoenix on my 32
bit ubuntu 12.10 for py3.2 from svn without any issue. So I moved on to my
12.10 64 bit desktop and everything goes well until it gets to sip. It
downloads the sip binary attempts to execute it and it fails saying
"/bin/sh: 1: (sip filename) command not found. I get the same error if I
try running it manually. Could this be a conflict between a 32 bit sip
binary and a 64 bit machine? Any help would be greatly appreciated. Ive
been a big fan of wxpython for a lot of years and its the only thing keeping
me from moving to python 3.2
Thanks
Yes, that is possible. However I run it on a 64-bit linux system with no
troubles. Perhaps there is some i386 compatibility library that you need to
install that will make it runnable for you? I
On 27 September 2012 04:37, Robin Dunn <robin@alldunn.com> wrote:
Yes, that is possible. However I run it on a 64-bit linux system with no
troubles. Perhaps there is some i386 compatibility library that you need to
install that will make it runnable for you? I
On ubuntu I think the package you need is called 'ia32-libs'. It rally
confused me the first time I saw that
Thanks for all your help I download the sip snapshot 4.14 and made it through the sip portion but crashed on waf_py so I downloaded the 4.13-maint and compiled that seeing as your sip was 4.13.4 unfortunately it crashed in the same spot. It starts waf_py and makes it through [5/491] before it starts throwing errors…
I figured it out I needed to copy the siplib folder from the sip build directory to the Phoenix/sip directory I didn’t do a make install on sip so i’m not sure if I would have if it would have worked fine but its currently working. Assuming this finishes (cross my fingers) I’d like to offer to do a buildbot slave if you’re interested.
Thanks again for all your help and the great work you’ve done on taking this endeavour on to add python3 support
···
On Thursday, September 27, 2012 1:13:48 PM UTC-4, Robin Dunn wrote:
