i would be very happy to have a newer version of ifc in portage. the latest one currently is 10.0.023... it seems that the 9.1.040 ebuild needs some non-trivial modifications to work with 10.0.x... if you want me to do them, just tell me, and i will see what i can do.
Created attachment 126238 [details] Modified ebuild
Created attachment 126239 [details] env file for ifc; has to go into files/10.0
I struggled with the same problem and modified the 9.1.040 ebuild to work for 10.0.x . This is my first ebuild, so please bear with me if there are gross flaws in it. I only checked its validity for the 32bit version of ifort, it might still be broken for 64bit. In addition, ifortvars.sh has changed, I modified the env.d file file accordingly and also attached it. If this is to go into portage, then the license also has to be added and changed within the ebuild; I must admit, I didn't check if there were nontrivial changes in it.
Uuups, just spotted a typo; should be "INTEL_LICENSE_FILE" in 05ifc...
well, the ebuild (ifc-10.0.023) seems to work fine for me on amd64 - except for the fact that revdep-rebuild says: " Checking dynamic linking consistency... broken /opt/intel/fortran100/bin/idb-e (requires libstdc++.so.5) broken /opt/intel/fortran100/lib/libomp_db.so (requires libstdc++.so.5) "
This linking breakage can be resolved by emerging libstdc++-v3 as the 64bit version seems to rely on the GCC3 version of libstdc++. Odd, since the 32bit version has no such dependency :) At least the 32bit version of idb is also broken by expecting version 1x of libxft, whereas portage only offer 2x nowadays. You can work around this by creating a symlink like libxft.so.2 somewhere pointing to the v2 library and pointing LD_LIBRARY_PATH there. This will allow idb to start and work, but the graphical frontend still doesn't work, the old version really is needed for this. Therefore, the idb part should be separated into another ebuild that works around this stuff, I will see if I can find time these days to find and try out a workaround and split the ebuilds (and if I do, then I'll also add a dependency on libstdc++-v3 for the 64bit version).
Now in cvs. Thanks.
