Problem installing Mongrel2 Python support on OSX 10.6
- From:
- John Toohey
- Date:
- 2011-06-12 @ 00:57
Hi,
Apologies if this is not a mongrel2 issue, but a pure python one. I
only have a passing familiarity with Python on OSX. I have a new
Mongrel2 server installed and running, and calling my Clojure based
handers. My server is a pub-sub feed server pushing real-time sporting
odds to Flash clients, and mobile clients.
I want to write some simple tests in Python, but have an issue when
trying to install the Mongrel2 Python modules. From example/python I
run sudo python setup.py install, but it fails with this :-
Installed
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/m2py-1.0beta7-py2.7.egg
Processing dependencies for m2py==1.0beta7
Searching for storm
Reading http://pypi.python.org/simple/storm/
Reading https://storm.canonical.com
Reading https://launchpad.net/storm/+download
Best match: storm 0.18
Downloading http://launchpad.net/storm/trunk/0.18/+download/storm-0.18.tar.bz2
Processing storm-0.18.tar.bz2
Running storm-0.18/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-SLExAI/storm-0.18/egg-dist-tmp-kQRcFq
In file included from /usr/include/architecture/i386/math.h:626,
from /usr/include/math.h:28,
from
/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/pyport.h:312,
from
/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:58,
from storm/cextensions.c:23:
/usr/include/AvailabilityMacros.h:108:14: warning: #warning Building
for Intel with Mac OS X Deployment Target < 10.4 is invalid.
/usr/libexec/gcc/powerpc-apple-darwin10/4.0.1/as: assembler
(/usr/bin/../libexec/gcc/darwin/ppc/as or
/usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not
installed
Installed assemblers are:
/usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64
/usr/bin/../libexec/gcc/darwin/i386/as for architecture i386
lipo: can't open input file: /var/tmp//ccByYCOo.out (No such file or directory)
error: Setup script exited with error: command 'gcc-4.0' failed with
exit status 1
I have Python 2.7.1 installed and am running on OSX 10.6
--
--
-JT
Re: [mongrel2] Problem installing Mongrel2 Python support on OSX 10.6
- From:
- Zed A. Shaw
- Date:
- 2011-06-12 @ 10:35
On Sat, Jun 11, 2011 at 08:57:52PM -0400, John Toohey wrote:
> Hi,
> Apologies if this is not a mongrel2 issue, but a pure python one. I
> only have a passing familiarity with Python on OSX. I have a new
> Mongrel2 server installed and running, and calling my Clojure based
> handers. My server is a pub-sub feed server pushing real-time sporting
> odds to Flash clients, and mobile clients.
This looks really weird:
> /usr/include/AvailabilityMacros.h:108:14: warning: #warning Building
> for Intel with Mac OS X Deployment Target < 10.4 is invalid.
> /usr/libexec/gcc/powerpc-apple-darwin10/4.0.1/as: assembler
> (/usr/bin/../libexec/gcc/darwin/ppc/as or
> /usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not
> installed
> Installed assemblers are:
> /usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64
> /usr/bin/../libexec/gcc/darwin/i386/as for architecture i386
> lipo: can't open input file: /var/tmp//ccByYCOo.out (No such file or directory)
> error: Setup script exited with error: command 'gcc-4.0' failed with
> exit status 1
I don't believe I've ever seen that kind of error, and actually can't
figure out what it's saying, apart from maybe your version of gcc is too
old and you need to upgrade the developer tools you have. Make sure
you've got the latest GCC that Apple offers then retry it.
--
Zed A. Shaw
http://zedshaw.com/
Re: [mongrel2] Problem installing Mongrel2 Python support on OSX 10.6
- From:
- Nathan Duran
- Date:
- 2011-06-13 @ 00:39
> /usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not
> installed
I'm going to guess that you probably paid $5 for Xcode 4 from the App Store,
which removes every last scrap of PPC support. Many an easy_install still
requires PPC compilers unfortunately, so if you want to keep using Python
installers without modification, you have to back out to Xcode 3.