Installing ifort 9.1.052 on Mint 10 KDE (Kubuntu 10.10)

[Matthias_Jerg]

Installing ifort 9.1.052 on Mint 10 KDE (Kubuntu 10.10)

---

Hello,
I am trying to install ifort 9.1.052 on Mint 10 which is essentially Kubuntu 10.10. I need to use ifort 9.1 because of the requirements of the software I need to compile. When I downloaded ifort I received a license file and a serial number however this was when I first entered to download the latest version. I then navigated to the older ifort versions and chose the above version. I tried to follow now the hints to install ifort on ubuntu as muc has I could identify how far they apply to me. However, the compiler won't install. Either my license file is rejected as invalid or if I try to install by serial number I get the error message:
secore: relocation error: /usr/lib32/libnss_mdns4_minimal.so.2: symbol strlen, version GLIBC_2.0 not defined in file libc.so.6 with link time reference

and the installation stops. I try to install as root.
Any help or other sources of information you can point me to is highly appreciated.

Thanks,

Matt

[TimP]

There's a note at the top of the forum about installing 11.x on Ubuntu; you would need compatibility libraries at least as old as those described there. I suspect you need the 32-bit libc.so.5, but I don't know if you'll find one compatible with such a new distro. You would definitely need a 32-bit libstdc++ no newer than the -33 version.
As far as the license is concerned, you can bypass the on-line serial number check by use of a copy of the license file, and the current license should be OK for the older ifort.
If the software has some peculiarity which prefers the old ifort, it might be preferable to resolve that.

[Ron_Green]

I don't want to say "it will never work" but ...

even if you are able to get 9.1.052 installed, I don't think it will work. I just tried a 9.1.052 compiler NFS mounted to my Ubu 10.10 host. the compiler won't run. The glibc this was built against years ago is just incompatible with the modern glibc on Ubu 10.10. The 9.1.052 compiler was released back in October 2007 and built against glibc of that era. The new ones are just not backwards compatible.

If you REALLY need to use the old 9.1.052 compiler, the quickest path is to install a really old distro that was supported by 9.1.052. A list is in the Release Notes but I've copied it here (these are some real dinosaurs - predating Ubuntu):

Red Hat* Enterprise Linux 3, 4
SUSE* LINUX 9.1 Professional
SUSE LINUX Enterprise Server 9, 10
Fedora* Core 4

Anything newer and no guarantees it will work.

[mecej4]

I need to use ifort 9.1 because of the requirements of the software I need to compile

There can be other problems if you try installing RH3 or RH4 (or a derivative such as Fedora) of that vintage. The old OS may not provide drivers for many of your new hardware components. RH4 and Ubuntu are different generations, after all.

In view of all the obstacles to getting a considerably older version to work properly on a current operating system, as outlined above, I think that it is appropriate to question this perceived requirement.

Generally, Intel Fortran can compile old (yes, even Fortran II, perhaps with a little polishing up) code. The question, then, is: What specific requirements force you to use Version 9.1? What if it turns out that Version 12.0 satisfies those requirements?

I think that it is worth your time to try out a current version of the compiler before you start retro-fitting your software setup.

[Matthias_Jerg]

Hello everybody,

thank you very much for your thoughtful replies. You all raised a lot of really good points. As a matter of fact, I haven't tried to compile with a new version, the installation instructions just claim that that it won't work with anything newer than ifort 9.1. I totally agree with the above statement that there might be other issues if an old OS is tried or the software is installed on old hardware even (which I don't have anyway). I will try to install the latest ifort and report back on how that went and hopefuly go from there. However, I will have to use a fairly complex research code (which is quite resource hungry), so if that is for some reason incompatible with a recent ifort, it would be tough to chase the problem through the code.

Thanks

Matthias