On Tue, Nov 08, 2005 at 10:59:22AM +0100, Pascal Bleser wrote: > Using icc will result in having to install icc runtime libraries, at least > for C++. > (see libstdc++ and libgcc for g++)
Wrong. On a Linux system icc uses by default the gcc provided libstdc++ if
installed and the other support libraries can be linked in statically by the
-i-static switch.
> What licenses apply to the runtime libraries ?
"C. Subject to all of the terms and conditions of this Agreement, Intel
grants to you a non-exclusive, non-assignable copyright license to
distribute (except under an Evaluation License as specified below) the
Redistributables, or any portions thereof, as part of the product or
application you developed using the Materials."
Note that all libraries that icc links to by default are "Redistributables".
> On what architectures are they available ?
i586, x86_64, and ia64.
> How well is RPM currently handling building with icc ? (flags, archs, ...)
Huh? RPM does not really care about the compiler you use.
> Needs quite some investigation upfront, IMO.
Technically there is no real problem using this compiler. But you should make
sure yourself whether you comply to this:
"ii. NONCOMMERCIAL-USE LICENSE: If you are using the Materials under the
control of a Noncommercial-Use license, you as an individual may use the
Materials only for non-business use where you receive no fee, salary or
any other forms of compensation. The Materials may not be used for any
other purpose, whether "for profit" or "not for profit." Any work
performed or produced as a result of use of the Materials cannot be
performed or produced for the benefit of other parties for a fee,
compensation or any other reimbursement or remuneration."
Robert
--
Robert Schiele Tel.: +49-621-181-2214
Dipl.-Wirtsch.informatiker mailto:[EMAIL PROTECTED]
pgpgR7Bqv0uOB.pgp
Description: PGP signature
