OK, here is the real fix to the problem.
Rehash:
Compiling for tool "msvc-stlport" fails with these errors repeated for
many files:
C:\PROGRA~1\MICROS~3\VC98\include\winbase.h(1011) : error C2733: second
C linkage of overloaded function 'InterlockedIncremen t' not allowed
C:\PROGRA~1\MICROS~3\VC98\include\winbase.h(1009) : see declaration of
'InterlockedIncrement'
C:\PROGRA~1\MICROS~3\VC98\include\winbase.h(1018) : error C2733: second
C linkage of overloaded function 'InterlockedDecremen t' not allowed
C:\PROGRA~1\MICROS~3\VC98\include\winbase.h(1016) : see declaration of
'InterlockedDecrement'
C:\PROGRA~1\MICROS~3\VC98\include\winbase.h(1026) : error C2733: second
C linkage of overloaded function 'InterlockedExchange ' not allowed
C:\PROGRA~1\MICROS~3\VC98\include\winbase.h(1023) : see declaration of
'InterlockedExchange'
This problem occurs when the Platform SDK is installed.
The PSDK include path must be searched before the standard MSVC
includes. The bjam tool adds -I"C:\PROGRA~1\MICROS~3\VC98\include" to
the cl command line, so that is searched before the PSDK include path
which is specified in the environment.
An immediate solution is to have the PSDK include path searched first,
using this bjam command line:
bjam -sTOOLS=msvc-stlport -sBUILD="debug release <stlport-iostream>on
<sysinclude>C:\Progra~1\MIFD68~1\Include\." -sSTLPORT_PATH=c:\etc
NOTE: "C:\Progra~1\MIFD68~1\Include\." is the short form of "C:\Program
Files\Microsoft SDK\Include" on my machine. YMMV.
This should probably be fixed in msvc-tools.jam which would somehow
check if the PSDK is installed (by checking the environment?) and added
to the header search path as needed.
BTW: I've added this to
http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?CommonBui
ldProblems
Regards,
David Resnick
MobileSpear Inc.
-----Original Message-----
From: David Abrahams [mailto:yg-boost-users@m.gmane.org]
Sent: Friday, September 06, 2002 23:56
To: boost-users@yahoogroups.com
Subject: [Boost-Users] Re: Re: msvc-stlport build problems
"David Resnick"
I've fixed the problem, here's my solution in case anyone else needs it:
The problem didn't have to do with the Platform SDK in the end.
The configuration that I'm using is MSVC6 SP3 on Windows 2000.
The fix was to add :
flags msvc-stlport DEFINES : _NTOS_=1 ;
to the "special flags for STLport 4.0" block in tools\build\msvc-stlport-tools.jam (line 117, for example).
Is that #define needed by STLPort, or is specific to the code you're trying to compile? If it's the former, we should patch the toolset. Please respond to jamboost@yahoogroups.com
I have a question for jam experts: How can I set this define (_NTOS_=1) from the command line?
bjam -sBUILD="<stlport-iostream>on <define>_NTOS_=1" ... ----------------------------------------------------------- David Abrahams * Boost Consulting dave@boost-consulting.com * http://www.boost-consulting.com Yahoo! Groups Sponsor ADVERTISEMENT Info: http://www.boost.org Wiki: http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl Unsubscribe: mailto:boost-users-unsubscribe@yahoogroups.com Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.