Wed 23 Nov 2016 09:56:13 PM UTC, comment #15:
I am truly sorry for the noise: I tried again to install inst-ctrl 0.2.3 with Octave 4.2.0 64 bits on Windows and now it totally works (output in 'Reinstalling_Instrument_Control_0.2.3_Succeded_64bits.log').
I used the exact same steps compared to when it failed the first time (I did not change anything related to user permission on my Windows7-64 machine).
BTW: octave was installed each time by using the regular win installers 'octave-4.2.0-w32-installer.exe' and 'octave-4.2.0-w64-installer.exe'
So, the rootcause of the failure during the first installation attempt of inst-ctrl remains a complete mystery for me.
In all cases, all topics related to this bug report are now solved (thank you).
FFE
(file #39062)
|
Wed 23 Nov 2016 12:36:59 AM UTC, comment #14:
Yeah, I get intermittent timeouts from sourceforge also, assuming it's occasional problems with the mirror network.
Let's give FFE a day or so to respond about the installation permissions error, but I think that's not at all related to this bug report and is just a normal administrator vs unprivileged user situation.
|
Wed 23 Nov 2016 12:28:14 AM UTC, comment #13:
The download issue sounds like the one I reported here:
http://lists.gnu.org/archive/html/octave-maintainers/2016-11/msg00094.html
it appeared intermittant - I think depending on what source forge mirror was being used.
It was fixed in mxe (or at least i havent had the issue since) so will be in the next installer.
|
Tue 22 Nov 2016 10:59:28 PM UTC, comment #12:
FYI
I had too install inst-ctrl on a different machine (fresh) as well.
I too had the problem with the server. Just thought it was a (temporary) server issue. So I downloaded the package myself. I Installed it on a laptop from work. This laptop is completely locked down. I have no special rights (unfortunately). Everything OK. I had no need for a -local option.
BTW: octave was 'installed' by just unpacking the octave-4.2.0-w64.zip is my user directory.
Win 10/64 bit
|
Tue 22 Nov 2016 10:25:38 PM UTC, comment #11:
Reopened.
This new error message seems like a Windows user permissions error, not something to do with the instrument-control package or Octave in particular.
When you install the package in Octave do you have permissions to create files and directories under C:\Octave\Octave-4.2.0? Does "pkg install -local ..." work? This error has been reported on the mailing list before and was resolved by installing Octave in a different directory or by repeating the steps as the admin user.
Inability to install a package with the -forge option seems like a connectivity, routing, or name resolution problem.
Does this link work for you in your web browser?
http://packages.octave.org/download/instrument-control-0.2.3.tar.gz
|
Tue 22 Nov 2016 10:03:09 PM UTC, comment #10:
Wait, wait. It's too soon to close this bug.
Indeed, I confirm the new release 0.2.3 of instrument-control is installing and working well with Octave 4.2.0-32 bits on Windows (see file 'Reinstalling_Instrument_Control_0.2.3_Succeded_32bits.log').
However, I failed to have it installed successfully on Octave 4.2.0-64 bits on Windows (see file 'Reinstalling_Instrument_Control_0.2.3_Failed_64bits.log').
In short: on the 64 bits version, the very last operation of the package installation failed by issuing the following:
After that, I have no instrument-control anymore.
Finally, is it normal to have the following command:
failing at 90% of calling attempts? Most of the time, it gives the following:
In fact, the file shortly appears and then it is erased with the above error message (on Windows).
FFE
(file #39048, file #39049)
|
Tue 22 Nov 2016 01:29:45 PM UTC, comment #9:
0.2.3 works in windows 10 32 bit
|
Mon 21 Nov 2016 08:05:26 PM UTC, comment #8:
New release 0.2.3 has been pushed to OF.
|
Sun 20 Nov 2016 11:19:53 PM UTC, comment #7:
As the maintainer said he still has to make a package.
In the meantime, you could try this (assuming you do not have mercurial installed)
Download the latest snapshot:
https://sourceforge.net/code-snapshots/hg/o/oc/octave/instrument-control/octave-instrument-control-da8d3d6c40b67b6d2e8ff8e5792e1874798bccea.zip
start the cmdshell.bat of octave.
go to the directory of the downloaded zip file (cd ....)
unzip octave-instrument-control-da8d3d6c40b67b6d2e8ff8e5792e1874798bccea.zip
mv octave-instrument-control-da8d3d6c40b67b6d2e8ff8e5792e1874798bccea instrument-control-0.2.3
tar -czf instrument-control-0.2.3.tar.gz instrument-control-0.2.3/
In octave
pkg install instrument-control-0.2.3.tar.gz
|
Sun 20 Nov 2016 05:37:50 PM UTC, comment #6:
As you already figured it out, I confirm that reinstalling from octave forge did not change anything to the issue.
Additionally, the following command failed
by giving the following
Therefore, I reinstalled manually:
The output of the reinstallation is in the attached file 'Reinstalling_Instrument_Control_0.2.2_Failed.log'.
FFE
(file #39031)
|
Fri 18 Nov 2016 01:00:36 PM UTC, comment #5:
I see subdirectory build was already documented in bug #47617
|
Fri 18 Nov 2016 12:56:37 PM UTC, comment #4:
Yes, it's a relict from the time, when there was no autoconf.
|
Fri 18 Nov 2016 12:39:40 PM UTC, comment #3:
It would be good if make fails if one of the subdirectories fails to build - or at least would make it obvious then something had gone wrong.
|
Fri 18 Nov 2016 05:36:21 AM UTC, comment #2:
I also noticed this. This problem also occurs on linux. I already had contact with the maintainer:
His response:
"
the BINOPDECL issue was already fixed:
https://sourceforge.net/p/octave/instrument-control/ci/808a4b7f9723bb875b1a2a06df19dd0cefa27582/
Unfortunately I did not manage to prepare a new release yet. Hope I have
time in the next few days.
"
|
Fri 18 Nov 2016 12:05:21 AM UTC, comment #1:
I'll take a look when I hae access to my windows machine.
In the meantime - does it still have the saeme issue if you install it from octave forge rather than using the prebuilt package?
pkg install -forge instrument-control
|
Thu 17 Nov 2016 10:09:50 PM UTC, original submission:
Since the latest release of Octave 4.2.0 for Windows 64 bits (32 or 64 binaries), it seems that the instrument-control package 0.2.2 does not support all serial-related functions anymore.
Indeed, after loading the package, the support of serial fails:
this gives me 0 (anything else than 3 means "no support").
Note that the serial support was just working well on Octave 4.0.3.
|