Re: Package installation trouble

[Tatsuro MATSUOKA]

>On Fri, Jun 19, 2015 at 8:14 PM, Tatsuro MATSUOKA <address@hidden> wrote:
>
>----- Original Message -----
>>>From: Vinicio Serment Moreno
>>
>>>To: Tatsuro MATSUOKA
>>>Date: 2015/6/20, Sat 08:23
>>>Subject: Re: Package installation trouble
>>>
>>>
>>>Thank you Tatsuro, I've performed as you requested by modifiying file 
>>>build_packages.m
>>>
>>>
>>>>> cd C:\Octave\Octave-4.0.0\src
>>> >> build_packages
>>>
>>>
>>>>yields different warnings, and I still get an error with the "make" 
>>>>instruction:
>>>#################################
>>>No such file
>>>make[1]: *** [comp_atrousfilterbank_td.oct] Error 1
>>>make: *** [oct] Error 2
>>>make: Entering directory `/tmp/oct-qxFnXo/ltfat/src'
>>># Compile the backend lib
>>>make -f Makefile_unix
>>>make[1]: Entering directory `/tmp/oct-qxFnXo/ltfat/src'
>>>
>>>
>>>#################################
>>>
>>>
>>>I tried to install the odepkg as you suggested:
>>>>> pkg install -forge -verbose odepkg
>>>
>>>
>>>
>>>and got a long list, where the last lines are read as:
>>>
>>>
>>>###################################
>>>c:/anaconda3/mingw/bin/../lib/gcc/x86_64-w64-mingw32/4.7.0/../../../../x86_64-w64-mingw32/
>>>bin/ld.exe: skipping incompatible C:\Octave\Octave-4.0.0\lib/libmsvcrt.a 
>>>when searching fo
>>>r -lmsvcrt
>>>c:/anaconda3/mingw/bin/../lib/gcc/x86_64-w64-mingw32/4.7.0/../../../../x86_64-w64-mingw32/
>>>bin/ld.exe: skipping incompatible C:\Octave\Octave-4.0.0\lib\libmsvcrt.a 
>>>when searching fo
>>>r -lmsvcrt
>>>collect2.exe: error: ld returned 1 exit status
>>>make: *** [dldsolver.oct] Error 1
>>>make: Leaving directory `/tmp/oct-b72aEZ/odepkg-0.8.5/src'
>>>
>>>
>>>pkg: error running `make' for the odepkg package.
>>>error: called from 'configure_make' in file 
>>>C:\Octave\Octave-4.0.0\share\octave\4.0.0\m\pk
>>>g\private\configure_make.m near line 96, column 9
>>>########################################
>>>
>>
>>Please keep to send reply to octave ML to record discussion between related 
>>people.
>>The records are opened in the  ML archives and the octave Nabble forum 
>>and might be help to other peoples in the future.
>>
>>BTW,
>>From the report pkg -verbose
>>>c:/anaconda3/mingw/bin/../lib/gcc/x86_64-w64-mingw32/4.7.0/../../../../x86_64-w64-mingw32/
>>>bin/ld.exe: skipping incompatible C:\Octave\Octave-4.0.0\lib/libmsvcrt.a 
>>>when searching fo
>>>r -lmsvcrt
>>
>>
>>The pkg system uses msys+MinGW installed in octave folder but not external 
>>MinGW.
>>You environmental variables setting in your PC obviously breaks this.
>>
>>> c:/anaconda3/mingw/bin/../lib/gcc/x86_64-w64-mingw32/4.7.0/
>>
>>MinGW version is 4.9.2 which is bundled with octave-4.0.0 but not 4.7.0 
>>
>>
>>How did you start octave?
>>1. Short cut icon 2. octave.vbs  3. octave.bat 4. octave-gui or octave-cli
>>
>>Short cut icon is pointed to octave.vbs so it is the same as execute octave 
>>via octave.vbs
>>
>>1. 2. are proffered because environmental variable is set properly. 
>>
>>Anyway I would like to confirm for your PATH with in octave 
>>What the below tells?
>>
>>>> system ('sh')      
>>sh-3.1$ echo $PATH
>>
>>Form me, 
>>/usr/bin:(other paths)
>>
>>
>>The first path should be /usr/bin, otherwise your octave fails to set 
>>environmental variable in
>>msys sh shell which is bundled in octave-4.0.0.
>>
>>
>>Tatsuro
>>
----- Original Message -----
>From: Vinicio Serment Moreno 
>To: Tatsuro MATSUOKA  
>Cc: address@hidden
>Date: 2015/6/20, Sat 10:48
>Subject: Re: Package installation trouble
> 
>
>I do start Octave with the .vbs file,
>
>
>#### here is what I get when typing
>>> system('sh')
>sh-3.1
>
>
>#### Then I typed:
>$ echo $PATH
>
>
>#### to get:
>/usr/bin:/c/ProgramData/Oracle/Java/javapath:/c/Program Files 
>(x86)/Silverfrost/FTN95:/c/P
>rogram Files (x86)/Intel/iCLS Client/:/c/Program Files/Intel/iCLS 
>Client/:/c/Windows/syste
>m32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/c/Pro
>gram Files/Intel/Intel(R) Management Engine Components/DAL:/c/Program 
>Files/Intel/Intel(R)
> Management Engine Components/IPT:/c/Program Files (x86)/Intel/Intel(R) 
>Management Engine
>Components/DAL:/c/Program Files (x86)/Intel/Intel(R) Management Engine 
>Components/IPT:/c/P
>rogram Files/MATLAB/R2014a/bin:/c/Program Files 
>(x86)/QuickTime/QTSystem/:/c/Program Files
> 
>(x86)/Skype/Phone/:/c/Anaconda3:/c/Anaconda3/Scripts:/usr/bin:/usr/notepad++:/usr/libexec
>/octave/4.0.0/site/exec/i686-w64-mingw32:/usr/libexec/octave/api-v50+/site/exec/i686-w64-m
>ingw32:/usr/libexec/octave/site/exec/i686-w64-mingw32:/usr/libexec/octave/4.0.0/exec/i686-
>w64-mingw32:/usr/bin
>sh-3.1$
>
I recommend bottom posting on this ML because it is custom in this ML.
When in Rome, do as the Romans do

(https://en.wikipedia.org/wiki/Posting_style)


BTW,
Hmmmmm! I do not find any reason why your octave failed to use mingw gcc in the 
octave folder.

>> getevn('PATH')
tells but I expect that 

ans = C:\octave\Octave-4.0.0\bin;(other paths)


If path is above, I cannot say any further.

>>> c:/anaconda3/mingw/bin/../lib/gcc/x86_64-w64-mingw32/4.7.0/


It seems that anaconda3 ships ver 4.7.0 mingw64 64bit gcc judging from your 
path setting.

Octave-4.0.0 distributed on the octave web site is 32 bit application and your 
octave did not 
use gcc bundled with octave so that your octave fails pkg install.

The solution is that mkoctfile (which is used in pkg install) does use octave 
bundles gcc but 
not that bundles with anaconda3.

One tricky solution to make batch file like the below


Rem trick batch file "octavetrick_gui.bat"
@echo off
PATH=C:\octave\Octave-4.0.0;C:\octave\Octave-4.0.0\bin
octave.vbs --force-gui

Then startoctave using "octavetrick_gui.bat" and try to execute pkg install.

Tatsuro