Cannot install pyephem on 64-bit machine

Bug #570343 reported by Paul Marganian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PyEphem
Invalid
Medium
Unassigned

Bug Description

On a 64-bit linux machine:
Python 2.5.2

[dss@trent 2]$ easy_install pyephem
Searching for pyephem
Reading http://pypi.python.org/simple/pyephem/
Reading http://rhodesmill.org/pyephem/
Best match: pyephem 3.7.3.4
Downloading http://pypi.python.org/packages/source/p/pyephem/pyephem-3.7.3.4.tar.gz
Processing pyephem-3.7.3.4.tar.gz
Running pyephem-3.7.3.4/setup.py -q bdist_egg --dist-dir /tmp/easy_install-umxhdE/pyephem-3.7.3.4/egg-dist-tmp-qaTkVS
In file included from /home/dss/robin/include/python2.5/Python.h:57,
                 from extensions/_libastro.c:3:
/home/dss/robin/include/python2.5/pyport.h:761:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
error: Setup script exited with error: command 'gcc' failed with exit status 1
[dss@trent 3]$

I get similar errors when I download the source and try to install by hand.
Thanks.

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

Are you using Red Hat 7? There was a bug in the development version of "gcc" that, for unknown reasons, the Red Hat team decided to distribute as though it were a production version of the compiler. See whether this Python FAQ entry helps you out:

http://wiki.python.org/moin/Python20FrequentlyAskedQuestions#LONGBITError

Good luck! Write back either way so that I know whether this has solved your problem. Thanks!

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

Since I see no further activity on this bug, I will assume that it was indeed a problem with Red Hat and close it as invalid. Please do add a new comment here if you were not able to solve your problem! Otherwise, good luck and I hope PyEphem works well for you.

Changed in pyephem:
status: New → Invalid
Revision history for this message
Anton Norup Sørensen (anton-norup) wrote :

While I am happily using pyephem on a 32bit ubuntu system, I cannot install it on 64 bit:
Linux version 2.6.32-26-generic
Ubuntu 10.04 LTS
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2

sudo easy_install pyephem
Searching for pyephem
Reading http://pypi.python.org/simple/pyephem/
Reading http://rhodesmill.org/pyephem/
Best match: pyephem 3.7.3.4
Downloading http://pypi.python.org/packages/source/p/pyephem/pyephem-3.7.3.4.tar.gz
Processing pyephem-3.7.3.4.tar.gz
Running pyephem-3.7.3.4/setup.py -q bdist_egg --dist-dir /tmp/easy_install-mkgjwd/pyephem-3.7.3.4/egg-dist-tmp-B1T9R_
Then a LOT of errors races over the screen - my xterm buffer cannot hold it all. Here is the top and bottom of the buffered content:
extensions/_libastro.c:1046: error: expected ‘)’ before ‘*’ token
extensions/_libastro.c:1053: error: expected declaration specifiers or ‘...’ before ‘PyObject’
extensions/_libastro.c:1053: error: expected declaration specifiers or ‘...’ before ‘PyObject’
extensions/_libastro.c: In function ‘Planet_setup’:
<lots more>
extensions/_libastro.c:2825: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
extensions/_libastro.c:2892: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘libastro_methods’
extensions/_libastro.c:2952: warning: return type defaults to ‘int’
extensions/_libastro.c: In function ‘DL_EXPORT’:
extensions/_libastro.c:2952: error: expected declaration specifiers before ‘init_libastro’
extensions/_libastro.c:3041: error: expected ‘{’ at end of input
error: Setup script exited with error: command 'gcc' failed with exit status 1

I hope you can help, thanks, Anton

Revision history for this message
Anton Norup Sørensen (anton-norup) wrote :

Got it installed now :)
I was missing the development header files for python 2.6 (Python.h, datetime.h, structmember.h)

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

Great! I'm glad that the package is now building for you.

Changed in pyephem:
importance: Undecided → Medium
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.