From owner-freebsd-ports Mon Dec 9 14:19:36 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C13637B401; Mon, 9 Dec 2002 14:19:35 -0800 (PST) Received: from newtrinity.zeist.de (newtrinity.zeist.de [193.111.112.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FC4243EC2; Mon, 9 Dec 2002 14:19:34 -0800 (PST) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) by newtrinity.zeist.de (8.12.6/8.12.6/ZEIST.DE) with ESMTP id gB9MJWhN051699; Mon, 9 Dec 2002 23:19:32 +0100 (CET) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.6/8.12.6/Submit) id gB9MJRuB051698; Mon, 9 Dec 2002 23:19:27 +0100 (CET) (envelope-from marius) Date: Mon, 9 Dec 2002 23:19:27 +0100 From: marius@alchemy.franken.de To: "Oneill, John J" Cc: "'netchild@FreeBSD.org'" , "'ports@FreeBSD.org'" Subject: Re: FreeBSD Port: icc-6.0.1.304 Message-ID: <20021209231927.A51152@newtrinity.zeist.de> References: <2B4461BF89BAD511A86100508B66D538060E64A7@fmsmsx112.fm.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <2B4461BF89BAD511A86100508B66D538060E64A7@fmsmsx112.fm.intel.com>; from john.j.oneill@intel.com on Mon, Dec 09, 2002 at 10:58:08AM -0800 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 On Mon, Dec 09, 2002 at 10:58:08AM -0800, Oneill, John J wrote: > Hi, > > The Intel 7.0 compilers added an option for -dynamic-linker to support > FreeBSD. 7.0 compilers have recently become available, and I was wondering > if you are able to directly generate executables. Are there other features > that would enhance using the Intel compilers under FreeBSD ? FYI - I work Hi! The dynamic linker is just one problem when generating native FreeBSD binaries among the other hardcoded options icc passes/passed to the linker. The real problem are the libraries, the shared ones don't work though it works quite well with modified static icc libraries. However the Dinkumware STL is completely unusable on FreeBSD due to the entire different ctype implementation on FreeBSD, we use STLport instead. All in all quite hackish but works. The WIP icc7-port even works better due to fixes from Intel and port-patches to fit the icc-headers better for FreeBSD. Have a look at the icc6-port to get an idea of the hacks and modifications in order to produce native FreeBSD binaries. The ifc6-port recently also was modified in a similar way (and thus switched from producing Linux binaries to FreeBSD ones). > for the Intel compiler support team. > Great, can you say something about the likelihood of a native FreeBSD version of the compilers by Intel ? Personally I'd really buy it! Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message