Re: Octave-forge and 'pkg install' question

[Tatsuro MATSUOKA]

Hello

--- "E. Joshua Rigler" <address@hidden> wrote:

> Thanks Tatsuro.  It turns out that even though I compiled all of the
> libraries that Ocatve depended on (SuiteSparse, fftw, etc.) using the
> LDFLAGS option, I did not set this when I compiled Octave, which is
> why mkoctfile wasn't working as expected.  I made the change you
> suggested and everything works fine now.
> 
> ...well, almost fine.  Can anyone tell me why my *.oct files get
> placed in my personal directory (i.e., ~/octave), even though the *.m
> scripts get placed in the system directory (i.e.,
> ~/local/share/octave/packages), when I install using 'pkg install
> -global plot-1.0.4.tar.gz'?  Maybe I misunderstand the '-global'
> option.


Please read:

octave>help path

See also: addpath, rmpath, genpath, pathdef, savepath, pathsep.

After that, please execute

octave>path

Octave loads *.m and *.oct files from the load path and present working 
directry.



> Maybe I misunderstand the '-global'
> option.

         `-local'
               A local installation is forced, even if the user has
               system privileges.

         `-global'
               A global installation is forced, even if the user
               doesn't normally have system privileges

Regards

Tatsuro


--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/