New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump octave version to 4.2.1 #2002

Closed
jgillis opened this Issue May 12, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@jgillis
Member

jgillis commented May 12, 2017

Blocked by missing information.

As of octave version 4.2, the structure of the octave binaries changed for windows: there are now 2 flavours, using 32 and 64 prefixes.
It's not clear to me how these new downloads map to the 3 octave-crossbuild configurations documented at http://wiki.octave.org/Continuous_Build: w32-on-debian , w64-32-on-debian , w64-64-on-debian

Does the 32 prefixed download correspond to w32-on-debian or to w64-32-on-debian?

@jgillis jgillis self-assigned this May 12, 2017

@jweaton

This comment has been minimized.

jweaton commented May 12, 2017

The configuration for the buildbot builds is as follows:

w32: 32-bit Windows, so 32-bit pointers and limited to 32-bit indexing. You can only allocate up to about 4GB total memory because of the limit imposed by using 32-bit pointers. This is distributed as the w32 binary on ftp.gnu.org.

w64-32: 64-bit Windows, so 64-bit pointers, allowing larger memory allocation, but limited to 32-bit indexing in Octave. This allows arrays up to about 2^31 elements, so for a double precision array, that requires about 16GB of memory. This is distributed as the w64 binary on ftp.gnu.org.

w64-64: 64-bit Windows and 64-bit indexing. We're not distributing this one as a binary release.

@jgillis

This comment has been minimized.

Member

jgillis commented May 19, 2017

Bump finished

@jgillis jgillis closed this May 19, 2017

@jaeandersson jaeandersson added this to the Version 3.2 milestone May 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment