From owner-freebsd-ports Sat Mar 30 17:45: 4 2002 Delivered-To: freebsd-ports@freebsd.org Received: from homeip.net (r96-12.bas1.srl.dublin.eircom.net [159.134.96.12]) by hub.freebsd.org (Postfix) with ESMTP id C0C7937B416; Sat, 30 Mar 2002 17:44:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by flapjack.netability.ie (8.11.6/8.11.6) with ESMTP id g2V1iI398301; Sun, 31 Mar 2002 02:44:18 +0100 (IST) (envelope-from nick-lists@netability.ie) Subject: Re: lang/icc doesn't compile c++ sources From: Nick Hilliard To: tlambert2@mindspring.com Cc: hackers@freebsd.org, ports@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 31 Mar 2002 03:44:18 +0200 Message-Id: <1017539059.24927.1.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 > --- bad Sat Mar 30 05:18:02 2002 > +++ good Sat Mar 30 05:18:23 2002 > @@ -1 +1,2 @@ > -echo '#include' > comp.cc > +echo '#include ' > comp.cc > +echo 'main() {}' >> comp.cc glibness aside, this doesn't work either: flapjack:/home/nick> echo '#include ' > comp.cc flapjack:/home/nick> echo 'main() {}' >> comp.cc flapjack:/home/nick> icc comp.cc comp.cc: "/usr/include/stdlib.h", line 57: error: invalid combination of type specifiers typedef _BSD_WCHAR_T_ wchar_t; [piles more warnings chopped This, of course, indicates nothing more than that the linux_devtools package hasn't been installed: a simple "pkg_add -r linux_devtools" appears to fix the problem. The devtools package should be included on the port dependency list to fix it properly. Also, the intel folks don't seem to understand csh syntax very well, according to the last line of compiler50/ia32/bin/iccvars.csh, which states: > setenv INTEL_FLEXLM_LICENSE=/licenses Oops - that should have been caught by QA. Unfortunately, this file is modified by pre-patch:, which means that a simple patch won't do the trick if people decide to install the port in a different location. Hmmm. I've mailed gnats about both of these problems, and have included suggested fixes for each. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message