Failure (Re: How to use octave-forge?)

[Vic Norton]

Thanks for all the advice about installing octave-forge functions. I am
sorry to report that my installation efforts have not met with success.
My octave 2.1.50 has no trouble reading newly installed octave-forge
m-files, but it cannot execute any oct-files.

This note is rather longish. I'm sorry about that. Throw it away if you
will. I am just trying to describe my situation accurately. Maybe someone
can tell me what is going on.

              *              *              *

I installed the "octave-forge-2003.06.02" package in "/opt/local", where
my octave resides:

   octave-forge-2003.06.02$ ./configure --prefix=/oct/local

Everything went where it was supposed to. After the installation, all
"m" files worked but no "oct" files worked. And "oct" files come
first in my LOADPATH:

   LOADPATH = 
/opt/local/libexec/octave/2.1.50/site/oct/powerpc-apple-darwin7.0.0/octave-forge:...


There was something peculiar about this installation. Both the tests
failed to execute:

   octave-forge-2003.06.02$ make check
   octave -q batch_test.m
   warning: batch_test.m: no such file or directory
   make: *** [check] Error 1

   octave-forge-2003.06.02$ make icheck
   octave -q interact_test.m
   warning: interact_test.m: no such file or directory
   make: *** [icheck] Error 1

And the files "batch_test.m" and "interact_test.m" were definitely in
the "octave-forge-2003.06.02" directory.


So I decided to run "batch_test" from octave interactively. After using
my newly created "addpath" function:

   octave> addpath("~/Download/octave-forge-2003.06.02");

to put the "octave-forge-2003.06.02" directory in my LOADPATH, I ran

   octave> batch_test;

The output was

   [main/optim]
   >leval
   error: `leval' undefined near line 8 column 24
   error: evaluating argument list element number 1
   error: near line 8 of file 
`/Users/vic/Download/octave-forge-2003.06.02/batch_test.m'

The script "batch_test.m" had failed at the line

   disp(">leval"); assert(leval("acos", list(-1)), pi, 100*eps);


What's the hell is going on here? "leval.cc" had clearly been compiled
in the make process:

   mkoctfile -DHAVE_OCTAVE_21 -v leval.cc
   g++ -c -no-cpp-precomp -I/opt/local/include 
-I/opt/local/include/octave-2.1.50 
-I/opt/local/include/octave-2.1.50/octave -I/opt/local/include -g -O2 
-Wall -DHAVE_OCTAVE_21 leval.cc -o leval.o
   g++ -bundle -bundle_loader /opt/local/bin/octave-2.1.50 -o 
leval.oct leval.o -L/opt/local/lib/octave-2.1.50 -loctave -lcruft 
-loctinterp -framework vecLib

And "leval" was apparently compiled right there in
"~/Download/octave-forge-2003.06.02/main/optim", where octave was
supposed to see it:

   optim$ ls -l
   ...
   -rw-r--r--  1 vic  vic     1674 13 Mar  2002 leval.cc
   -rw-r--r--  1 vic  vic   255744 23 Dec 12:17 leval.o
   -rwxr-xr-x  1 vic  vic  1391620 23 Dec 12:17 leval.oct*

So why couldn't octave see "lp.oct"? Whu can't it see any newly compiled
oct files.


This whole situation is VERY FRUSTRATING!!! Any insights into what my
problem is would be greatly appreciated!


Regards,

Vic



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------