Date: 31 Mar 2002 14:19:30 +0200 From: Nick Hilliard <nick-lists@netability.ie> To: Terry Lambert <tlambert2@mindspring.com> Cc: ports@freebsd.org Subject: Re: lang/icc doesn't compile c++ sources Message-ID: <1017577171.30389.2.camel@flapjack.netability.ie> In-Reply-To: <3CA67AAD.58C6DC82@mindspring.com> References: <1017539059.24927.1.camel@flapjack.netability.ie> <3CA67AAD.58C6DC82@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[cc: trimmed to ports] On Sun, 2002-03-31 at 03:55, Terry Lambert wrote: > Actually, when you install the Linux devtools, then what you > get is a Linux binary search path inserted first. This is > actually the *wrong* thing, if what you want is to use the > compiler to generate native FreeBSD binaries. I'm aware of this. However, by default, the icc compiler appears to generate linux binaries when compiling C files. I had assumed that this was the intended behaviour. > Probably, it would be best to handle the warnings, each on a > case-by-case basis. > > Unless what you really want is to generate Linux binaries on > FreeBSD? Ideally not. However, the Makefile and patches for the port don't contain the sort of gnarliness I would expect them to have in order to fix the compiler up to produce freebsd binaries. > I think this is just a "sed" path that is supposed to be replaced > during the installation. This is a probably bug in the FreeBSD > install replacement, rather than an Intel bug. Actually, it looks very much like an intel bug. They just do a straight replacement on "<INSTALLDIR>", which means that the csh script will be left with the "=". Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1017577171.30389.2.camel>