* Thomas Weber <[EMAIL PROTECTED]> [2005-04-11 12:51]:
> Package: octaviz
> Version: 0.4.0-10
> Severity: normal
>
> octave:1> pwd
> /usr/share/doc/octaviz/examples
> octave:2> vtk_demo
> error: liboctaviz.so: cannot open shared object file: No such file or
> directory
> error: called from `vtk_demo' in file
> `/usr/share/doc/octaviz/examples/vtk_demo.m'
>
> This is due to the fact that liboctaviz.so is at
> /usr/lib/octave-2.1.67/liboctaviz.so,
> so vtk_init cannot find it.
>
> temporary workaround:
> symlink it from /usr/lib/octave-2.1.69/
Yes, this is a real problem because it forces us to recompile octaviz for
every minor release of Octave. We already fixed this problem for the
*.oct files by installing them in an API-versioned directory. I am
Cc:ing this message to the octave-maintainers mailing list for further
discussion.
The problem with octaviz is that is generates a liboctaviz.so file that
goes into OCTLIBDIR, which is:
$ octave-config -p OCTLIBDIR
/usr/lib/octave-2.1.69
Would it be possible to make this directory also "API-versioned" (if this
makes sense at all)?
--
Rafael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
