[sage-support] Re: Problem in Octave console

2009-04-22 Thread mabshoff



On Apr 22, 12:46 am, Ajay Rawat ajay.rawa...@gmail.com wrote:
 Well i tried the command
 sage:octave_version()
 sage:3.0.0
 but when i tried octave_console
 it replied...

 octave:
 /usr/local/sage-3.2.3-Ubuntu8.04LTS-64bit-Intel-x86_64-Linux/local/lib/l\
 ibz.so.1: no version information available (required by
 /usr/lib/octave-3.0.0/liboctinterp.so)

The problem is that the libz shipped by Sage and the one used by the
system (and which was linked by Octave) do not play nicely together.

To work around this write a script called octave (I assume that is the
name of the octave start script/binary

#!/bin/sh
LD_LIBRARY_PATH=SAGE_ORIG_LD_LIBRARY_PATH; export LD_LIBRARY_PATH
exec octave $@

I didn't try this, so you might need to adjust something.

To fix this once and for all in sage we should use native execute -
would someone open a ticket since I am about to go offline for the
night :)

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] Re: Problem in Octave console

2009-04-22 Thread Marshall Hampton

This is now a href=http://trac.sagemath.org/sage_trac/ticket/
5858ticket 5858/a.

Note that since I don't use Octave, I don't plan on working on this, I
just created the ticket :)

-M. Hampton

On Apr 22, 2:53 am, mabshoff michael.absh...@mathematik.uni-
dortmund.de wrote:
 On Apr 22, 12:46 am, Ajay Rawat ajay.rawa...@gmail.com wrote:

  Well i tried the command
  sage:octave_version()
  sage:3.0.0
  but when i tried octave_console
  it replied...

  octave:
  /usr/local/sage-3.2.3-Ubuntu8.04LTS-64bit-Intel-x86_64-Linux/local/lib/l\
  ibz.so.1: no version information available (required by
  /usr/lib/octave-3.0.0/liboctinterp.so)

 The problem is that the libz shipped by Sage and the one used by the
 system (and which was linked by Octave) do not play nicely together.

 To work around this write a script called octave (I assume that is the
 name of the octave start script/binary

 #!/bin/sh
 LD_LIBRARY_PATH=SAGE_ORIG_LD_LIBRARY_PATH; export LD_LIBRARY_PATH
 exec octave $@

 I didn't try this, so you might need to adjust something.

 To fix this once and for all in sage we should use native execute -
 would someone open a ticket since I am about to go offline for the
 night :)

 Cheers,

 Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---