Date: Wed, 27 Mar 2002 17:22:07 +0100 (CET) From: Alexander Leidinger <Alexander@Leidinger.net> To: jmallett@FreeBSD.ORG Cc: green@FreeBSD.ORG, sw@anthologeek.net, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/lang Makefile ports/lang/icc Makefile distinfo pkg-comment pkg-descr pkg-plist ports/lang/icc/files patch-include Message-ID: <200203271622.g2RGM7h3075540@Magelan.Leidinger.net> In-Reply-To: <20020327153610.GB7219@FreeBSD.ORG>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 Mär, J. Mallett wrote: >> But the Linux kernel isn't icc compilable too, so it's not that much of >> a drawback... >> > > Read the article Intel did about porting Mach (and then Linux) to IA64 using > icc initially on pre-silicon. They outline a lot of the things they had to > do to make Linux build with icc, I seem to recall. In general it's the same > stuff we all know anyway, but the point is they were able to do it, and I > *THINK* they may have even included manhour figures, which could be useful if > someone were to look into doing something similar for FreeBSD. I don't wanted to imply it isn't possible. I just had said what I read somewhere on www.intel.com at the time I downloaded icc (last year). It was mainly because of some gcc attributes which aren't supported by icc. I just startet a LINT compile (-current as of ~2 hours ago) with icc, expect the compile log to appear at http://www.leidinger.net/FreeBSD/ as soon as it finishes. I also will include a list of generated object files at the end of the log. Bye, Alexander. -- The dark ages were caused by the Y1K problem. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203271622.g2RGM7h3075540>