From owner-freebsd-hackers Thu Jan 24 14:42: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 0D52237B417; Thu, 24 Jan 2002 14:42:04 -0800 (PST) Received: from pool0162.cvx40-bradley.dialup.earthlink.net ([216.244.42.162] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16TsZE-00009T-00; Thu, 24 Jan 2002 14:42:01 -0800 Message-ID: <3C508DB4.E0285E7A@mindspring.com> Date: Thu, 24 Jan 2002 14:41:56 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dan Nelson Cc: Rahul Siddharthan , ports@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Port: Intel Fortran (and C++?) compilers References: <20020124184506.B87867@lpt.ens.fr> <20020124192136.GG87583@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dan Nelson wrote: > This is definitely dependant on what you're building. icc will try and > use the Linux headers, so if you use FILE, or pretty much any system > struct, it's not going to run right. Actually, what might work is "icc > -X -I /usr/include", and then link with the freebsd ld. But icc > doesn't understand all gcc-isms, which is why Intel had to rewrite a > lot of them and put them in intel/compiler50/ia32/substitute_headers. > You'de have to do the same for any offending FreeBSD headers. It's probably a worthwhile exercise to make these conditional on the GCC manifest constant predefines that only show up when you use GCC, so that there aren't unsynchronized copies of everything lying around... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message