From owner-freebsd-ports Sun Mar 31 4:20:11 2002 Delivered-To: freebsd-ports@freebsd.org Received: from homeip.net (r96-39.bas1.srl.dublin.eircom.net [159.134.96.39]) by hub.freebsd.org (Postfix) with ESMTP id F399A37B426 for ; Sun, 31 Mar 2002 04:19:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by homeip.net (8.11.6/8.11.6) with ESMTP id g2VCJUD18588; Sun, 31 Mar 2002 13:19:30 +0100 (IST) (envelope-from nick-lists@netability.ie) Subject: Re: lang/icc doesn't compile c++ sources From: Nick Hilliard To: Terry Lambert Cc: ports@freebsd.org In-Reply-To: <3CA67AAD.58C6DC82@mindspring.com> References: <1017539059.24927.1.camel@flapjack.netability.ie> <3CA67AAD.58C6DC82@mindspring.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 31 Mar 2002 14:19:30 +0200 Message-Id: <1017577171.30389.2.camel@flapjack.netability.ie> Mime-Version: 1.0 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [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 "", 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