Review of windows package

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Review of windows package

John Donoghue-3
Does any one have a little spare time to review the next version of the
windows package on the release tracker?

https://sourceforge.net/p/octave/package-releases/362/

The current review checklist is
https://wiki.octave.org/Reviewing_Octave-Forge_packages


Thanks

JohnD


Reply | Threaded
Open this post in threaded view
|

Re: Review of windows package

mmuetzel
Am 06. April 2019 um 13:49 Uhr schrieb "John Donoghue":
> Does any one have a little spare time to review the next version of the
> windows package on the release tracker?
>
> https://sourceforge.net/p/octave/package-releases/362/
>
> The current review checklist is
> https://wiki.octave.org/Reviewing_Octave-Forge_packages
>

To be honest I am not very familiar with Octave's package system and I don't know how to do a review.
This is what I did:
On Octave 6.0.0 (hg id: 7b03bc060dc7) unpacked from the 7z-dist file, I ran the following:
>> pkg install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
For information about changes from previous versions of the windows package, run 'news windows'.

"news windows" displays fine. "pkg load windows" seems to work and "runtests D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1" reported that both BISTs succeeded.
"pkg unload windows" works.
However on uninstall, I see the following:
>> pkg uninstall windows
error: couldn't delete directory D:\Repositories\Octave\test\octave-2019-04-06-15-4
2-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1: Directory not empty
error: called from
    uninstall at line 120 column 11
    pkg at line 490 column 7
But the directory is empty:
>> dir D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1
.   ..
I don't know whether this is specific to the package.
Should I run any further tests?


On Octave 5.1.0.0 installed with the official Windows installer, I couldn't install the package with the same command that succeeded with the self-compiled development version:
>> pkg -verbose install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
mkdir (C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
untar (C:\Users\Markus\AppData\Local\Temp\oct-9fRLSF\windows-1.3.1.tar.gz, C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
./configure: line 1436: cannot create temp file for here-document: Permission denied
./configure: line 1448: cannot create temp file for here-document: Permission denied
./configure: line 1483: cannot create temp file for here-document: Permission denied
./configure: line 1645: cannot create temp file for here-document: Permission denied
./configure: line 1649: cannot create temp file for here-document: Permission denied
./configure: line 1653: cannot create temp file for here-document: Permission denied
./configure: line 1657: cannot create temp file for here-document: Permission denied
./configure: line 1661: cannot create temp file for here-document: Permission denied
./configure: line 1665: cannot create temp file for here-document: Permission denied
configure: loading site script /usr/local/etc/config.site
checking for gcc... gcc
./configure: line 2128: cannot create temp file for here-document: Permission denied
checking whether the C compiler works... no
sed: can't read conftest.c: No such file or directory
configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-PEhJf8/windows-1.3.1/src':
configure: error: C compiler cannot create executables
See `config.log' for more details

pkg: error running the configure script for windows.
error: called from
    configure_make at line 82 column 9
    install at line 184 column 7
    pkg at line 441 column 9
>>

However, I don't know whether I am doing the right thing.
Maybe this is because the folder that Octave is installed in seems to be protected by user account control on my system. If this is the case, I am inclined to say that this is an error in Octave's pkg function or the installer rather than in the windows package.

Markus

Reply | Threaded
Open this post in threaded view
|

Re: Review of windows package

John Donoghue-3
On 4/6/19 12:01 PM, "Markus Mützel" wrote:

> Am 06. April 2019 um 13:49 Uhr schrieb "John Donoghue":
>> Does any one have a little spare time to review the next version of the
>> windows package on the release tracker?
>>
>> https://sourceforge.net/p/octave/package-releases/362/
>>
>> The current review checklist is
>> https://wiki.octave.org/Reviewing_Octave-Forge_packages
>>
> To be honest I am not very familiar with Octave's package system and I don't know how to do a review.
> This is what I did:
> On Octave 6.0.0 (hg id: 7b03bc060dc7) unpacked from the 7z-dist file, I ran the following:
>>> pkg install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
> For information about changes from previous versions of the windows package, run 'news windows'.
>
> "news windows" displays fine. "pkg load windows" seems to work and "runtests D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1" reported that both BISTs succeeded.
> "pkg unload windows" works.
> However on uninstall, I see the following:
>>> pkg uninstall windows
> error: couldn't delete directory D:\Repositories\Octave\test\octave-2019-04-06-15-4
> 2-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1: Directory not empty
> error: called from
>      uninstall at line 120 column 11
>      pkg at line 490 column 7
> But the directory is empty:
>>> dir D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1
> .   ..
> I don't know whether this is specific to the package.
> Should I run any further tests?
>
>
> On Octave 5.1.0.0 installed with the official Windows installer, I couldn't install the package with the same command that succeeded with the self-compiled development version:
>>> pkg -verbose install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
> mkdir (C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
> untar (C:\Users\Markus\AppData\Local\Temp\oct-9fRLSF\windows-1.3.1.tar.gz, C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
> ./configure: line 1436: cannot create temp file for here-document: Permission denied
> ./configure: line 1448: cannot create temp file for here-document: Permission denied
> ./configure: line 1483: cannot create temp file for here-document: Permission denied
> ./configure: line 1645: cannot create temp file for here-document: Permission denied
> ./configure: line 1649: cannot create temp file for here-document: Permission denied
> ./configure: line 1653: cannot create temp file for here-document: Permission denied
> ./configure: line 1657: cannot create temp file for here-document: Permission denied
> ./configure: line 1661: cannot create temp file for here-document: Permission denied
> ./configure: line 1665: cannot create temp file for here-document: Permission denied
> configure: loading site script /usr/local/etc/config.site
> checking for gcc... gcc
> ./configure: line 2128: cannot create temp file for here-document: Permission denied
> checking whether the C compiler works... no
> sed: can't read conftest.c: No such file or directory
> configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-PEhJf8/windows-1.3.1/src':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
>
> pkg: error running the configure script for windows.
> error: called from
>      configure_make at line 82 column 9
>      install at line 184 column 7
>      pkg at line 441 column 9
> However, I don't know whether I am doing the right thing.
> Maybe this is because the folder that Octave is installed in seems to be protected by user account control on my system. If this is the case, I am inclined to say that this is an error in Octave's pkg function or the installer rather than in the windows package.
>
> Markus


You could try a local install perhaps (-local) and see if that gets
around permission issues ?



What does installing a package from forge do? Such as the recently
reclease control or signal package ?


Reply | Threaded
Open this post in threaded view
|

Re: Review of windows package

mmuetzel
Am 06. April 2019 um 19:50 Uhr schrieb "John Donoghue":

> On 4/6/19 12:01 PM, "Markus Mützel" wrote:
> > Am 06. April 2019 um 13:49 Uhr schrieb "John Donoghue":
> >> Does any one have a little spare time to review the next version of the
> >> windows package on the release tracker?
> >>
> >> https://sourceforge.net/p/octave/package-releases/362/
> >>
> >> The current review checklist is
> >> https://wiki.octave.org/Reviewing_Octave-Forge_packages
> >>
> > To be honest I am not very familiar with Octave's package system and I don't know how to do a review.
> > This is what I did:
> > On Octave 6.0.0 (hg id: 7b03bc060dc7) unpacked from the 7z-dist file, I ran the following:
> >>> pkg install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
> > For information about changes from previous versions of the windows package, run 'news windows'.
> >
> > "news windows" displays fine. "pkg load windows" seems to work and "runtests D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1" reported that both BISTs succeeded.
> > "pkg unload windows" works.
> > However on uninstall, I see the following:
> >>> pkg uninstall windows
> > error: couldn't delete directory D:\Repositories\Octave\test\octave-2019-04-06-15-4
> > 2-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1: Directory not empty
> > error: called from
> >      uninstall at line 120 column 11
> >      pkg at line 490 column 7
> > But the directory is empty:
> >>> dir D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1
> > .   ..
> > I don't know whether this is specific to the package.
> > Should I run any further tests?
> >
> >
> > On Octave 5.1.0.0 installed with the official Windows installer, I couldn't install the package with the same command that succeeded with the self-compiled development version:
> >>> pkg -verbose install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
> > mkdir (C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
> > untar (C:\Users\Markus\AppData\Local\Temp\oct-9fRLSF\windows-1.3.1.tar.gz, C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
> > ./configure: line 1436: cannot create temp file for here-document: Permission denied
> > ./configure: line 1448: cannot create temp file for here-document: Permission denied
> > ./configure: line 1483: cannot create temp file for here-document: Permission denied
> > ./configure: line 1645: cannot create temp file for here-document: Permission denied
> > ./configure: line 1649: cannot create temp file for here-document: Permission denied
> > ./configure: line 1653: cannot create temp file for here-document: Permission denied
> > ./configure: line 1657: cannot create temp file for here-document: Permission denied
> > ./configure: line 1661: cannot create temp file for here-document: Permission denied
> > ./configure: line 1665: cannot create temp file for here-document: Permission denied
> > configure: loading site script /usr/local/etc/config.site
> > checking for gcc... gcc
> > ./configure: line 2128: cannot create temp file for here-document: Permission denied
> > checking whether the C compiler works... no
> > sed: can't read conftest.c: No such file or directory
> > configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-PEhJf8/windows-1.3.1/src':
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details
> >
> > pkg: error running the configure script for windows.
> > error: called from
> >      configure_make at line 82 column 9
> >      install at line 184 column 7
> >      pkg at line 441 column 9
> > However, I don't know whether I am doing the right thing.
> > Maybe this is because the folder that Octave is installed in seems to be protected by user account control on my system. If this is the case, I am inclined to say that this is an error in Octave's pkg function or the installer rather than in the windows package.
> >
> > Markus
>
>
> You could try a local install perhaps (-local) and see if that gets
> around permission issues ?
>
>
>
> What does installing a package from forge do? Such as the recently
> reclease control or signal package ?

I see the same error for control:
>> pkg -forge install control
./configure: line 1390: cannot create temp file for here-document: Permission denied
./configure: line 1402: cannot create temp file for here-document: Permission denied
./configure: line 1437: cannot create temp file for here-document: Permission denied
./configure: line 1599: cannot create temp file for here-document: Permission denied
./configure: line 1603: cannot create temp file for here-document: Permission denied
./configure: line 1607: cannot create temp file for here-document: Permission denied
./configure: line 1611: cannot create temp file for here-document: Permission denied
./configure: line 1615: cannot create temp file for here-document: Permission denied
./configure: line 1619: cannot create temp file for here-document: Permission denied
./configure: line 1970: cannot create temp file for here-document: Permission denied
sed: can't read conftest.cpp: No such file or directory
configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-bQ3I7B/control-3.2.0/src':
configure: error: C++ compiler cannot create executables
See `config.log' for more details
configure: loading site script /usr/local/etc/config.site
checking for mkoctfile... C:/Octave/OCTAVE~1.0/mingw64/bin/mkoctfile-5.1.0.exe
checking for octave-config... C:/Octave/OCTAVE~1.0/mingw64/bin/octave-config-5.1.0.exe
checking for g++... g++
checking whether the C++ compiler works... no

pkg: error running the configure script for control.
error: called from
    configure_make at line 82 column 9
    install at line 184 column 7
    pkg at line 441 column 9

And also the same for a -local install:
>> pkg -local install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
./configure: line 1436: cannot create temp file for here-document: Permission denied
./configure: line 1448: cannot create temp file for here-document: Permission denied
./configure: line 1483: cannot create temp file for here-document: Permission denied
./configure: line 1645: cannot create temp file for here-document: Permission denied
./configure: line 1649: cannot create temp file for here-document: Permission denied
./configure: line 1653: cannot create temp file for here-document: Permission denied
./configure: line 1657: cannot create temp file for here-document: Permission denied
./configure: line 1661: cannot create temp file for here-document: Permission denied
./configure: line 1665: cannot create temp file for here-document: Permission denied
./configure: line 2128: cannot create temp file for here-document: Permission denied
sed: can't read conftest.c: No such file or directory
configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-Asu4E3/windows-1.3.1/src':
configure: error: C compiler cannot create executables
See `config.log' for more details
configure: loading site script /usr/local/etc/config.site
checking for gcc... gcc
checking whether the C compiler works... no

pkg: error running the configure script for windows.
error: called from
    configure_make at line 82 column 9
    install at line 184 column 7
    pkg at line 441 column 9

Markus

Reply | Threaded
Open this post in threaded view
|

Re: Review of windows package

John Donoghue-3
On 4/6/19 3:53 PM, "Markus Mützel" wrote:

> Am 06. April 2019 um 19:50 Uhr schrieb "John Donoghue":
>> On 4/6/19 12:01 PM, "Markus Mützel" wrote:
>>> Am 06. April 2019 um 13:49 Uhr schrieb "John Donoghue":
>>>> Does any one have a little spare time to review the next version of the
>>>> windows package on the release tracker?
>>>>
>>>> https://sourceforge.net/p/octave/package-releases/362/
>>>>
>>>> The current review checklist is
>>>> https://wiki.octave.org/Reviewing_Octave-Forge_packages
>>>>
>>> To be honest I am not very familiar with Octave's package system and I don't know how to do a review.
>>> This is what I did:
>>> On Octave 6.0.0 (hg id: 7b03bc060dc7) unpacked from the 7z-dist file, I ran the following:
>>>>> pkg install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
>>> For information about changes from previous versions of the windows package, run 'news windows'.
>>>
>>> "news windows" displays fine. "pkg load windows" seems to work and "runtests D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1" reported that both BISTs succeeded.
>>> "pkg unload windows" works.
>>> However on uninstall, I see the following:
>>>>> pkg uninstall windows
>>> error: couldn't delete directory D:\Repositories\Octave\test\octave-2019-04-06-15-4
>>> 2-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1: Directory not empty
>>> error: called from
>>>       uninstall at line 120 column 11
>>>       pkg at line 490 column 7
>>> But the directory is empty:
>>>>> dir D:\Repositories\Octave\test\octave-2019-04-06-15-42-w64\octave-2019-04-06-15-42-w64\mingw64\share\octave\packages\windows-1.3.1
>>> .   ..
>>> I don't know whether this is specific to the package.
>>> Should I run any further tests?
>>>
>>>
>>> On Octave 5.1.0.0 installed with the official Windows installer, I couldn't install the package with the same command that succeeded with the self-compiled development version:
>>>>> pkg -verbose install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
>>> mkdir (C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
>>> untar (C:\Users\Markus\AppData\Local\Temp\oct-9fRLSF\windows-1.3.1.tar.gz, C:\Users\Markus\AppData\Local\Temp\oct-PEhJf8)
>>> ./configure: line 1436: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1448: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1483: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1645: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1649: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1653: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1657: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1661: cannot create temp file for here-document: Permission denied
>>> ./configure: line 1665: cannot create temp file for here-document: Permission denied
>>> configure: loading site script /usr/local/etc/config.site
>>> checking for gcc... gcc
>>> ./configure: line 2128: cannot create temp file for here-document: Permission denied
>>> checking whether the C compiler works... no
>>> sed: can't read conftest.c: No such file or directory
>>> configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-PEhJf8/windows-1.3.1/src':
>>> configure: error: C compiler cannot create executables
>>> See `config.log' for more details
>>>
>>> pkg: error running the configure script for windows.
>>> error: called from
>>>       configure_make at line 82 column 9
>>>       install at line 184 column 7
>>>       pkg at line 441 column 9
>>> However, I don't know whether I am doing the right thing.
>>> Maybe this is because the folder that Octave is installed in seems to be protected by user account control on my system. If this is the case, I am inclined to say that this is an error in Octave's pkg function or the installer rather than in the windows package.
>>>
>>> Markus
>>
>> You could try a local install perhaps (-local) and see if that gets
>> around permission issues ?
>>
>>
>>
>> What does installing a package from forge do? Such as the recently
>> reclease control or signal package ?
> I see the same error for control:
>>> pkg -forge install control
> ./configure: line 1390: cannot create temp file for here-document: Permission denied
> ./configure: line 1402: cannot create temp file for here-document: Permission denied
> ./configure: line 1437: cannot create temp file for here-document: Permission denied
> ./configure: line 1599: cannot create temp file for here-document: Permission denied
> ./configure: line 1603: cannot create temp file for here-document: Permission denied
> ./configure: line 1607: cannot create temp file for here-document: Permission denied
> ./configure: line 1611: cannot create temp file for here-document: Permission denied
> ./configure: line 1615: cannot create temp file for here-document: Permission denied
> ./configure: line 1619: cannot create temp file for here-document: Permission denied
> ./configure: line 1970: cannot create temp file for here-document: Permission denied
> sed: can't read conftest.cpp: No such file or directory
> configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-bQ3I7B/control-3.2.0/src':
> configure: error: C++ compiler cannot create executables
> See `config.log' for more details
> configure: loading site script /usr/local/etc/config.site
> checking for mkoctfile... C:/Octave/OCTAVE~1.0/mingw64/bin/mkoctfile-5.1.0.exe
> checking for octave-config... C:/Octave/OCTAVE~1.0/mingw64/bin/octave-config-5.1.0.exe
> checking for g++... g++
> checking whether the C++ compiler works... no
>
> pkg: error running the configure script for control.
> error: called from
>      configure_make at line 82 column 9
>      install at line 184 column 7
>      pkg at line 441 column 9
>
> And also the same for a -local install:
>>> pkg -local install https://sourceforge.net/p/octave/package-releases/_discuss/thread/bdda9bfc44/5bdb/attachment/windows-1.3.1.tar.gz
> ./configure: line 1436: cannot create temp file for here-document: Permission denied
> ./configure: line 1448: cannot create temp file for here-document: Permission denied
> ./configure: line 1483: cannot create temp file for here-document: Permission denied
> ./configure: line 1645: cannot create temp file for here-document: Permission denied
> ./configure: line 1649: cannot create temp file for here-document: Permission denied
> ./configure: line 1653: cannot create temp file for here-document: Permission denied
> ./configure: line 1657: cannot create temp file for here-document: Permission denied
> ./configure: line 1661: cannot create temp file for here-document: Permission denied
> ./configure: line 1665: cannot create temp file for here-document: Permission denied
> ./configure: line 2128: cannot create temp file for here-document: Permission denied
> sed: can't read conftest.c: No such file or directory
> configure: error: in `/c/Users/Markus/AppData/Local/Temp/oct-Asu4E3/windows-1.3.1/src':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> configure: loading site script /usr/local/etc/config.site
> checking for gcc... gcc
> checking whether the C compiler works... no
>
> pkg: error running the configure script for windows.
> error: called from
>      configure_make at line 82 column 9
>      install at line 184 column 7
>      pkg at line 441 column 9
>
> Markus

Well at least it is consistent across packages :)

I seem to recall perhaps seeing this before, and it was my virus checker
trying to be smart and was stopping configure from creating files. Or at
least worked again when I turned of the virus checker. It never had an
notifcations, just was silently stopping it from creating files.

Are you able to turn off your virus checker temporarily and run the pkg
install again ?


Reply | Threaded
Open this post in threaded view
|

Re: Review of windows package

Mike Miller-4
On Sat, Apr 06, 2019 at 17:05:40 -0400, John Donoghue wrote:

> On 4/6/19 3:53 PM, "Markus Mützel" wrote:
> > checking whether the C compiler works... no
> >
> > pkg: error running the configure script for windows.
> > error: called from
> >      configure_make at line 82 column 9
> >      install at line 184 column 7
> >      pkg at line 441 column 9
> >
> > Markus
>
> Well at least it is consistent across packages :)
>
> I seem to recall perhaps seeing this before, and it was my virus checker
> trying to be smart and was stopping configure from creating files. Or at
> least worked again when I turned of the virus checker. It never had an
> notifcations, just was silently stopping it from creating files.

ISTR this is about Windows restrictions on what can be done with files
in the default user Temp directory.

Try setting the TEMP or TMPDIR environment variables to point to another
directory and see if that works around it.

--
mike

Reply | Threaded
Open this post in threaded view
|

Re: Review of windows package

nrjank
On Sat, Apr 6, 2019, 6:05 PM Mike Miller <[hidden email]> wrote:

ISTR this is about Windows restrictions on what can be done with files
in the default user Temp directory.

Try setting the TEMP or TMPDIR environment variables to point to another
directory and see if that works around it.


That was the issue I discovered a few weeks ago.  Rather than change the TEMP location for the whole system I created an empty C:\Octave\Temp folder, and before a pkg install, in run:

>> setenv('tmpdir', 'C:\Octave\Temp')

And then installation works just fine. You could also add that line to your .octaverc file.

To check current setting:

>> tempdir
ans = c:\Octave\Temp\

Compilation and execution in the user's temp folder is disallowed by some windows security protocols and anti-malware services now. Telling it to compile elsewhere seems to be the easiest solution.