Ebuild for IFC 8.0.034 Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Properly emerges IFC 8.0
Created attachment 22045 [details] Ebuild for IFC 8.0.034
Created attachment 22046 [details] /usr/portage/dev-lang/ifc/files/8.0.034/05icc-ifc
Created attachment 22047 [details] /usr/portage/dev-lang/ifc/files/8.0.034/ifc
Created attachment 22048 [details] /usr/portage/dev-lang/ifc/files/8.0.034/ifort Starting with 8.0, the binary driver for IFC is no longer called "ifcbin", rather it is "ifortbin". This file fixes the "ifort" script located in the bin/ directory to do the same thing that the ifc script does.
Created attachment 22050 [details] Fix for old environment variable file
Created attachment 22173 [details] Updated Ebuild for IFC Fixes path to /opt/intel/compiler80
Created attachment 22174 [details] /usr/portage/dev-lang/ifc/files/8.0.034/05icc-ifc
Created attachment 22175 [details] /usr/portage/dev-lang/ifc/files/8.0.034/ifc
Created attachment 22176 [details] /usr/portage/dev-lang/ifc/files/8.0.034/ifort
Created attachment 22177 [details] /usr/portage/dev-lang/ifc/files/8.0.034/05icc-ifc Fixes path error
Created attachment 22179 [details] New IFC 8.0 ebuild Fixes path typo.
Created attachment 22353 [details] IFC 8.0.034 Ebuild with support for conf.d configuration file This ebuild now installs into /etc/conf.d a file called "iccifc" which contains compiler flags and settings for the ICC and IFC compilers for use in ebuilds.
Created attachment 22354 [details] /usr/portage/dev-lang/ifc/files/8.0.034/iccifc /etc/conf.d configuration file which contains ICC & IFC compiler settings for use in ebuilds.
Created attachment 22415 [details] /usr/portage/dev-lang/ifc/files/8.0.034/iccifc.conf This file replaces the iccifc configuration file, and now exists as /etc/iccifc.conf.
Created attachment 22416 [details] IFC 8.0.034 Ebuild with modified configuration file support
Sorry about it being in LiveCD. I have moved it to Gentoo Ebuilds.
Created attachment 23740 [details] ebuild Changed the following lines of code in the ebuild: < for FILE in $(find $SD/bin/ -regex '.*[ei][cf]p?c$\|.*cfg$\|.*pcl$\|.*vars[^/]*.c?sh$' 2>/dev/null) < do < sed s@\<INSTALLDIR\>@$RD@g ${FILE} > ${FILE}.abs < mv -f ${FILE}.abs ${FILE} < chmod 755 ${FILE} < done > for FILE in $(grep -l "<INSTALLDIR>" *) > do > sed s@\<INSTALLDIR\>@$RD@g ${FILE} > ${FILE}.abs > chmod --reference=${FILE} ${FILE}.abs > mv -f ${FILE}.abs ${FILE} > done for proper handling of file permissions.
Created attachment 24021 [details] ebuild - cleaned up the ebuild - fixed some `untagging` related stuff - removed dependency on virtual/linux-sources still wondering if their should be a seperate ebuild for the intel debugger since it is also contained in the icc tarball. currently the debugger is not installed at all.
Hi.. is there a reason why this still isnt in portage? I'm using it now since months without problems till now - and icc is already at the 8.0-level..
could you make it depend on rpm2tgz instead of rpm?
Unfortunately rpm2targz is much, _much_ slower than using the RPM eclass. We're talking exponentially...
"rpm2targz is much, _much_ slower" Are you sure... genlop -t rpm: app-arch/rpm-4.2.1 -- merge time: 10 minutes and 48 seconds app-arch/rpm-4.2.1 -- merge time: 9 minutes and 58 seconds versus 5 runs of "time rpm2targz intel-ifort8-8.0-40.i386.rpm": real 0m23.882s user 0m17.470s sys 0m1.470s real 0m24.262s user 0m17.540s sys 0m1.500s real 0m24.008s user 0m17.570s sys 0m1.450s real 0m23.740s user 0m17.580s sys 0m1.570s real 0m22.783s user 0m17.580s sys 0m1.450s Looks to me like rpm2targz is faster for me -- If i am off base on what you were speaking to, please correct me :)
There are a couple of flaws in that. First, you need to unpack the tarball after you run rpm2targz on it. Second, you make the assumption that the only time-consuming step in emerging it is the unpacking.
So why is it that the icc ebuild is now using rpm2tgz?
Just wonder, why it is not yeat in the portage? Will we have this version or will wait untill IFC 12.0 ? :) I guess anyway all, whos use IFC, use this ebuild in local overlay. Just because linking of bilingual programs (C and Fortran) can be a headache when version of IFC and ICC different.
I put the provided ebuild file in /usr/portage/dev-lang/ifc. after emerge ifc I then had to do ebuild ifc-8.0.034.ebuild digest then do emerge ifc again. Then I created a 06ifc file in /etc/env.d with contents: PATH="/opt/intel/compiler80/bin/" LDPATH="/opt/intel/compiler80/lib" NLSPATH="/opt/intel/compiler80/lib/" MANPATH="/opt/intel/compiler80/man" finally I had to make a symb link from /opt/intel/compiler80/lib/ifcore_msg.cat to /usr/lib And THEN it worked. I think the ebuild file needs some more work.
I put the provided ebuild file in /usr/portage/dev-lang/ifc. after emerge ifc I had to do ebuild ifc-8.0.034.ebuild digest then do emerge ifc again. Then I created a 06ifc file in /etc/env.d with contents: PATH="/opt/intel/compiler80/bin/" LDPATH="/opt/intel/compiler80/lib" NLSPATH="/opt/intel/compiler80/lib/" MANPATH="/opt/intel/compiler80/man" finally I had to make a symb link from /opt/intel/compiler80/lib/ifcore_msg.cat to /usr/lib And THEN it worked. I think the ebuild file needs some more work. Too much manual tweaking right now.
WONTFIX, i won't work on ifc < 9.