Newbie Build Problem - Debug Assertion Failed
New install of Visual C++ 2005 Express New install of the Platform SDK New download of boost-jam-3.1.12 I get the attached error when the build script tries to launch jam0. Any ideas? Reinstall something maybe? Eric --- Begin Build Log --- C:\boost-jam-3.1.12>build Setting environment for using Microsoft Visual Studio 2005 x86 tools. ### ### Using 'vc8' toolset. ### C:\boost-jam-3.1.12>rd /S /Q bootstrap C:\boost-jam-3.1.12>md bootstrap C:\boost-jam-3.1.12>cl /nologo /RTC1 /Zi /MTd -DNT -DYYDEBUG -wd4996 kernel32.lib advapi32.lib /Febootstrap\jam0 [snipped] command.c compile.c debug.c execnt.c expand.c filent.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c Generating Code... Compiling... regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c w32_getreg.c native.c set.c path.c regex.c property-set.c sequence.c Generating Code... Compiling... order.c Generating Code... C:\boost-jam-3.1.12>.\bootstrap\jam0 -f build.jam --toolset=vc8 "--toolset-root=C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\ " clean
Eric Hill wrote:
New install of Visual C++ 2005 Express New install of the Platform SDK New download of boost-jam-3.1.12
I get the attached error when the build script tries to launch jam0. Any ideas? Reinstall something maybe?
Yikes that looks bad. I have no idea why it's showing up though. Best guess is your clock is way off, or something in jam is trying to translate a date which VC thinks is invalid somehow. Although I must say vc8 is what I used to make the Windows binaries and it worked fine for me, it wasn't the express edition though, it was the pro edition vanilla install. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Yikes that looks bad. I have no idea why it's showing up though. Best guess is your clock is way off, or something in jam is trying to translate a date which VC thinks is invalid somehow. Although I must say vc8 is what I used to make the Windows binaries and it worked fine for me, it wasn't the express edition though, it was the pro edition vanilla install.
After some tinkering without success, I decided to remove the .Net framework 1.x and reinstall. (Obviously 2.0 was installed by the VS setup.) For some reason, after reinstalling the 1.x framework, the problem corrected itself. Eric
participants (2)
-
Eric Hill
-
Rene Rivera