Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Jan 2002 14:41:56 -0800
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Dan Nelson <dnelson@allantgroup.com>
Cc:        Rahul Siddharthan <rsidd@online.fr>, ports@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject:   Re: Port: Intel Fortran (and C++?) compilers
Message-ID:  <3C508DB4.E0285E7A@mindspring.com>
References:  <20020124184506.B87867@lpt.ens.fr> <20020124192136.GG87583@dan.emsphone.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C508DB4.E0285E7A>