Nick Hilliard wrote:
> > --- bad Sat Mar 30 05:18:02 2002
> > +++ good Sat Mar 30 05:18:23 2002
> > @@ -1 +1,2 @@
> > -echo '#include<iostream>' > comp.cc
> > +echo '#include <iostream>' > comp.cc
> > +echo 'main() {}' >> comp.cc
>
> glibness aside, this doesn't work either:
Works with g++... though I expect "glib-ness"... ;^)...
> "/usr/include/stdlib.h", line 57: error: invalid combination of type specifiers
> typedef _BSD_WCHAR_T_ wchar_t;
This seems to be a problem with the wchar_t being intrinsic,
and defined anyway for the compiler.
> [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.
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.
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?
> 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=<INSTALLDIR>/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.
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.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
