[Octave-bug-tracker] [bug #40222] OF windows pkg doesn't get installed anymore with Octave dev version

[Philip Nienhuis]

URL:
  <http://savannah.gnu.org/bugs/?40222>

                 Summary: OF windows pkg doesn't get installed anymore with
Octave dev version
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Wed 09 Oct 2013 07:30:50 PM CEST
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

See (parts of) the discussion about this in bug #40180.

While many other OF packages install w/o issues, (e.g., control, io, general,
...), the windows package can't get beyond the configure step. This issue
popped up about a week ago.


> pkg install -verbose windows-1.2.1.tar.gz
mkdir (C:\Home\Philip\LOCALS~1\Temp\oct-61)
untar (windows-1.2.1.tar.gz, C:\Home\Philip\LOCALS~1\Temp\oct-61)
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-2013-10-07-22-02/bin/mkoctfile-3.7.7+.exe
In file included from conftest.cc:2:0:
C:\octave\octave-2013-10-07-22-02\include\octave-3.7.7+\octave\../octave/version.h:35:8:
error: 'string' in namespace 'std' does not name a type
C:\octave\octave-2013-10-07-22-02\include\octave-3.7.7+\octave\../octave/version.h:37:8:
error: 'string' in namespace 'std' does not name a type
C:\octave\octave-2013-10-07-22-02\include\octave-3.7.7+\octave\../octave/version.h:39:8:
error: 'string' in namespace 'std' does not name a type
C:\octave\octave-2013-10-07-22-02\include\octave-3.7.7+\octave\../octave/version.h:41:8:
error: 'string' in namespace 'std' does not name a type
C:\octave\octave-2013-10-07-22-02\include\octave-3.7.7+\octave\../octave/version.h:43:8:
error: 'string' in namespace 'std' does not name a type
C:\octave\octave-2013-10-07-22-02\include\octave-3.7.7+\octave\../octave/version.h:47:8:
error: 'string' in namespace 'std' does not name a type
C:\octave\octave-2013-10-07-22-02\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-2013-10-07-22-02/bin/mkoctfile-3.7.7+.exe

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


(Above lines may not be in strict chronological order as there are separate
processes at work).

Manually trying the various commands in share/.../pkg/private/configure_make.m
in an MSYS shell, I can only get as far as a complaint from configure a la
"mkoctfile not found". But that doesn't match the error messages above => I
gave up there.

Note that in lines 51-65 of configure_make.m, where the configure flags are
cooked, 'mkoctfile ("-p", "AR")' always returns newlines at the end, e.g.:

>> mkoctfile("-p", "AR")
ar
>> int8 (mkoctfile("-p", "AR"))
ans =

   97  114   13   10


(note CRLF at end); these newlines end up in the final shell command a few
lines down.
To my surprise this also happens on older (e.g., 3.7.5) Octave versions;
apparently that wasn't a problem there ?!





    _______________________________________________________

Reply to this item at:

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

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