Closed GoogleCodeExporter closed 9 years ago
Try to rebuild. Also try to run Visual Studio as admin.
Original comment by zexspect...@gmail.com
on 12 Apr 2010 at 5:49
i tried to rebuild. several times. i also tried to run as admin. this is
what i got:
1>------ Build started: Project: CrashRpt, Configuration: Debug Win32 ------
1>Compiling...
1>StdAfx.cpp
1>...\crashrpt\src\StdAfx.cpp : fatal error C1001: An internal error has
occurred in
the compiler.
1>(compiler file
'f:\dd\vctools\compiler\utc\src\p2\main.c[0x6E097740:0x0000000C]',
line 182)
1> To work around this problem, try simplifying or changing the program near the
locations listed above.
1>Please choose the Technical Support command on the Visual C++
1> Help menu, or open the Technical Support help file for more information
1>INTERNAL COMPILER ERROR in 'c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\cl.exe'
1> Please choose the Technical Support command on the Visual C++
1> Help menu, or open the Technical Support help file for more information
1>Creating browse information file...
1>Microsoft Browse Information Maintenance Utility Version 9.00.21022
1>Copyright (C) Microsoft Corporation. All rights reserved.
1>BSCMAKE: error BK1506 : cannot open file '.\Debug\CrashRpt.sbr': No such file
or
directory
1>Build log was saved at "file:...\crashrpt\src\Debug\BuildLog.htm"
1>CrashRpt - 2 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Original comment by anbaricf...@gmail.com
on 12 Apr 2010 at 6:39
What service pack do you have? Install the latest service pack for VS2008. This
should fix the problem. I compiled CrashRpt with VS2008 SP1 without errors.
Original comment by zexspect...@gmail.com
on 12 Apr 2010 at 6:42
This problem seems to be related to Visual Studio, not to CrashRpt. So, nothing
is to
be fixed here.
Original comment by zexspect...@gmail.com
on 14 Apr 2010 at 10:33
yeah, i figger'd it out, you can close this bug.
i am running under parallels on my mac, i use a ".psf" mapped network drive to
access
the files on the mac side. when i instead keep the files on the actual
internal "C"
drive, they compile fine.
Original comment by anbaricf...@gmail.com
on 17 Apr 2010 at 9:44
Original issue reported on code.google.com by
anbaricf...@gmail.com
on 12 Apr 2010 at 5:45