> From: [hidden email] <[hidden email]> on behalf of Nicholas
> Jankowski <[hidden email]>
> Sent: Monday, May 15, 2017 1:37 PM
> To: Calvin Corey
> Subject: Re: Windows PKG Error - 'gfortran' is not recognized as an internal
> or external command
> On Mon, May 15, 2017 at 1:25 PM, flamed250 <[hidden email]> wrote:
>> I'm a new Octave user, but have been using matlab for years.
>> All of the basic functionality is working well, but I'm trying to install
>> the controls package (then signal package) and am getting the following
> control should be one of the default installed packages in the windows
> builds. Is yours missing?
> I installed the compiled windows version, 4.2.1, it does not appear to have
> the controls toolbox installed.
> what I'm really after is the signal toolbox, and the THD function. I
> confirmed the controls toolbox wasn't installed, because when I run "pkg
> install - forge signal" I receive the error "signal needs control >= 2.4.5.
(Sorry, new phone I keep neglecting to keep the help list in the
conversation. CC'd now)
Both 4.2.1 install methods, whether you used the zip package or the
.exe installer, include a set of pre-installed packages including
control and signal. Note that if you used the .zip package installer,
you need to run:
>> pkg rebuild
once for Octave to see and be able to use the packages. to be sure
you can go to:
and see if there are package folders listed there.
otherwise you should be able to type
>> pkg list
and see what packages Octave recognizes as being installed in your system, and
>> pkg load control
>> pkg load system
should load each of the respective packages for you to use.
Re: Windows PKG Error - 'gfortran' is not recognized as an internal or external command
On Mon, May 15, 2017 at 3:46 PM, flamed250 <[hidden email]> wrote:
> I don't see control when I run the command "pkg list"... but I do see signal
> now... odd.
> I'll try a fresh install tonight and update where I get.
I am seeing some odd things too trying to run pkg install after a
package is already installed. If it was previously installed, it may
fail. If it fails, it may or may not show up in a pkg list before
running pkg rebuild. Uninstall may fail with a permission error trying
to move a file from the /lib folder to the /share folder. And
re-installs will fail until manually deleting that /lib folder...
A fresh install should fix things. Do a pkg list to see what's there
right away. a pkg update should bring any installed packages up to
the latest version if you notice something out of date.