[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with Octave-2.9.14
From: |
Muthiah Annamalai |
Subject: |
Re: Problem with Octave-2.9.14 |
Date: |
Wed, 3 Oct 2007 17:13:38 -0500 |
On 10/3/07, John W. Eaton <address@hidden> wrote:
> On 3-Oct-2007, Rajkiran wrote:
>
> | I see that it is picking up m-files from another installation
> | on my system. How can I change the path from where it picks octave's
> | m-files ?
>
> It should just work. If you run what you think is the octave-2.9.14
> binary and version still returns 2.1.50, then you are not running
> 2.9.14. The fact that the version function returns 2.1.50 should tell
> you that something is screwed up. What is the output of running ls -l
> in the directory where you think octave 2.9.14 is installed? Have you
> tried removing 2.1.50? How did you install 2.9.14?
>
> jwe
>
>
One quick check to run 2.9.14 or whatever version, from the sources
is to do a
cd octave-2.9.14/
./run-octave
and actually see if you compiled octave successfully. This must
unambiguously startup 2.9.14, if you built it at all.
-Muthu
- Re: Problem with Octave-2.9.14, (continued)
- Re: Problem with Octave-2.9.14, Rajkiran, 2007/10/03
- Re: Problem with Octave-2.9.14, Tom Holroyd, 2007/10/03
- Re: Problem with Octave-2.9.14, John W. Eaton, 2007/10/03
- Re: Problem with Octave-2.9.14, Rajkiran, 2007/10/03
- Re: Problem with Octave-2.9.14, Rajkiran, 2007/10/03
- Re: Problem with Octave-2.9.14, John W. Eaton, 2007/10/03
- Re: Problem with Octave-2.9.14, Tom Holroyd, 2007/10/03
Re: Problem with Octave-2.9.14, Rajkiran, 2007/10/03
Re: Problem with Octave-2.9.14, Sergei Steshenko, 2007/10/03