octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53938] Windows Octave doesn't wait for --eval


From: John Donoghue
Subject: [Octave-bug-tracker] [bug #53938] Windows Octave doesn't wait for --eval statements to complete
Date: Fri, 6 Jul 2018 08:08:10 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299

Follow-up Comment #17, bug #53938 (project octave):

statistics is overriding octave.

I created the octave changes patch from the stable branch so at least it
should merge cleanly.


However .....


I just tried the strings package which I see has $(shell $(OCTAVE)) call in
its make file and it fails at that point because it is running in a bash 
shell and do doesn't know the DOC commands used in bat files



>> pkg install -verbose -forge strings
mkdir (C:\Users\JOHN\AppData\Local\Temp\oct-MI6SEN)
untar (C:\Users\JOHN\strings-1.2.0.tar.gz,
C:\Users\JOHN\AppData\Local\Temp\oct-MI6SEN)
C:/Octave/OCTAVE~4.0/bin/octave-5.0.0.bat: line 1: @echo: command not found
C:/Octave/OCTAVE~4.0/bin/octave-5.0.0.bat: line 2: Rem: command not found
C:/Octave/OCTAVE~4.0/bin/octave-5.0.0.bat: line 9: syntax error near
unexpected token `('
C:/Octave/OCTAVE~4.0/bin/octave-5.0.0.bat: line 9: `for %%I in ("%OCT_HOME%")
do set OCT_HOME=%%~sI'
make: Entering directory `/tmp/oct-MI6SEN/strings-1.2.0/src'
C:/Octave/OCTAVE~4.0/bin/mkoctfile-5.0.0.exe --verbose  -o pcregexp.oct
pcregexp.cc
g++ -c -I/home/johnd/mxe-octave/build-64/usr/x86_64-w64-mingw32/include 
-IC:\Octave\OCTAVE~4.0\include\octave-5
.0.0\octave\.. -IC:\Octave\OCTAVE~4.0\include\octave-5.0.0\octave
-IC:\Octave\OCTAVE~4.0\include   -fopenmp -g -
O2    pcregexp.cc -o C:/Users/JOHN/AppData/Local/Temp/oct-gpBQRQ.o
pcregexp.cc: In function 'octave_value_list Fpcregexp(const
octave_value_list&, int)':



And to make more fun,  from octave, running system("octave.bat") works fine as
it is then using the windows shell.

Im not sure what other repercusions there would be if we just change the shell
variable in the scripts


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53938>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]