[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: help installing control 2.4.4 in in non-standard path installation o
|
From: |
Olaf Till |
|
Subject: |
Re: help installing control 2.4.4 in in non-standard path installation of 3.6.3 on RHEL6 |
|
Date: |
Thu, 22 Aug 2013 20:36:24 +0200 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, Aug 22, 2013 at 11:04:55AM -0500, Troy Lutes wrote:
> Greetings,
>
> I have Octave 3.6.3 installed in /usr/local/octave-3.6.3 on an NFS
> exported dirve. It was built with "./configure
> --prefix=/usr/local/octave-3.6.3" so that it created subdirectories
> like this /usr/local/octave-3.6.3/usr/local/share/octave/3.6.3.
This should not be so, are you sure? With this prefix, it should
create subdirectories like
/usr/local/octave-3.6.3/share/octave/3.6.3/
> <snip>
> Also "pkg install - forge control" fails like this:
> octave:1> pkg install -forge control
> warning: creating installation directory /usr/local/share/octave/packages
> error: could not create installation directory: No such file or directory
> error: called from:
> error: /usr/local/octave-3.6.3/scripts/pkg/pkg.m at line 659, column 7
Where comes this path from? Maybe you are running Octave from your
build directory? In this case, it seems you installed Octave under
your build directory. Is that so? I would not try such a thing, I
would not expect this is supported.
Olaf
--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net
signature.asc
Description: Digital signature