Fortran Compiler installation problem

[postaquestion]

I am using 64-bit Mandriva 2008 Linux on a QX6800 system. When I try to install Intel Fortran the 32-bit fc compiler installs but the 64-bit fce compiler doesn't. An fce/10.1.013 directory is created but is empty.

Using OpenMP, I then seem to hit a 2 MB ceiling on thread size, which is really getting in my way. A friend running fce on SUSE Linux on a similiar system has no such problems with my code.

Could you point me in a direction that might help me resolve these problems?

[Steven_L_Intel1]

I would suggest reporting the install issue to support.

You may need to set the thread stack size higher by defining the environment variable KMP_STACKSIZE to a value such as "16m" (means 16MB), etc. See the compiler's OpenMP documentation for more details.

[Jose_Luis_Martins]

I had the same problem. I edited the /etc/mandriva-release file to pretend that it was a mandriva 2007 system.
As I had all the libraries in place it installed the 64-bit version without problem.

[mandriva64_icc]

Quoting - jlmartins@inesc-mn.pt

I had the same problem. I edited the /etc/mandriva-release file to pretend that it was a mandriva 2007 system.
As I had all the libraries in place it installed the 64-bit version without problem.

I successfuly installed the latest release of icc (C++, for IA32 and Intel 64) on Mandriva 2009.0 x86_64 thanks to http://bohr.inesc-mn.pt/~jlm/intel-mandriva.html . On the other side, I had no problem for installing icc (C++, for IA32) on Mandriva ONE 2009.0 (32 bit).

A solution (for Intel) seems to modify the install_cc.sh file in order to consider Mandriva 2008 and earlier as "not supported" (or "supported" if applicable) instead of as "Unknown", something like that. I didn't succeed to contact the support on that topic. Could an Intel employee report that feedback to the support for us ?

Thank you in advance (for all the people who want to install icc on recent Mandriva Linux distributions)

[Ron_Green]

Quoting - mandriva64_icc

I successfuly installed the latest release of icc (C++, for IA32 and Intel 64) on Mandriva 2009.0 x86_64 thanks to http://bohr.inesc-mn.pt/~jlm/intel-mandriva.html . On the other side, I had no problem for installing icc (C++, for IA32) on Mandriva ONE 2009.0 (32 bit).

A solution (for Intel) seems to modify the install_cc.sh file in order to consider Mandriva 2008 and earlier as "not supported" (or "supported" if applicable) instead of as "Unknown", something like that. I didn't succeed to contact the support on that topic. Could an Intel employee report that feedback to the support for us ?

Thank you in advance (for all the people who want to install icc on recent Mandriva Linux distributions)

We have been having discussions interally on two topics: the checking of GCC and Kernel versions, and the checking of supported/unsupported/unknown distro checking.

First, a little context: the checks were put in because prior products did not do much checking. So in the past, we had a LOT less issues related to installation, but a substantally larger number of issues where the user really did not have the prereqs and the compilation would fail. So it's a balance of "catch it now" or "catch it later". The "catch it later" issues require substantially more time from engineering support staff.

Distro checks: Yes, I agree with you that perhaps 2 categories would suffice: "supported" and "unsupported". "unsupported" should allow the install to continue with a WARNING that this may not work and is unsupported (and assuming that the GCC and Kernel checks passed).

GCC/prereq checking: We have a matrix of supported Linux distros and versions, as listed in our ReleaseNotes for each compiler update. We try our best to make the installer recognize and work with as many distros as possible. It's a constant game of catch up. We are leaning towards an option to ignore and install along with the interactive message warning that we can't find the prereqs but install anyway. Or perhaps an install script with vars up at the top that could be user edited to point the various prereq paths.

We should have improvements coming along in a future update. But we are very aware of the issues here and are working on improvements.

ron