regression - failed tests for date_time and regex in vc7.1 toolkit
I've noticed that regression test I'm running are failing on almost all tests in date_time and many tests in regex. Here's what I've found: bjam is building static library: libboost_date_time-71-mt-gd-1_32.lib Please note that there's no "vc71", but "71" instead. File: libboost_date_time-vc71-mt-gd-1_32.lib is not build, thus all tests linking to this file are failing. When I copy libboost_date_time-71-mt-gd-1_32.lib into libboost_date_time-vc71-mt-gd-1_32.lib , date_time tests are no longer failing. The same applies to dynamic library: what is actually being build is named: boost_date_time-71-mt-gd-1_32.lib boost_date_time-71-mt-gd-1_32.dll but for tests to succeed there should be: boost_date_time-vc71-mt-gd-1_32.lib boost_date_time-vc71-mt-gd-1_32.dll What's even more interesting, library files "71" are actually being used, too (besides "vc71" files). I've found that "cmd" files are referring to "71" files. I do not know what is referring to "vc71" files (maybe autolink feature?) The same problem plagued regression tests for regex library - libraries build by bjam are named : libboost_regex-71-mt-gd-1_32.lib boost_regex-71-mt-gd-1_32.lib boost_regex-71-mt-gd-1_32.dll while tests require also files named : libboost_regex-vc71-mt-gd-1_32.lib boost_regex-vc71-mt-gd-1_32.lib boost_regex-vc71-mt-gd-1_32.dll Any ideas what might be wrong? B.
Bronek Kozicki wrote: [...] Here's full list of "71" files from regression tests directory tree: boost\libs\config\test\link\link_test.dll\vc7.1\debug\threading-multi\link_test-71-mt-gd-1_32.lib boost\libs\date_time\build\boost_date_time.dll\vc7.1\debug\threading-multi\boost_date_time-71-mt-gd-1_32.lib boost\libs\date_time\build\libboost_date_time.lib\vc7.1\debug\threading-multi\libboost_date_time-71-mt-gd-1_32.lib boost\libs\filesystem\build\libboost_filesystem.lib\vc7.1\debug\threading-multi\libboost_filesystem-71-mt-gd-1_32.lib boost\libs\program_options\build\boost_program_options.dll\vc7.1\debug\threading-multi\boost_program_options-71-mt-gd-1_32.lib boost\libs\program_options\build\libboost_program_options.lib\vc7.1\debug\threading-multi\libboost_program_options-71-mt-gd-1_32.lib boost\libs\regex\build\boost_regex.dll\vc7.1\debug\threading-multi\boost_regex-71-mt-gd-1_32.lib boost\libs\regex\build\libboost_regex.lib\vc7.1\debug\threading-multi\libboost_regex-71-mt-gd-1_32.lib boost\libs\signals\build\libboost_signals.lib\vc7.1\debug\threading-multi\libboost_signals-71-mt-gd-1_32.lib boost\libs\thread\build\boost_thread.dll\vc7.1\debug\threading-multi\boost_thread-71-mt-gd-1_32.lib boost\libs\thread\build\libboost_thread.lib\vc7.1\debug\runtime-link-static\threading-multi\libboost_thread-71-mt-sgd-1_32.lib boost\libs\config\test\link\link_test.dll\vc7.1\debug\threading-multi\link_test-71-mt-gd-1_32.dll boost\libs\date_time\build\boost_date_time.dll\vc7.1\debug\threading-multi\boost_date_time-71-mt-gd-1_32.dll boost\libs\program_options\build\boost_program_options.dll\vc7.1\debug\threading-multi\boost_program_options-71-mt-gd-1_32.dll boost\libs\regex\build\boost_regex.dll\vc7.1\debug\threading-multi\boost_regex-71-mt-gd-1_32.dll boost\libs\thread\build\boost_thread.dll\vc7.1\debug\threading-multi\boost_thread-71-mt-gd-1_32.dll There are no *-vc71-*.lib files at all. That's funny that only date_time and regex are unexpectedly failing. Maybe other testers running vc7.1 toolset could check their regression tests directory tree? B.
I don't "empty" the library directory before each regression run (perhaps I should?? maybe that's why I have 812 files in there) so I went and checked and the last time I have files with the vc71 (or vc80 for that matter) in them was on the 11th at approximately 2000PDT. Isn't this the same time Rene fixed the problem of copying two different files over the same one in the build process? At Friday 2004-08-13 13:48, you wrote:
I've noticed that regression test I'm running are failing on almost all tests in date_time and many tests in regex. Here's what I've found: bjam is building static library: libboost_date_time-71-mt-gd-1_32.lib
Please note that there's no "vc71", but "71" instead. File: libboost_date_time-vc71-mt-gd-1_32.lib
is not build, thus all tests linking to this file are failing. When I copy libboost_date_time-71-mt-gd-1_32.lib into libboost_date_time-vc71-mt-gd-1_32.lib , date_time tests are no longer failing. The same applies to dynamic library: what is actually being build is named: boost_date_time-71-mt-gd-1_32.lib boost_date_time-71-mt-gd-1_32.dll
but for tests to succeed there should be: boost_date_time-vc71-mt-gd-1_32.lib boost_date_time-vc71-mt-gd-1_32.dll
What's even more interesting, library files "71" are actually being used, too (besides "vc71" files). I've found that "cmd" files are referring to "71" files. I do not know what is referring to "vc71" files (maybe autolink feature?)
The same problem plagued regression tests for regex library - libraries build by bjam are named : libboost_regex-71-mt-gd-1_32.lib boost_regex-71-mt-gd-1_32.lib boost_regex-71-mt-gd-1_32.dll
while tests require also files named : libboost_regex-vc71-mt-gd-1_32.lib boost_regex-vc71-mt-gd-1_32.lib boost_regex-vc71-mt-gd-1_32.dll
Any ideas what might be wrong?
B.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"
Victor A. Wagner Jr. wrote:
I don't "empty" the library directory before each regression run (perhaps I should?? maybe that's why I have 812 files in there) so I went and checked and the last time I have files with the vc71 (or vc80 for that matter) in them was on the 11th at approximately 2000PDT. Isn't this the same time Rene fixed the problem of copying two different files over the same one in the build process?
I had to do some significant changes to fix that library duplication problem, and to fix a few other problems with naming. So I did not have time to test all variations fully :-( Sorry about that, but testing build changes takes a long time. I'm also sorry that I won't be able to look at this until tomorrow, I just got back to my computers... after a long 18 hour day. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
Rene Rivera wrote:
I had to do some significant changes to fix that library duplication problem, and to fix a few other problems with naming. So I did not have time to test all variations fully :-( Sorry about that, but testing
You do not need to be sorry, that's what we are for. But I feel relief - my computer is not broken :) B.
Bronek Kozicki wrote:
Bronek Kozicki wrote:
You do not need to be sorry, that's what we are for.
Of course I meant that we are for running tests, not to be sorry ;)
LOL... Got it the first time :-) It's fixed now. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
participants (3)
-
Bronek Kozicki -
Rene Rivera -
Victor A. Wagner Jr.