Errors building boost w/ VC++ 6.0 sp5
I downloaded boost_1_30_0.zip, unpacked the zip file, cd'ed into
boost_1_30_0, and ran "bjam "-sTOOLS=msvc". Most of the library seemd to
compile fine (Python was skipped since I didn't have it installed). Bjam
failed to update 12 targets, skipped 12 targets (the same 12 that failed?),
and updated 452 targets. The error messages at the end were:
...failed vc-Link
libs\test\build\bin\boost_test_exec_monitor.dll\msvc\debug\run
time-link-dynamic\threading-single\boost_test_exec_monitor.dll
libs\test\build\b
in\boost_test_exec_monitor.dll\msvc\debug\runtime-link-dynamic\threading-sin
gle\
boost_test_exec_monitor.lib...
...skipped
nul "C:\Program Files\Microsoft Visual Studio\VC98\bin\link" /nologo /INCREMENT AL:NO /DEBUG /DLL /subsystem:console /out:"libs\test\build\bin\boost_test_exe c_monitor.dll\msvc\debug\runtime-link-dynamic\threading-multi\boost_test_exe c_mo nitor.dll" /IMPLIB:"libs\test\build\bin\boost_test_exec_monitor.dll\msvc\debug\ runtime-link-dynamic\threading-multi\boost_test_exec_monitor.lib" @"libs\tes t\build\bin\boost_test_exec_monitor.dll\msvc\debug\runtime-link-dynamic\thre adin g-multi\boost_test_exec_monitor.CMD"
boo st_test_exec_monitor.lib... MkDir1 libs\test\build\bin\boost_unit_test_framework.dll MkDir1 libs\test\build\bin\boost_unit_test_framework.dll\msvc MkDir1 libs\test\build\bin\boost_unit_test_framework.dll\msvc\debug MkDir1
nul "C:\Program Files\Microsoft Visual Studio\VC98\bin\link" /nologo /INCREMENT AL:NO /DEBUG /DLL /subsystem:console /out:"libs\test\build\bin\boost_unit_tes t_framework.dll\msvc\debug\runtime-link-static\threading-single\boost_unit_t est_
nul "C:\Program Files\Microsoft Visual Studio\VC98\bin\link" /nologo /INCREMENT AL:NO /DEBUG /DLL /subsystem:console /out:"libs\test\build\bin\boost_unit_tes t_framework.dll\msvc\debug\runtime-link-static\threading-multi\boost_unit_te st_f ramework.dll" /IMPLIB:"libs\test\build\bin\boost_unit_test_framework.dll\msvc\d ebug\runtime-link-static\threading-multi\boost_unit_test_framework.lib" @"li bs\test\build\bin\boost_unit_test_framework.dll\msvc\debug\runtime-link-stat ic\t
boost_unit_test_framework.lib... MkDir1
...failed vc-Link
libs\test\build\bin\boost_test_exec_monitor.dll\msvc\debug\run
time-link-dynamic\threading-multi\boost_test_exec_monitor.dll
libs\test\build\bi
n\boost_test_exec_monitor.dll\msvc\debug\runtime-link-dynamic\threading-mult
i\bo
ost_test_exec_monitor.lib...
...skipped
nul
"C:\Program Files\Microsoft Visual Studio\VC98\bin\link" /nologo
/INCREMENT
AL:NO /DEBUG /DLL /subsystem:console
/out:"libs\test\build\bin\boost_unit_tes
t_framework.dll\msvc\debug\runtime-link-dynamic\threading-single\boost_unit_
test
_framework.dll"
/IMPLIB:"libs\test\build\bin\boost_unit_test_framework.dll\msvc
\debug\runtime-link-dynamic\threading-single\boost_unit_test_framework.lib"
@"libs\test\build\bin\boost_unit_test_framework.dll\msvc\debug\runtime-link-
dyna
mic\threading-single\boost_unit_test_framework.CMD" nul
"C:\Program Files\Microsoft Visual Studio\VC98\bin\link" /nologo
/INCREMENT
AL:NO /DEBUG /DLL /subsystem:console
/out:"libs\test\build\bin\boost_unit_tes
t_framework.dll\msvc\debug\runtime-link-dynamic\threading-multi\boost_unit_t
est_ ...failed vc-Link
libs\test\build\bin\boost_unit_test_framework.dll\msvc\debug\r
untime-link-dynamic\threading-single\boost_unit_test_framework.dll
libs\test\bui
ld\bin\boost_unit_test_framework.dll\msvc\debug\runtime-link-dynamic\threadi
ng-s
ingle\boost_unit_test_framework.lib...
...skipped
You could not build shared libraries on Windows. Search this group for more details. Gennadiy.
"Gennadiy E. Rozental"
You could not build shared libraries on Windows. Search this group for more details.
Gennadiy.
Gennadiy, I don't think this can be an acceptable answer for much longer. It causes new users too much grief too often. What's it going to take for you to make the test library build right OOTB (or is it already fixed in the CVS)? -- Dave Abrahams Boost Consulting www.boost-consulting.com
--- In Boost-Users@yahoogroups.com, David Abrahams
"Gennadiy E. Rozental"
writes: You could not build shared libraries on Windows. Search this group for more details.
Gennadiy.
Gennadiy,
I don't think this can be an acceptable answer for much longer. It causes new users too much grief too often. What's it going to take for you to make the test library build right OOTB (or is it already fixed in the CVS)?
While ago. Right after 1.30.0 came out. I already explained this in this newsgroup three times. Gennadiy.
"Gennadiy E. Rozental"
--- In Boost-Users@yahoogroups.com, David Abrahams
wrote: "Gennadiy E. Rozental"
writes: You could not build shared libraries on Windows. Search this group for more details.
Gennadiy.
Gennadiy,
I don't think this can be an acceptable answer for much longer. It causes new users too much grief too often. What's it going to take for you to make the test library build right OOTB (or is it already fixed in the CVS)?
While ago. Right after 1.30.0 came out. I already explained this in this newsgroup three times.
Sorry I missed it. Is the fix checked into the RC_1_30_0 branch so it will go out with 1.30.2? -- Dave Abrahams Boost Consulting www.boost-consulting.com
While ago. Right after 1.30.0 came out. I already explained this in this newsgroup three times.
Sorry I missed it. Is the fix checked into the RC_1_30_0 branch so it will go out with 1.30.2?
I do not know. My PC is in disassembled state at the moment, so I have only limited access to the tools needed. Particulaly I do not have any compilers or cvs. It would be difficult to me to fix it before you are planning the release. Gennadiy.
"Gennadiy E. Rozental"
While ago. Right after 1.30.0 came out. I already explained this in this newsgroup three times.
Sorry I missed it. Is the fix checked into the RC_1_30_0 branch so it will go out with 1.30.2?
I do not know. My PC is in disassembled state at the moment, so I have only limited access to the tools needed. Particulaly I do not have any compilers or cvs. It would be difficult to me to fix it before you are planning the release.
OK, I applied the changes from the HEAD libs/test/build/Jamfile to RC_1_30_0 and checked the build. I presume that's all that was needed? -- Dave Abrahams Boost Consulting www.boost-consulting.com
OK, I applied the changes from the HEAD libs/test/build/Jamfile to RC_1_30_0 and checked the build. I presume that's all that was needed?
I do not think this will do. There was one more change in Jamfile - I added one more module. You should not be able to build using latest Jamfile and 1.30.0 sources. Gennadiy.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
"Gennadiy E. Rozental"
OK, I applied the changes from the HEAD libs/test/build/Jamfile to RC_1_30_0 and checked the build. I presume that's all that was needed?
I do not think this will do. There was one more change in Jamfile - I added one more module. You should not be able to build using latest Jamfile and 1.30.0 sources.
I didn't take that part of your change. I did test the build after making the change, after all ;-> -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (3)
-
David Abrahams
-
Gennadiy E. Rozental
-
Michael H. Cox