Re: octave forge does not work after upgrade

On 8/1/07, address@hidden < address@hidden> wrote:

Hello,
i upgraded from octave-2.1.73 to 2.9.9 and got problems with the
forge functions. I realized that some of them went to
octave 2.9.9 path (/usr/local/share/octave/2.9.9/m), but many
others not. Why is there a partial forge functions migration?

It is confusing. For example the two directories bellow have
different contents after upgrade (the former has more functions):
/usr/local/libexec/octave/2.1.73/oct/i386-portbld-freebsd6.2
/usr/local/libexec/octave/2.9.9/oct/i386- portbld-freebsd6.2

Are there deprecated functions which do not migrate to the new
version? What is the idea behind?

My actual problem now is running the function leasqr function.
As you see bellow, the problem is in the function __grishold__
which is a symlink to __grcmd__.oct, an LSB shared object.
Any help? Thanks in advance ...

> leasqr(g(:,1), g(:,2), pin, Tcalc);
error: /usr/local/libexec/octave/2.1.73/site/oct/i386-portbld-freebsd6.2 /octave-forge/__grishold__.oct:
Undefined symbol "_ZTV12octave_value"
error: `__grishold__' undefined near line 39 column 18
error: evaluating assignment _expression_ near line 39, column 16
error: evaluating if command near line 32, column 3
error: called from `__plt__' in file
`/usr/local/share/octave/2.1.73/site/octave-forge-alternatives/m/graceplot/__plt__.m'
error: called from `plot' in file
`/usr/local/share/octave/2.1.73/site/octave-forge-alternatives/m/graceplot/plot.m'
error: evaluating if command near line 245, column 3
error: evaluating for command near line 186, column 1
error: called from `leasqr' in file
`/usr/local/share/octave/2.1.73/site/m/octave-forge/optim/leasqr.m'
_______________________________________________
Help-octave mailing list
address@hidden
https://www.cae.wisc.edu/mailman/listinfo/help-octave

From:	James Sherman Jr.
Subject:	Re: octave forge does not work after upgrade
Date:	Wed, 1 Aug 2007 14:37:34 -0400