Re: error caused by Octave-forge function __grcmd__.oct

[Quentin Spencer]

Quentin Spencer wrote:
> Aakash Dalwani wrote:
>   
> > Hi,
> >     Octave-forge function __grcmd__.oct is throwing the following error 
> > when Octave starts-up
> >
> > "error: API version 2.1.50 found in .oct file function `__grcmd__'
> >        does not match the running Octave (API version api-v18)
> >        this can lead to incorrect results or other failures
> >        you can fix this problem by recompiling this .oct file
> > error: failed to install dld function `__grcmd__'
> > error: evaluating argument list element number 2
> > error: near line 1 of file 
> > `/home/octave-forge-2006.03.17/build/graceplot//PKG_ADD'
> > error: source: error sourcing file 
> > `/home/octave-forge-2006.03.17/build/graceplot//PKG_ADD'"
> >
> >
> > I am using Octave version 2.9.5 and I configured octave-forge in the 
> > following manner:
> >
> > export PATH=/home/octave-2.9.5/build:$PATH
> > export OCTAVE=/home/octave-2.9.5/build/bin/octave
> > export LD_LIBRARY_PATH=/home/octave-2.9.5/build/lib:$LD_LIBRARY_PATH
> > export MKOCTFILE=/home/octave-2.9.5/build/bin/mkoctfile
> >
> >
> > ./configure --with-path=/home/octave-forge-2006.03.17/build 
> > --prefix=/home/octave-forge-2006.03.17/build
> >
> >
> > If I am running an interactive job then I can proceed after the error, 
> > but if I have to submit a job, the PBS job exits after the error message.
> >
> > How do I get rid of it?
> >   
> >     
>
> If you're getting an API mismatch, I'd say you probably have two copies 
> of it in your path and you're picking up the wrong one. Look at the 
> output of "which __grcmd__" to see if it is what you expect it to be. 
>  From looking at this, I'm guessing you're on a Linux system with 2.1.50 
> (RHEL, maybe?) and you don't have root access so you're trying to run it 
> from your home directory. I'd say you need to look carefully at what's 
> happening when you build octave-forge and make sure it's not picking up 
> the installed system octave rather than your local one. It's been a long 
> time since I've done this, so that's about all the advice I can give.
>   

In reading my response I realize I'm kind of contradicting myself. You 
probably don't have two different versions of __grcmd__, but like I said 
later you're probably picking up the wrong mkoctfile or octave or 
something when compiling octave-forge.

Quentin