Hi, I am using VC++ 7.1 and getting an internal compiler error when compiling in DEBUG mode: boost\mpl\aux_\preprocessed\plain\apply.hpp(50) : fatal error C1001: INTERNAL COMPILER ERROR. This is at the declaration of boost::mpl::apply2 This does not happen when compiling in RELEASE mode. When doing a full build, two files cause this error, say X.cpp and Y.cpp. If I first clean the build and compile X.cpp then Y.cpp, only Y.cpp will generate the error. Ditto for reversing the order. Has anybody else seen this inexplicable (to me) behavior? Thanks, Greg
Greg Emerson writes:
Hi,
I am using VC++ 7.1 and getting an internal compiler error when compiling in DEBUG mode:
boost\mpl\aux_\preprocessed\plain\apply.hpp(50) : fatal error C1001: INTERNAL COMPILER ERROR. This is at the declaration of boost::mpl::apply2
This does not happen when compiling in RELEASE mode.
When doing a full build, two files cause this error, say X.cpp and Y.cpp. If I first clean the build and compile X.cpp then Y.cpp, only Y.cpp will generate the error. Ditto for reversing the order.
Has anybody else seen this inexplicable (to me) behavior?
A guess: you have [automatic] precompiled headers enabled, and the error is in fact in one of the headers that is used by both X.cpp and Y.cpp. You can try disabling the precompiled headers and see if it helps you identify the actual source of the failure. Disclaimer: it's been a while since I had my hands dirty in something like this, so this might be not the most efficient way to track it down (or I might be wrong). P.S. What version of boost are you using? -- Aleksey Gurtovoy MetaCommunications Engineering
participants (2)
-
Aleksey Gurtovoy
-
Greg Emerson