[Octave-bug-tracker] [bug #40180] pkg.m: search for mkoctfile etc. ignores .exe extension on windows

[Philip Nienhuis]

Follow-up Comment #6, bug #40180 (project octave):

The variable 'octave_binary' also needs an .exe extension as
__gripe_missing_component__ checks this executable as well, a few lines
lower.
With the patch from comment #2, after fixing this, dropping the "if then else"
for the superfluous '.' and trying again, the build_packages script in the MXE
Windows build works again- for most packages, see below.
Shall I try to produce a changeset later (I'm on Windows now, I usually
cross-build on Linux), or will you, Mike?


However, it turns out that now the windows package doesn't install anymore (it
did fine before changeset 17516:21656a949661).

I tried to debug this but didn't get very far; the error messages are:

>> pkg install -verbose windows-1.2.1.tar.gz
mkdir (C:\Users\Philip\AppData\Local\Temp\oct-20)
untar (windows-1.2.1.tar.gz, C:\Users\Philip\AppData\Local\Temp\oct-20)

checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for mkoctfile...
C:/Octave/octave-3.7.7+_MXE/bin/mkoctfile-3.7.7+.exe
In file included from conftest.cc:2:0:
C:\Octave\octave-3.7.7+_MXE\include\octave-3.7.7+\octave\../octave/version.h:35:8:
error: 'string' in namespace 'std' does not name a type
C:\Octave\octave-3.7.7+_MXE\include\octave-3.7.7+\octave\../octave/version.h:37:8:
error: 'string' in namespace 'std' does not name a type
C:\Octave\octave-3.7.7+_MXE\include\octave-3.7.7+\octave\../octave/version.h:39:8:
error: 'string' in namespace 'std' does not name a type
C:\Octave\octave-3.7.7+_MXE\include\octave-3.7.7+\octave\../octave/version.h:41:8:
error: 'string' in namespace 'std' does not name a type
C:\Octave\octave-3.7.7+_MXE\include\octave-3.7.7+\octave\../octave/version.h:43:8:
error: 'string' in namespace 'std' does not name a type
C:\Octave\octave-3.7.7+_MXE\include\octave-3.7.7+\octave\../octave/version.h:47:8:
error: 'string' in namespace 'std' does not name a type
C:\Octave\octave-3.7.7+_MXE\include\octave-3.7.7+\octave\../octave/version.h:51:8:
error: 'string' in namespace 'std' does not name a type
g++: error: conftest.o: No such file or directory
configure: error: Could not run
C:/Octave/octave-3.7.7+_MXE/bin/mkoctfile-3.7.7+.exe
status =  1
output =

pkg: error running the configure script for windows.
error: called from 'configure_make' in file
C:\Octave\octave-3.7.7+_MXE\share\octave\3.7.7+\m\pkg\private\configure_make.m
near line 72, column 9
error: called from:
error:  
C:\Octave\octave-3.7.7+_MXE\share\octave\3.7.7+\m\pkg\private\install.m at
line 199, column 5
error:   C:\Octave\octave-3.7.7+_MXE\share\octave\3.7.7+\m\pkg\pkg.m at line
394, column 9
>>


The above compile errors are a red herring. The actual error is with the
configure command.
I got only as far as assessing that the variable 'cmd' cooked up in lines
66-67 of ..../pkg/private/configure_make.m seems to contain a number of
newlines inserted at the end (clearly distinguishable from line wrap):

cmd = cd 'C:\Users\Philip\AppData\Local\Temp\oct-20\Windows\src';
MKOCTFILE="C:\Octave\octave-3.7.7+_MXE\bin\mkoctfile-3.7.7+.exe"
OCTAVE_CONFIG="C:\Octave\octave-3.7.7+_MXE\bin\octave-config-3.7.7+.exe"
OCTAVE="C:\Octave\octave-3.7.7+_MXE\bin\octave-3.7.7+.exe"
INSTALLDIR="C:\Octave\octave-3.7.7+_MXE\share\octave\packages\windows-1.2.1"
./configure
--prefix="C:\Octave\octave-3.7.7+_MXE\share\octave\packages\windows-1.2.1"
 CC="gcc
" CXX="g++
" AR="ar
" RANLIB="ranlib
"


Discerning where these newlines come from proved undoable for me; a stumbling
block I hit (while stepping through configure_make) was that this 'cmd'
variable was garbled at the end in my Octave GUI terminal (maybe a separate
issue).

(The windows pkg install issue is reported here because I suppose it is
related to changeset 17516:21656a949661)


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/