From: Jeff Holle (jeff.holle_at_[hidden])
Date: 2004-02-10 19:16:39
In doing more research, I found how to fix this problem.
The offensive line is boost/tools/build/v1/intel-win32-tools.jam line 87.
I simply commented it out.
Another thing recommended is suppression of warning 167. It is emitted
520 times during the boost build. Always associated with use of
Appending "/Qwd167" to line 42 of intel-win32-tools.jam fixed this.
Now the only problem is the link stage of all dll builds appear to have
failed because the symbol __declspec(dllimport) is reported as an
The interesting thing, to me at least, is this isn't a problem with the
intel-win32 build. This suggests there is a solution.
My hope is this isn't a show stopper because this mechanism has been
tossed so dlls work more like shared libraries on linux. At least this
compiler package comes with xilink, something described as a "dynamic
I humbly request guidance in resolving this problem.
Jeff Holle wrote:
> I am testing Intel's C++ compiler v8.0 on a windows 2000 system.
> I've got STLPort-4.5 installed on this machine and want to use it.
> In attempting to build boost v1.31.0, I've run into a problem using
> "bjam -sTOOLS=intel-win32-stlport". It produces:
> icl: Command line error: invalid argument for option '-Qms'.
> Running "bjam -sTOOLS=intel-win32" appears to by and large work.
> At least the above problem doesn't appear.
> In looking into the output of "bjam -a -n -sTOOLS=intel-win32-stlport",
> the problematic compiler flag appears to be '/Qmsvc-stlport'.
> In running "bjam -a -n -sTOOLS=intel-win32", no similar flag is emitted.
> Can somebody point out what needs to be changed to get rid of the
> offending compiler flag?
> *Yahoo! Groups Links*
> * To visit your group on the web, go to:
> * To unsubscribe from this group, send an email to:
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk