Installation of PyEphem version 3.7.3.4 fails for Python 2.5.x under Mac OS X version 10.4.11

Bug #417130 reported by Starfighter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PyEphem
Invalid
Medium
Brandon Rhodes

Bug Description

Attempting to install PyEphem-3.7.3.4 on a PPC Mac running Mac OS X 10.4.11 for Mac Python ver. 2.5.x. I ran the installer script as follows:
dsl092-239-159:~/pyephem-3.7.3.4 samueldupree$ sudo python setup.py install
running install
running bdist_egg
running egg_info
writing src/pyephem.egg-info/PKG-INFO
writing top-level names to src/pyephem.egg-info/top_level.txt
writing dependency_links to src/pyephem.egg-info/dependency_links.txt
reading manifest file 'src/pyephem.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'src/pyephem.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.3-ppc/egg
running install_lib
running build_py
running build_ext
building 'ephem._libastro' extension
creating build/temp.macosx-10.3-ppc-2.5
creating build/temp.macosx-10.3-ppc-2.5/extensions
creating build/temp.macosx-10.3-ppc-2.5/libastro-3.7.3
creating build/temp.macosx-10.3-ppc-2.5/extensions/data
gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -Ilibastro-3.7.3 -I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c extensions/_libastro.c -o build/temp.macosx-10.3-ppc-2.5/extensions/_libastro.o
gcc: unrecognized option '-no-cpp-precomp'
cc1: error: unrecognized command line option "-arch"
cc1: error: unrecognized command line option "-arch"
cc1: error: unrecognized command line option "-Wno-long-double"
error: command 'gcc' failed with exit status 1
dsl092-239-159:~/pyephem-3.7.3.4 samueldupree$

Revision history for this message
Brandon Rhodes (brandon-rhodes) wrote :

I'm a bit at a loss about what to do with this bug! Those "gcc" options that Python's trying to use are not ones that I mention anywhere in my code, so it must be part of Python, distutils, or setuptools that's pulling them in instead. Are you using a Python you compiled yourself, or one that came from something like MacPorts?

It looks like your version of "gcc" might have been upgraded beyond the version that your Python was compiled with. Doing a Google search for those errors, I can see it has to do with old versions of Python that use those "--" options, but I can't tell exactly which component you need to switch out or upgrade for this to work.

Changed in pyephem:
status: New → Incomplete
importance: Undecided → Medium
assignee: nobody → Brandon Craig Rhodes (brandon-rhodes)
Revision history for this message
Brandon Rhodes (brandon-rhodes) wrote :

Since I have received no answer to my question of several months ago (about whether the bug reporter's version of Python was compiled themselves or by someone else), I cannot provide further help and am closing this report.

Changed in pyephem:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.