PySPICE fails to install

[fergalm]

I'm having some trouble getting PySpice installed on my machine.
It compiles without warning:

$ CSPICE_SRC=/home/fmullall/apps/cspice/
$ export CSPICE_SRC
$ python setup.py build_ext
running build_ext
building '_spice' extension
creating build
creating build/temp.linux-x86_64-2.7
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/home/fmullall/apps/cspice/include -I/usr/include/python2.7 -c pyspice.c -o build/temp.linux-x86_64-2.7/pyspice.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/home/fmullall/apps/cspice/include -I/usr/include/python2.7 -c spicemodule.c -o build/temp.linux-x86_64-2.7/spicemodule.o
creating build/lib.linux-x86_64-2.7
gcc -pthread -shared build/temp.linux-x86_64-2.7/pyspice.o build/temp.linux-x86_64-2.7/spicemodule.o -L/home/fmullall/apps/cspice/lib -L/usr/lib64 -lcspice -lpython2.7 -o build/lib.linux-x86_64-2.7/_spice.so

and installs without incident:
$ python setup.py install --prefix=~/.local/
running install
running build
running build_py
creating build/lib.linux-x86_64-2.7/spice
copying spice/objects.py -> build/lib.linux-x86_64-2.7/spice
copying spice/init.py -> build/lib.linux-x86_64-2.7/spice
copying spice/misc.py -> build/lib.linux-x86_64-2.7/spice
running build_ext
running install_lib
copying build/lib.linux-x86_64-2.7/_spice.so -> /home/fmullall/.local//lib64/python2.7/site-packages
running install_egg_info
Removing /home/fmullall/.local//lib64/python2.7/site-packages/Spice-1.0-py2.7.egg-info
Writing /home/fmullall/.local//lib64/python2.7/site-packages/Spice-1.0-py2.7.egg-info

But when I run it, I get an error message:
$ PYTHONPATH=$PYTHONPATH:/home/fmullall/.local/lib64/python2.7/site-packages/
$ python -c 'import spice'
Traceback (most recent call last):
File "", line 1, in
File "spice/init.py", line 3, in
from misc import *
File "spice/misc.py", line 3, in
from _spice import *
ImportError: dynamic module does not define init function (init_spice)

The readme files suggests this might be a 32/64 bit problem, but cspice
is compiling 64 bit as well, as best I can tell. Any ideas what I'm doing wrong?

[michaelaye]

what do you mean by "cspice is compiling 64 bit as well' ? Are you compiling your own cspice? I am asking because usually NAIF delivers usable binaries in its distribution files?

[astromancer]

Hi there!

I'm bumping into exactly the same problem described above. I'm running the 64bit Linux SPICE (http://naif.jpl.nasa.gov/naif/toolkit_C_PC_Linux_GCC_64bit.html) and python 2.7.

I also tried Apollo117's Python3 fork, but again got the same error.

Any advice?

[fergalm]

Hi Apodemus,

Firstly, apologies to Michael Aye, for some reason I never saw your email
back when I was trying to get things installed. For what it's worth, I
think I downloaded source code and complied it myself, but I can't be sure.

Anyway, I fixed the missing init function error, but this was a couple of
years ago, and my memory is hazy about what I did exactly. I think the
solution was to follow the manual instructions in README.rst

I think the line
python mkwrapper.py /path/to/cspice > spicemodule.c

hardcoded a path to a shared object library previously generated by CSpice
so that python knew where to look for it.

Hope that helps.

Fergal

On 6 August 2014 05:48, apodemus notifications@github.com wrote:

Hi there!

I'm bumping into exactly the same problem described above. I'm running the
64bit Linux SPICE (
http://naif.jpl.nasa.gov/naif/toolkit_C_PC_Linux_GCC_64bit.html) and
python 2.7.

I also tried Apollo117's Python3 fork, but again got the same error.

Any advice?

—
Reply to this email directly or view it on GitHub
#6 (comment).

[astromancer]

Hi Fergal

The manual build did the trick. So simple - should have done that straight away!

Thanks!

[abieler]

Have the same thing happening. Can not do the manual install as

python mkwrapper.py /myPathTo/PySPICE-master/cspice > spicemodule.c

fails with

File "mkwrapper.py", line 1077, in
print main(cspice_toolkit)
File "mkwrapper.py", line 1004, in main
if gen_wrapper(curr_prototype, buffer):
File "mkwrapper.py", line 259, in gen_wrapper
param_info = parse_param(param)
File "mkwrapper.py", line 837, in parse_param
raise msg
ValueError: invalid literal for int() with base 10: ''

I had pyspice working on several machines under linux, but with mint 17 it now fails.
sidenote: when executing python setup.py build_ext it returns the same error as above, however rerunning the command will let it go through. also the install part works with no complaints.

cheers
andre

[drbitboy]

Quick solution for N0065:

https://github.com/drbitboy/PySPICE

[abieler]

thanks, that worked fine. Although some funky permission issues:

/usr/local/lib/python2.7/dist-packages/spice/ and _spice.so had reading permissions
disabled. so python could not import it although it was installed just fine.

[matteobachetti]

I have the same problem.
The fix (manual installation with hardcoded full path) didn't work for me, on Ubuntu 14.04 LTS 64b and Mac OSX Mavericks (still 64b).
Funky things happen with the parsing of include files in mkwrapper.py.
In the file cspice/include/SpiceZpr.h, the line

                                SpiceDouble           termpts [ ][3] );

seems to give problems, producing in turn that

ValueError: invalid literal for int() with base 10: ''

message. That open bracket/space/closed bracket raises an exception in mkwrapper.py. Eliminating the space doesn't seem to take the problem away.

This does not happen in linux 32b AFAIK, as other colleagues installed it correctly, but I haven't had the time to install it on a VM and test it myself.

[drbitboy]

Quick solution for N0065:

https://github.com/drbitboy/PySPICE

[drjmcauliffe]

@drbitboy thanks for this fix.

[tonyVeco]

I have problems after installing PySPICE for linux suse 32 bit to use SPICE in the 32 bit version.
The spice package correctly appears in the python library but I can not use any of the functions, python does not recognize them. What could be the problem?

[michaelaye]

Please specify "appears in the python library". Do you mean "import spice"
worked?
And what do you mean by "python does not recognize them".
Just show the commands you are trying to do and their error messages.

On Mon, Mar 16, 2015 at 8:47 AM, antonio19812 notifications@github.com
wrote:

I have problems after installing PySPICE for linux suse 32 bit to use
SPICE in the 32 bit version.
The spice package correctly appears in the python library but I can not
use any of the functions, python does not recognize them. What could be the
problem?

—
Reply to this email directly or view it on GitHub
#6 (comment).

[tonyVeco]

This is the screenshot.
I need to work with spice and I am trying to learn how to use it. First I would like to try some examples of the various functions. I need to use for example GETFOV and I was trying to reproduce an example from the documentation but when I try to call the function and load the kernel with FURNSH, python just see them as undefined variables. WHY?? how should i call the functions??? I usually works with python but this time i have problems

[drjmcauliffe]

This wrapper of SPICE is not really maintained. I'd checkout SpiceyPy by Andrew Annex if I were you: https://github.com/AndrewAnnex/SpiceyPy

[drbitboy]

Do this at a shell prompt:

python -c 'import spice;spice.tkvrsn("toolkit")'

please and paste the result in a response here.