> icc users:
>
> Aparently support for icc isn't complete. Here is where
> you can help by submitting a patch that fixes the problems
> you're running into. I don't have access to this compiler,
> so if it is something you want, you'll have to volunteer to
> do it. Please read http://www.gnu.org
I'am the author of the icc-patch, but I dont subscribe to [EMAIL PROTECTED]
(maybe I should) so please CC me in any icc-issues.
Try to add /opt/intel/compiler70/ia32/bin to you PATH and run configure with
CC=icc CXX=icpc. I do a check on whether $CC=icc, and I am not sure it all
the path-inform
Hi Robert
Here's an update on my icc-patch
I have checked how my patch works from CVS HEAD now against icc 7.0. It
finally seems Intel with version 7.0 has made a usefull standard C++ library.
I have even be able to compile at full working KDE-suite.
Libtool CVS just need to following addition
Hi again
I looked a bit a your CVS-repository and have updated my patch so it applies
cleanly against it. I have also resolved the remaining issues with the patch,
so it now works in all tested cases and doesnt interfere with other ports.
I hope you find the patch to your satisfaction and chos
Hi.
I made a patch for supporting Intel's C and C++ compiler against
libtool.m4.in in KDE-CVS, but I was told we more less used libtool from your
cvs, and I therefore should go to the source.
I have attached the patch (I hope it applies) If you have questions or
comments please CC me since I
