RE: error when installing io package

[JohnD]

> -----Original Message-----
> From: John W. Eaton [mailto:address@hidden
> Sent: Thursday, January 15, 2015 12:09 PM
> To: JohnD; address@hidden; 'Philip Nienhuis'
> Subject: Re: error when installing io package
> 
> On 01/15/2015 08:49 AM, JohnD wrote:
> >
> >
> >> -----Original Message-----
> >> From: JohnD [mailto:address@hidden
> >> Sent: Thursday, January 15, 2015 9:33 AM
> >> To: address@hidden; address@hidden; 'Philip Nienhuis'
> >> Subject: RE: error when installing io package
> >>
> >>>
> >>> Message: 1
> >>> Date: Wed, 14 Jan 2015 12:22:10 -0600
> >>> From: "John W. Eaton" <address@hidden>
> >>> To: octave maintainers mailing list <address@hidden>
> >>> Subject: error when installing io package
> >>> Message-ID: <address@hidden>
> >>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >>>
> >>> I noticed an error from movefile when installing the io package on
> >>> windows saying that there were no files to move.  Can anyone else
> >>> confirm this
> >> problem,
> >>> or is it just me?  All I did was
> >>>
> >>>     pkg install -noauto -verbose io-2.2.6.tar.gz
> >>>
> >>> and the installation fails with the movefile "no files to move" error.
> >>>
> >>> Should this problem be fixed in pkg by avoiding the call to movefile
> >>> if
> >> there are
> >>> no files to move, or should movefile simply issue a warning if there
> >>> are
> >> no files
> >>> to move and return success?
> >>>
> >>> jwe
> >>>
> >>
> >> I see it on my 4.1.0+
> >>
> >>>> pkg install -forge -noauto -verbose io
> >> mkdir (C:\Users\JDONOG~1.ECE\AppData\Local\Temp\oct-lSqsGj)
> >> untar (C:\Octave\Octave-4.1.0+\src\io-2.2.6.tar.gz,
> >> C:\Users\JDONOG~1.ECE\AppData\Local\Temp\oct-lSqsGj)
> >> movefile: no files to move
> >> error: called from 'movefile' in file
> >> C:\Octave\Octave-4.1.0+\share\octave\4.1.0+\m\miscellaneous\movefile.
> >> m
> >> near line 92,  column 5
> >>>>
> >
> > It doesn't do it in 3.8.2
> 
> Any idea what changed?  Is it the assumption of what directory the PKG_???
file
> will be installed in?  The post_install script uses
> 
>    files = cstrcat (desc.archprefix, filesep, octave_config_info
> ("canonical_host_type"),
>                    "-", octave_config_info ("api_version"), filesep,
"PKG_???");
> 
> Is that no longer the valid location of the PKG_??? files?  If we just
want a quick
> fix for this problem with 4.1.0+, is there a better way to specify the
location of
> these files?
> 
> It also seems to me that using fullfile would be better than concatenating
with
> filesep, but that's a separate issue.
> 
> jwe
> 

On 3.8.2 it compiled the octfile etc, on 4.1.0 it doesn't.
Looking in configure_make.m, there is a change on the shell call for make:
4.8.2: shell ([scenv "make -C '" src "'"], verbose);
4.1.0: shell (sprintf ("%s make --jobs %i --directory '%s'",
                                         scenv, nproc ("overridable"), src),
                                verbose);

ans = MKOCTFILE="C:\Octave\Octave-4.1.0+\bin\mkoctfile-4.1.0+.exe --verbose"
OCTAVE_CONFIG="C:\Octave\Octave-4.1.0+\bin\oc
tave-config-4.1.0+.exe"
OCTAVE="C:\Octave\Octave-4.1.0+\bin\octave-4.1.0+.exe"
INSTALLDIR="C:\Octave\Octave-4.1.0+\share\o
ctave\packages\io-2.2.6"  make --jobs 4 --directory
'C:\Users\JDONOG~1.ECE\AppData\Local\Temp\oct-sTrdWG\io\src'

ans = MKOCTFILE="C:\Octave\Octave-3.8.2\bin\mkoctfile-3.8.2.exe"
OCTAVE_CONFIG="C:\Octave\Octave-3.8.2\bin\octave-config-3
.8.2.exe" OCTAVE="C:\Octave\Octave-3.8.2\bin\octave-3.8.2.exe"
INSTALLDIR="C:\Octave\Octave-3.8.2\share\octave\packages\io
-2.2.6" make -C 'C:\Users\JDONOG~1.ECE\AppData\Local\Temp\oct-3\io\src'


If I comment out the lines in configure_make.m that append the --verbose
option to makeoctfile, then starts running mkoctfile

On mine however, at that point it sticks on 'mkoctfile cell2csv.cc' forever.
(at least has been for 10 mins now)