Installing idb in Fedora Core 6

[nav211]

Hi,
I am new to Linux and Fortran. Can the Intel Fortran compiler 9.1 be used in FC6. When I try installing the compiler installs but the debugger fails. I am thinking I'll probably have to go back to FC5, but I still wanted to check.
Thanks,
Navneet

[umar]

Hi,

FC5 has the same problem. The problem is that a library used by idb is
an older version than the one that comes with FC5 and FC6. This is the
libXft.so library. The installed one is libXft.so.2 whereas the idb needs
libXft.so.1. There is practically no difference between the two libraries.

Solution: Find the idb rpm you want to install under the data/ directory.
Install it using the "rpm -Uvh --nodeps --force WhatEver.rpm". This
installs under /opt/intel which is the default if you had been accepting
the defaults normally. Than switch to /usr/lib and do
ln -s libXft.so.2 libXft.so.1
to logically link the libraries. At this point there is one more thing to do
which is to go the bin/ directory of intel ifort installation and do a grep
on INSTALL or something like that. Since you manually installed the rpm
some of the idb scripts have PATH= or something similar, which
you should replace by /opt/intel/bin for default or whatever your path is.

Ironically the x86_64 versions for FC5 and Fc6 does not have this problem
since their build machine must have the same version of LibXft.so.

Umar

[nav211]

Thanks Umar.
I was able to install the debugger and link the libraries. Can you please elaborate on what "grep on INSTALL" means. I edited the ibdvars.sh script files but I am having trouble adding the source command to the login script. I am not on my PC right now therefore I cant paste the code from idbvars.sh. I will do that when I get home.

Again, really appreciate your help.

Navneet

[umar]

Hi,

Just make sure the PATH (and perhaps MANPATH) point to the bin
directory where the idb binaries are (usually the same directoty).
When you install it by force using rpm the PATH usually has a dummy
destination, which I don't exactly remember what it was called, like
INSTALLDIR. So, just doing the above it good enough.

Umar

[joseph-krahn]

If you run the install script and select the "Custom Install" option, it lets you override the rpm options, but will still do the correct post-install stuff for you.

If the RPMs were designed right, the post-install scripts would be built into the RPM package. The drawback is that RPMs are not set up for "interactive installation", so it would also require some configure scripts for setting up the license information.