> >> Inline functions are better way for forwarding calls, esp. in this case. > > Ok by me, but shouldn't you do all 6?
Turns out your prediction of trouble came true faster than expected. Looking at the mass build report, there are a number of errors that all map to these stdcall functions. As near as I can make out, what happened was this: Boost duplicated the lines declaring the prototypes for these functions (see http://svn.boost.org/svn/boost/trunk/boost/detail/interlocked.hpp). They declared these functions as DLLIMPORT. Normally not a problem, but when I did "#define InterlockedExchange _InterlockedExchange" in winbase, suddenly their code started looking for an import named "_imp___InterlockedExchange@8" (note the triple underscore) instead of _imp__InterlockedExchange@8 (double underscore). Jacek's proposed patch (if he does all 6 stdcall functions) should resolve this problem. dw ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
