Comment 6 for bug 578767

Revision history for this message
albop (pablo-winant) wrote :

After spending some time on it, I could compile pytave under sage but I now get a runtime exception (and another bug with python interpreter). Here are the steps I have followed (which I will summarize properly when the whole thing is done) :

* sage -sh # loads sage subshell with its environment variables
* compile/install the boost library
* compile/install octave (a pending bug prevents it from compiling withouth X libraries so xorg-dev has to be installed) # I compiled octave because it needs zlib which is included in sage and results in version conflicts
* go to pytave subdirectory and run :
 - LINK = `"python -c "import distutils.sysconfig; print distutils.sysconfig.get_config_var('LINKFORSHARED')"
- ./configure CFLAGS="$LINK -lm" LDFLAGS="-L/home/pablo/Source/sage-4.4/local/lib/python2.6/config -L/home/pablo/Source/boost_1_43_0/stage/lib/"
- python setup.py build
- python setup.py install

Then I get interesting bugs (some of them may be related to Sage). I wrote a simple test file containing
'''
from pytave import pytave
pytave.eval(0,'a=213')
print pytave.eval(1,'a')
''
then running :
- ./sage test.py # no problem
- ./sage -ipython test.py # no problem

but if I use interactive interpreter,
- ./sage then import pytave
I get a long backtrace which I attach here. I don't know how to interpret this one. Any clue ?

Also (this is not related to sage) when I run :
- ./sage -python then import pytave
- python then import pytave # system wide python on my laptop
I get octave greeting message and end up with octave command line. It works perfectly with IPython.