Beman Dawes <bdawes <at> acm.org> writes:
On Thu, Jul 7, 2011 at 8:18 AM, Beman Dawes <bdawes <at> acm.org> wrote:
There has been no reply to Eric's query above
I'll see if I can reproduce the problem and test the patch.
I'm not able to reproduce this problem on either the current trunk or branches/release. Thus I'm unwilling to apply the patch.
I'm building release candidates now. Once those go up on the ftp site, perhaps the OP could try again. And if it fails, give us the exact build command line that is failing.
I can confirm that the issue is still present in the boost_1_47_0.7z package from boost.cowic.de/rc/ timestamped '2011-Jul-07 16:06:52'. My environment is Win7 x64, MSVC10 SP1. My build command lines are as follows: x86 debug: bjam.exe --without-mpi --without-python --build-type=complete toolset=msvc-10.0 architecture=x86 address-model=32 extern-c-nothrow=on debug stage x86 release: bjam.exe --without-mpi --without-python --build-type=complete toolset=msvc-10.0 architecture=x86 address-model=32 extern-c-nothrow=on cxxflags="/GS- /arch:SSE2 /GL" linkflags="/OPT:REF /OPT:ICF /LTCG" release stage x64 debug: bjam.exe --without-mpi --without-python --build-type=complete toolset=msvc-10.0 architecture=x86 address-model=64 extern-c-nothrow=on debug stage x64 release: bjam.exe --without-mpi --without-python --build-type=complete toolset=msvc-10.0 architecture=x86 address-model=64 extern-c-nothrow=on cxxflags="/GS- /GL" linkflags="/OPT:REF /OPT:ICF /LTCG" release stage All four variants experience the same issue.