On 3/3/2011 11:25 PM, Michael D Godfrey wrote:
On 03/03/2011 09:21 PM, Orion Poplawski wrote:
It has been suggested that the binary components of octave packages
be installed in /usr/lib{,64}/octave rather than /usr/libexec/octave.
This is what happens now for rpm installed Octave on my Fedora 14
x86_64 system:
[root@pbds ~]# ls -l /usr/lib64/octave-3.2.4/
total 26092
lrwxrwxrwx. 1 root root 17 Feb 22 12:29 libcruft.so ->
libcruft.so.3.2.4
-rwxr-xr-x. 1 root root 573120 Feb 13 11:11 libcruft.so.3.2.4
lrwxrwxrwx. 1 root root 18 Feb 22 12:29 liboctave.so ->
liboctave.so.3.2.4
-rwxr-xr-x. 1 root root 11997440 Feb 13 11:11 liboctave.so.3.2.4
lrwxrwxrwx. 1 root root 21 Feb 22 12:29 liboctinterp.so ->
liboctinterp.so.3.2.4
-rwxr-xr-x. 1 root root 14140992 Feb 13 11:11 liboctinterp.so.3.2.4
[root@pbds ~]#
====================================
Seems OK.
That octave itself, not octave packages. Install octave-forge and take
a look at /usr/libexec/octave.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
