octave-4.0.1 64 bit binary for windows is uploaded

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
Hello

In the official release, there is not 64 bit binary for windows.

The testing and unofficial release of 64 bit binary has been uploaded on my web site.

http://www.tatsuromatsuoka.com/octave/Eng/Win/


octave-4.0.1-installer-w64.exe.zip


If the official site will start to distribute 64 bit binary for windows, I will stop distribution here. 

Notes.

1. This binary build with 64 bit environments using 64 bit compilers. 
   But it  does not support "large arrays (lager than c.a. 2GB) ".

2. My web site does not allow to upload files with "exe" extension and thus 
   the exe file is archived in zip. Unzip first and execute installer.

3. Binaries of the octave-forge packages were not included.
   Build by yourself at "src" directory and execute "build_packages" from
   octave prompt.

4. Parallel install 32 bit and 64 bit binary seem to be not allowed.
   For parallel install, you have to do a trick.  
    a. Copy or archive the first installed binaries with keeping directory structures.  
    b. Uninstall the first one.
    c. Install the second one to the directory. Name of install directory name should 
       be different from that of the first one.
    d. Rename copied image to have the original directory name or 
        un-archive archived file and restore the whole directory structures.    

Tatsuro


Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

nitnit
tmacchant wrote
Hello

In the official release, there is not 64 bit binary for windows.

The testing and unofficial release of 64 bit binary has been uploaded on my web site.

http://www.tatsuromatsuoka.com/octave/Eng/Win/


octave-4.0.1-installer-w64.exe.zip


If the official site will start to distribute 64 bit binary for windows, I will stop distribution here. 

Notes.

1. This binary build with 64 bit environments using 64 bit compilers. 
   But it  does not support "large arrays (lager than c.a. 2GB) ".

2. My web site does not allow to upload files with "exe" extension and thus 
   the exe file is archived in zip. Unzip first and execute installer.

3. Binaries of the octave-forge packages were not included.
   Build by yourself at "src" directory and execute "build_packages" from
   octave prompt.

4. Parallel install 32 bit and 64 bit binary seem to be not allowed.
   For parallel install, you have to do a trick.  
    a. Copy or archive the first installed binaries with keeping directory structures.  
    b. Uninstall the first one.
    c. Install the second one to the directory. Name of install directory name should 
       be different from that of the first one.
    d. Rename copied image to have the original directory name or 
        un-archive archived file and restore the whole directory structures.    

Tatsuro
Hello Tatsusro,

Thank you for contributing for the x64 windows installation package.

I have two notes (for now):

1. It seems that the package includes many leftovers from a previous 4.0.1-rc4 build (i.e. share\octave\4.0.1-rc4 subdir, *-4.0.1-rc4.exe files in bin subdir etc). Maybe you have not cleaned up a previous build.

2. src/build_packages.m have
try_install database-2.3.2.tar.gz
instead of
try_install database-2.4.1.tar.gz
which is supplied with the package.

Nitzan
Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
----- Original Message -----

> From: nitnit <[hidden email]>
> To: [hidden email]
> Cc:
> Date: 2016/3/26, Sat 03:13
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
> Hello Tatsusro,
>
> Thank you for contributing for the x64 windows installation package.
>
> I have two notes (for now):
>
> 1. It seems that the package includes many leftovers from a previous
> 4.0.1-rc4 build (i.e. share\octave\4.0.1-rc4 subdir, *-4.0.1-rc4.exe
> files
> in bin subdir etc). Maybe you have not cleaned up a previous build.
>
> 2. src/build_packages.m have
> try_install database-2.3.2.tar.gz
> instead of
> try_install database-2.4.1.tar.gz
> which is supplied with the package.
>
> Nitzan

Nitzan


Thanks for your feedback.
As you said, I did not clean up 4.0.1-rc4.

I will rebuild today and replace it.

Regards

Tatsuro

Reply | Threaded
Open this post in threaded view
|

RE: octave-4.0.1 64 bit binary for windows is uploaded

JohnD
In reply to this post by tmacchant
>
> Message: 7
> Date: Sat, 26 Mar 2016 04:18:02 +0900 (JST)
> From: Tatsuro MATSUOKA <[hidden email]>
> To: Arazi Nitzan <[hidden email]>, "[hidden email]"
> <[hidden email]>
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=iso-8859-1
>
> ----- Original Message -----
>
> > From: nitnit <[hidden email]>
> > To: [hidden email]
> > Cc:
> > Date: 2016/3/26, Sat 03:13
> > Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded Hello
> > Tatsusro,
> >
> > Thank you for contributing for the x64 windows installation package.
> >
> > I have two notes (for now):
> >
> > 1. It seems that the package includes many leftovers from a previous
> > 4.0.1-rc4 build (i.e. share\octave\4.0.1-rc4 subdir, *-4.0.1-rc4.exe
> > files in bin subdir etc). Maybe you have not cleaned up a previous
> > build.
> >
> > 2. src/build_packages.m have
> > try_install database-2.3.2.tar.gz
> > instead of
> > try_install database-2.4.1.tar.gz
> > which is supplied with the package.
> >
> > Nitzan
> >?
>
> Nitzan
>
>
> Thanks for your feedback.
> As you said, I did not clean up 4.0.1-rc4.
>
> I will rebuild today and replace it.
>
> Regards
>
> Tatsuro
>
Mxe-octave build_packages.m is now updated to correct database version



Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

nitnit
In reply to this post by tmacchant
tmacchant wrote
Hello

In the official release, there is not 64 bit binary for windows.

The testing and unofficial release of 64 bit binary has been uploaded on my web site.

http://www.tatsuromatsuoka.com/octave/Eng/Win/


octave-4.0.1-installer-w64.exe.zip


If the official site will start to distribute 64 bit binary for windows, I will stop distribution here. 

Notes.

1. This binary build with 64 bit environments using 64 bit compilers. 
   But it  does not support "large arrays (lager than c.a. 2GB) ".

2. My web site does not allow to upload files with "exe" extension and thus 
   the exe file is archived in zip. Unzip first and execute installer.

3. Binaries of the octave-forge packages were not included.
   Build by yourself at "src" directory and execute "build_packages" from
   octave prompt.

4. Parallel install 32 bit and 64 bit binary seem to be not allowed.
   For parallel install, you have to do a trick.  
    a. Copy or archive the first installed binaries with keeping directory structures.  
    b. Uninstall the first one.
    c. Install the second one to the directory. Name of install directory name should 
       be different from that of the first one.
    d. Rename copied image to have the original directory name or 
        un-archive archived file and restore the whole directory structures.    

Tatsuro
I could build all included octaveforge packages using src/build_packaes.m ecxept nan-3.0.1.tar.gz:

try_install nan-3.0.1.tar.gz
ls: /usr/local/: No such file or directory
linear.cpp: In function 'int save_model(const char*, const model*)':
linear.cpp:1900:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
  for(i=0; i<model_->nr_class; i++)
            ^
linear.cpp: In function 'void get_labels(const model*, int*)':
linear.cpp:2201:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for(int i=0;i<model_->nr_class;i++)
                ^
make: cc: Command not found
make: *** [svm.o] Error 127
make: Entering directory `/tmp/oct-5oUpjV/NaN/src'
C:/Octave/Octave-4.0.1-x64/bin/mkoctfile-4.0.1.exe --mex "histo_mex.cpp"
C:/Octave/Octave-4.0.1-x64/bin/mkoctfile-4.0.1.exe --mex "covm_mex.cpp"
C:/Octave/Octave-4.0.1-x64/bin/mkoctfile-4.0.1.exe --mex "kth_element.cpp"
C:/Octave/Octave-4.0.1-x64/bin/mkoctfile-4.0.1.exe --mex "sumskipnan_mex.cpp"
C:/Octave/Octave-4.0.1-x64/bin/mkoctfile-4.0.1.exe --mex "str2array.cpp"
g++ -fopenmp -Wall -Wextra -Wconversion -O2  -fopenmp  -c tron.cpp
g++ -fopenmp -Wall -Wextra -Wconversion -O2  -fopenmp  -c linear.cpp
env CC=g++ C:/Octave/Octave-4.0.1-x64/bin/mkoctfile-4.0.1.exe --mex -lblas train.c tron.o linear.o linear_model_matlab.c
cc -fopenmp -Wall -Wextra -Wconversion -O2  -fopenmp  -c svm.cpp
make: Leaving directory `/tmp/oct-5oUpjV/NaN/src'

Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
> I could build all included octaveforge packages using src/build_packaes.m

> except nan-3.0.1.tar.gz:


I have re-built a 64 bit binary installer for windows.
http://www.tatsuromatsuoka.com/octave/Eng/Win/


octave-4.0.1-installer-w64-1.exe.zip


As John Donoghue said:
build_package.m has been updated.

http://octave.1599824.n4.nabble.com/octave-4-0-1-64-bit-binary-for-windows-is-uploaded-tp4675849p4675883.html


Now I am installing octave-forge packages by build_package.m
But I have to go home because time for the final bus come soon.

Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
----- Original Message -----

> From: Tatsuro MATSUOKA 
> To: Arazi Nitzan  "octave-maintainers
> Cc:
> Date: 2016/3/26, Sat 22:02
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
>
>>  I could build all included octaveforge packages using src/build_packaes.m
>
>>  except nan-3.0.1.tar.gz:
>
>
> I have re-built a 64 bit binary installer for windows.
> http://www.tatsuromatsuoka.com/octave/Eng/Win/
>
> octave-4.0.1-installer-w64-1.exe.zip
>
> As John Donoghue said:
> build_package.m has been updated.
>
> http://octave.1599824.n4.nabble.com/octave-4-0-1-64-bit-binary-for-windows-is-uploaded-tp4675849p4675883.html
>


I have confirmed that build_packages.m worked successfully on the PC at my home
using 64 bit binary that I have buit.
(Windows 10 Home 64 bit upgraded from windows 7 home 64 bit)


But I have not tested each packages yet.

Does anyone teach me how I can test packages installed?

BTW, I really appreciated for efforts done by who are contributed to the mxe-octave.

Tatsuro

Reply | Threaded
Open this post in threaded view
|

RE: octave-4.0.1 64 bit binary for windows is uploaded

JohnD


> -----Original Message-----
> From: Tatsuro MATSUOKA [mailto:[hidden email]]
> Sent: Sunday, March 27, 2016 4:30 AM
> To: [hidden email]; Arazi Nitzan; [hidden email];
> [hidden email]
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
>
> ----- Original Message -----
>
> > From: Tatsuro MATSUOKA
> > To: Arazi Nitzan  "octave-maintainers
> > Cc:
> > Date: 2016/3/26, Sat 22:02
> > Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
> >
> >>  I could build all included octaveforge packages using
> >> src/build_packaes.m
> >
> >>  except nan-3.0.1.tar.gz:
> >
> >
> > I have re-built a 64 bit binary installer for windows.
> > http://www.tatsuromatsuoka.com/octave/Eng/Win/
> >
> > octave-4.0.1-installer-w64-1.exe.zip
> >
> > As John Donoghue said:
> > build_package.m has been updated.
> >
> > http://octave.1599824.n4.nabble.com/octave-4-0-1-64-bit-binary-for-win
> > dows-is-uploaded-tp4675849p4675883.html
> >
>
>
> I have confirmed that build_packages.m worked successfully on the PC at my
> home using 64 bit binary that I have buit.
> (Windows 10 Home 64 bit upgraded from windows 7 home 64 bit)
>
>
> But I have not tested each packages yet.
>
> Does anyone teach me how I can test packages installed?
>
> BTW, I really appreciated for efforts done by who are contributed to the
mxe-
> octave.
>
> Tatsuro

I use a modified version of the script mentioned here [1] which will test
each package currently loaded.

I have been meaning to update the window compatibility assessment page [2]
built hadn’t gotten around to it yet.

[1]
http://octave.1599824.n4.nabble.com/Unmaintained-packages-becoming-a-maintai
ner-tt4670318.html#a4670455
[2]
http://wiki.octave.org/wiki/index.php?title=Octave-Forge&oldid=6422#GNU_Octa
ve_4.0_compatibility_assessment








Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
In reply to this post by tmacchant
> From: Tatsuro MATSUOKA 

> To: tmacchant Arazi Nitzan  "[hidden email]" ; "john.david.donoghue
> Cc:
> Date: 2016/3/27, Sun 17:30
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
>
> I have confirmed that build_packages.m worked successfully on the PC at my home
> using 64 bit binary that I have buit.
> (Windows 10 Home 64 bit upgraded from windows 7 home 64 bit)
>
>
> But I have not tested each packages yet.


I have executed runtests on the mxe-octave 4.0.1 64 bit.
I have found two issues.


I have filed the both

1. bug #47554 : logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue)
2. bug #47555: Segmentation violation after "runtests" mxe-octave 64bit


For 1., workaround to use the openblas built on windows.
I will upload it later on my web.

Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
> From: Tatsuro MATSUOKA 

> To: tmacchant Arazi Nitzan "octave-maintainers"  "john.david.donoghue" 
> Cc:
> Date: 2016/3/28, Mon 14:36
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded

> I have executed runtests on the mxe-octave 4.0.1 64 bit.
> I have found two issues.
>
>
> I have filed the both
>
> 1. bug #47554 : logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit
> (openblas issue)
> 2. bug #47555: Segmentation violation after "runtests" mxe-octave
> 64bit
>
>
> For 1., workaround to use the openblas built on windows.
> I will upload it later on my web.
>


I have uploaded the OpenBLAS replacement.

http://www.tatsuromatsuoka.com/octave/Eng/Win/


Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
>From: Rafael Monteiro 
>To: Tatsuro MATSUOKA  
>Date: 2016/3/29, Tue 00:07
>Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded

>Thank you very much! :)
>
>
>Some observations (using octave-4.0.1-installer-w64-1.exe.zip):
>- package signal-1.3.2.tar.gz is missing from src directory;
>
>- nan-3.0.1 won't build (same error Nit Nit got).



>- package signal-1.3.2.tar.gz is missing from src directory;


For me, package signal-1.3.2.tar.gz exists in src directory
and it was installed successfully.
Workaround is:

>> pkg install -forge signal

>- nan-3.0.1 won't build (same error Nit Nit got).


I have confirmed. I will file this as a bug.

Thank you for the feedback

Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
> From: Tatsuro MATSUOKA 

> To: Rafael Monteiro ; "[hidden email]
> Cc:

>
>> - nan-3.0.1 won't build (same error Nit Nit got).
>
The error come from no finding cc command.
Perhaps it assume cc is symbolic linked to gcc.
But on native windows (not Cygwin) does not have symbolic link.

Workaound:
Just copy gcc.exe to cc.exe in the bin directory.

Then execute

>> pkg install nan-3.0.1.tar.gz

at src directory 
or

>> pkg install -forge nan

BTW, I have submitted a bug ticket
http://savannah.gnu.org/bugs/?47559


Tatsuro


Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
> From: Tatsuro MATSUOKA 

> To: tmacchant Rafael Monteiro  "octave-maintainers" ; Arazi Nitzan <
> Cc:
> Date: 2016/3/29, Tue 11:49
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded
>
>>  From: Tatsuro MATSUOKA 
>
>>  To: Rafael Monteiro ; "[hidden email]
>>  Cc:
>
>>
>>>  - nan-3.0.1 won't build (same error Nit Nit got).
>>
> The error come from no finding cc command.
> Perhaps it assume cc is symbolic linked to gcc.
> But on native windows (not Cygwin) does not have symbolic link.
>
> Workaound:
> Just copy gcc.exe to cc.exe in the bin directory.
>
> Then execute
>
>>>  pkg install nan-3.0.1.tar.gz
>
> at src directory 
> or
>
>>>  pkg install -forge nan
>
> BTW, I have submitted a bug ticket
> http://savannah.gnu.org/bugs/?47559

http://savannah.gnu.org/bugs/?47559

The above bug report is duplicated to
http://savannah.gnu.org/bugs/?47355


Much better workaround is:

>> setenv CC gcc

before install nan package.

Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
Hello

An issue of OpenBLAS was solved due to efforts by John Donoghue.
(http://savannah.gnu.org/bugs/?47554

I have re-packaged 64 bit binary of octave-4.0.1 for windows and upload to the below
http://www.tatsuromatsuoka.com/octave/Eng/Win/


1. octave-4.0.1-installer-w64-2.exe.zip
2. octave-4.0.1-w64-2.7z
3. octave-4.0.1-w64-2-forge.7z

1. installer
2. 7-Zip archived binary package with pre-built octave-forge packages.
3. 7-Zip archived pre-built octave-forge packages for 1.

Notes for 2 and 3
 Please execute
  >> pkg rebuild
 to refresh package database.

Notes for install package by build_packages.m
1. nan package will fail to install because of lack of cc command octave for windows.
   Workaroung is to execute
    >> setenv CC gcc
   Before execute build_pakcages.

2. I noticed that size of oct and mex files for each package installed by build_packages.m
   is huge because they are not stripped.
   For stripping, execute the below (assume octave is installed to C:\octave\Octave-4.0.1-w64)
    >> cd C:\octave\Octave-4.0.1-w6 4\lib\octave\packages
    >> system bash
   Copy and paste the below to the  bash prompt

strip ./communications-1.2.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./control-3.0.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./database-2.4.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./dicom-0.1.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./fits-1.0.7/x86_64-w64-mingw32-api-v50+/*.oct
strip ./fl-core-1.0.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./general-2.0.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./image-2.4.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./instrument-control-0.2.2/x86_64-w64-mingw32-api-v50+/*.oct
strip ./interval-1.4.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./io-2.4.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./linear-algebra-2.2.2/x86_64-w64-mingw32-api-v50+/*.oct
strip ./lssa-0.1.2/x86_64-w64-mingw32-api-v50+/*.oct
strip ./ltfat-2.1.2/x86_64-w64-mingw32-api-v50+/*.oct
strip ./mapping-1.2.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./miscellaneous-1.2.1/x86_64-w64-mingw32-api-v50+/*.oct
strip ./nan-3.0.1/x86_64-w64-mingw32-api-v50+/*.mex
strip ./netcdf-1.0.9/x86_64-w64-mingw32-api-v50+/*.oct
strip ./nurbs-1.3.10/x86_64-w64-mingw32-api-v50+/*.oct
strip ./ocs-0.1.5/x86_64-w64-mingw32-api-v50+/*.oct
strip ./odepkg-0.8.5/x86_64-w64-mingw32-api-v50+/*.oct
strip ./optim-1.5.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./quaternion-2.4.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./signal-1.3.2/x86_64-w64-mingw32-api-v50+/*.oct
strip ./sockets-1.2.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./sparsersb-1.0.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./specfun-1.1.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./stk-2.3.4/x86_64-w64-mingw32-api-v50+/*.mex
strip ./strings-1.2.0/x86_64-w64-mingw32-api-v50+/*.oct
strip ./struct-1.0.12/x86_64-w64-mingw32-api-v50+/*.oct
strip ./tisean-0.2.3/x86_64-w64-mingw32-api-v50+/*.oct
strip ./tsa-4.4.1/x86_64-w64-mingw32-api-v50+/*.mex
strip ./video-1.2.2/x86_64-w64-mingw32-api-v50+/*.oct
strip ./windows-1.2.3/x86_64-w64-mingw32-api-v50+/*.oct
strip ./zeromq-1.1.0/x86_64-w64-mingw32-api-v50+/*.oct



Tatsuro


Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

John Swensen-3

> On Mar 30, 2016, at 12:40 AM, Tatsuro MATSUOKA <[hidden email]> wrote:
>
> Hello
>
> An issue of OpenBLAS was solved due to efforts by John Donoghue.
> (http://savannah.gnu.org/bugs/?47554)
>
> I have re-packaged 64 bit binary of octave-4.0.1 for windows and upload to the below
> http://www.tatsuromatsuoka.com/octave/Eng/Win/
>
>
> 1. octave-4.0.1-installer-w64-2.exe.zip
> 2. octave-4.0.1-w64-2.7z
> 3. octave-4.0.1-w64-2-forge.7z
>
> 1. installer
> 2. 7-Zip archived binary package with pre-built octave-forge packages.
> 3. 7-Zip archived pre-built octave-forge packages for 1.
>
> Notes for 2 and 3
>  Please execute
>   >> pkg rebuild
>  to refresh package database.
>
> Notes for install package by build_packages.m
> 1. nan package will fail to install because of lack of cc command octave for windows.
>    Workaroung is to execute
>     >> setenv CC gcc
>    Before execute build_pakcages.
>
> 2. I noticed that size of oct and mex files for each package installed by build_packages.m
>    is huge because they are not stripped.
>    For stripping, execute the below (assume octave is installed to C:\octave\Octave-4.0.1-w64)
>     >> cd C:\octave\Octave-4.0.1-w6 4\lib\octave\packages
>     >> system bash
>    Copy and paste the below to the  bash prompt
>
> strip ./communications-1.2.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./control-3.0.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./database-2.4.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./dicom-0.1.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./fits-1.0.7/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./fl-core-1.0.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./general-2.0.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./image-2.4.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./instrument-control-0.2.2/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./interval-1.4.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./io-2.4.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./linear-algebra-2.2.2/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./lssa-0.1.2/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./ltfat-2.1.2/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./mapping-1.2.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./miscellaneous-1.2.1/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./nan-3.0.1/x86_64-w64-mingw32-api-v50+/*.mex
> strip ./netcdf-1.0.9/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./nurbs-1.3.10/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./ocs-0.1.5/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./odepkg-0.8.5/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./optim-1.5.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./quaternion-2.4.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./signal-1.3.2/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./sockets-1.2.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./sparsersb-1.0.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./specfun-1.1.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./stk-2.3.4/x86_64-w64-mingw32-api-v50+/*.mex
> strip ./strings-1.2.0/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./struct-1.0.12/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./tisean-0.2.3/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./tsa-4.4.1/x86_64-w64-mingw32-api-v50+/*.mex
> strip ./video-1.2.2/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./windows-1.2.3/x86_64-w64-mingw32-api-v50+/*.oct
> strip ./zeromq-1.1.0/x86_64-w64-mingw32-api-v50+/*.oct
>
>
>
> Tatsuro
>
>

If OctConf were to give out annual awards for contributions to Octave, I think Tatsuro deserves one for the work done on making sure there are up-to-date Windows installers and packages. Of course there are a ton of other people who also deserve awards, but his work in particular lets me tell a student “Go download and install from this link" and have it “Just work” about 99.8% of the time.

John S.




Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
> From: John Swensen 

> To: Tatsuro MATSUOKA
> Cc: Rafael Monteiro ; "octave-maintainers; Arazi Nitzan  Date: 2016/3/31, Thu 00:50
> Subject: Re: octave-4.0.1 64 bit binary for windows is uploaded

>
> If OctConf were to give out annual awards for contributions to Octave, I think
> Tatsuro deserves one for the work done on making sure there are up-to-date
> Windows installers and packages. Of course there are a ton of other people who
> also deserve awards, but his work in particular lets me tell a student “Go
> download and install from this link" and have it “Just work” about 99.8% of
> the time.
>
> John S.
>

I feel honored for your recommendation. 

However, my distributions can be done owing to the great mxe-octave build system.
Efforts of John W. Eaton, John David Donoghue, and Philip Nienhuis on mxe-octave system 
are much greater than me. Especially John David Donoghue's successive and 
extensive contributions to the system should be praised.

Tatsuro 

Reply | Threaded
Open this post in threaded view
|

Re: octave-4.0.1 64 bit binary for windows is uploaded

tmacchant
Hello

I have uploaded octave for windows with supporting large arrays.

http://www.tatsuromatsuoka.com/octave/Eng/Win/


1. octave-4.0.1-LA.7z -- 7-Zip archived binary package
2. octave-4.0.1-LA-forge.7z -- 7-Zip archived pre-built octave-forge package for 1.


Note that large arrays supports is now experimental so that 
one may meet unexpected bugs.

I describe the contents in readme.txt included in octave-4.0.1-LA.7z

*** readme.txt ****
This is an experimental binary with Large Arrays supports [1, 2].

This binary is produced using mxe-octave with --enable-windows64 and --enable-64 options.
You have to use this on 64 bit windows OS.

An easy test whether large array facility works on your PC [1].

>> a = zeros (1024*1024*1024*3, 1, 'int8');

If condition is not fullfiled, you see
error: memory exhausted or requested size too large
       for range of Octave's index type --
       trying to return to prompt

Error noticed that I have awared at present.
 The build_packages.m scripts fails to build image, odepkg, netcdf, and sparsersb packages in 
 producing oct files.
 This means that some functionalities may not work correctly. 
 See "octave-4.0.1-LA_bpl.log" to see what happened in building packages processes.

No Warranty
 Please use this binary at your own risk.

Feedback
 Feedback is welcome to the octave mailing list[3, 4, 5] or the bug tracker[6].

[1] http://www.gnu.org/software/octave/doc/v4.0.1/Compiling-Octave-with-64_002dbit-Indexing.html
[2] http://wiki.octave.org/Enable_large_arrays:_Build_octave_such_that_it_can_use_arrays_larger_than_2Gb.
[3] https://lists.gnu.org/mailman/listinfo/help-octave
[4] https://lists.gnu.org/mailman/listinfo/octave-maintainers
[5] http://octave.1599824.n4.nabble.com/
[6] https://savannah.gnu.org/bugs/?group=octave
*** readme.txt ****

Tatsuro