Re: fresh build -> error: `unimplemented' not found

[Ben Abbott]

On Sep 20, 2012, at 11:39 AM, Jordi Gutiérrez Hermoso wrote:

> On 20 September 2012 11:31, Ben Abbott <address@hidden> wrote:
>> On Sep 20, 2012, at 11:24 AM, Jordi Gutiérrez Hermoso wrote:
>> 
>>> On 20 September 2012 11:18, Ben Abbott <address@hidden> wrote:
>>>> 
>>>> On Sep 20, 2012, at 10:55 AM, Jordi Gutiérrez Hermoso wrote:
>>>> 
>>>>> On 20 September 2012 08:16, Ben Abbott <address@hidden> wrote:
>>>>>> 
>>>>>>      $ ./run-octave --no-site-file --no-init-file --no-site-file
>>>>>> 
>>>>>>      octave:1> path
>>>>>>      error: feval: function `unimplemented' not found
> 
>>>>> If you temporarily modify run-octave so that it echoes the
>>>>> actual command it uses, can you verify that it's attempting to set a
>>>>> path that isn't there?
> 
>>>> I replaced "exec" with "echo"
>>>> 
>>>> /Users/bpabbott/Development/mercurial/default/sources/libtool 
>>>> --mode=execute 
>>>> /Users/bpabbott/Development/mercurial/default/sources/src/octave 
>>>> --no-init-path 
>>>> --path=/Users/bpabbott/Development/mercurial/default/sources/scripts:
>>> [etc]
>>> 
>>> And is this the right path? :-)
>> 
>> Looks correct to me.
> 
> Well, I'm mystified. Why would path complain? It's a built-in
> function. Do you have a path.m somewhere?
> 
> - Jordi G. H.


The problem is present without the initialization files ...

        ./run-octave --no-gui --no-site-file --no-init-file

... and there is no path.m in my build directory (from where I'm running 
octave), so I don't think a errant path.m is my problem.

Ben