Re: problems with -sTOOLS=intel-win32-stlport

From: David Abrahams (dave_at_[hidden])
Date: 2004-02-11 10:12:50

Jeff Holle <jeff.holle_at_[hidden]> writes:

> 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.

What is INTEL_BASE_MSVC_TOOLSET set to on your system?

> Another thing recommended is suppression of warning 167. It is emitted 
> 520 times during the boost build. Always associated with use of 
> BOOST_ASSERT.
> Appending "/Qwd167" to line 42 of intel-win32-tools.jam fixed this.

I think we ought to fix BOOST_ASSERT so that it doesn't do that.

> 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 
> undefined reference.
>
> The interesting thing, to me at least, is this isn't a problem with the 
> intel-win32 build. This suggests there is a solution.

It appears something you've done to the toolset is turning
MS-specific extensions.

> 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 
> linker".
>
> I humbly request guidance in resolving this problem.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com