Compiling GNU Octave 3.4.2

[bredsj]

It is described inhttp://software.intel.com/en-us/articles/using-intel-mkl-in-gnu-octave/how to build GNU Octave 3.2.x. The file configure.in must be edited and then autoconf is used to create the configure file.

However, I need to build octave 3.4.2 as the latest io package require >3.4. In the 3.4.2 there is no configure.in (only configure.ac which is used with autoconf) with a different structure than that described in the above article, so I can't implement the changes in the article. For a green belt like me it is a bit difficult to figure out all the nuances so I'll appreciate some guidance.

I am using Ubuntu 11.04 Natty on a 64 bit system.

Perhaps this thread belongs on the MKL Forum?

Thanks in advance.

[Victor_Gladkikh]

Hi

You can skip "update configure" and "run autoreconf" steps. It affects only DFT performance.

Victor

[huang__astone]

Same here. Thanks for the info.

Now I'm getting an error while configuring: to build Octave, the C++ to Fortran calling convention must be known.

Any ideas?

EDIT

Sorry, this was for octave 4.2.0, I guess it's off topic then...

[TimP]

On linux, the Intel C++ to Fortran calling conventions are the same as between g++ and gfortran.  Perhaps you could build with those and then copy over the configuration to use with Intel compilers.

As the preceding posts indicate, it seems the main objective is to use MKL, which could be done with g++ and gfortran.  Then the topic would clearly belong on MKL forum.

I'm guessing the only difference between gnu and Intel compiler configuration would be in the choice of OpenMP library and corresponding MKL parallel libraries.  That difference could be eliminated by linking with Intel libiomp5 even when gnu compilers are used.  The Intel MKL link advisor applet may be needed as a reference in either case.

Ubuntu 64-bit throws in a bit of uncertainty as they have changed their library organization from year to year.  This does make it difficult for anyone who is not an expert on Ubuntu, and could cause posted advice to be out of date.