Hi Brian, Thank you so much! I downloaded the most recent version from the repository, and (this is probably key) upgraded my version of vsasym to the latest. Then built it exactly as instructed from a clean download. (except I piped the text to a log). I used the VS2015 msbuild dos window in a pythjon 3 environment to do it.
All 201 tests ran successfully. The libraries compiled with no warnings or errors. The tests had warnings but that is no big deal as they all run. Thanks again!! Terry On Saturday, 21 May 2016 22:33:16 UTC+1, Cactus wrote: > On 21/05/2016 13:24, terry...@lyonstech.net <javascript:> wrote: > > Version 2.7.2 Release x64 lib for Haswell using VS2015 enterprise > msbuild in an admin command window. > > > > Have just built this library and run the tests through the python > script. The tests reported that all built tests succeeded, however it > reported that 10 tests were not built. > > > > Build failure for mpn.dc_bdiv_q > > Build failure for mpn.dc_bdiv_q_n > > Build failure for mpn.dc_bdiv_qr > > Build failure for mpn.dc_bdiv_qr_n > > Build failure for mpn.inv_div_q > > Build failure for mpn.inv_div_qr > > Build failure for mpn.inv_div_qr_n > > Build failure for mpn.sb_bdiv_q > > Build failure for mpn.sb_bdiv_qr > > Build failure for mpn.tdiv_qr > > Hi Terry, > > I am sorry that you are having problems but I fear that I cannot > duplicate your problems here. I was hopeful that I could help as my > setup is identical to yours (VS2015 Enterprise). But I downloaded a > clean version of MPIR 2.7.2, configured a Haswell build and built the > library and the tests without any problems at all. > > There is a potential issue in building the tests that leads to a number > of build failures when they are built but it doesn't match your report. > > Typically VS2015 will buid a number of the tests in parallel but this > means that the add-test-lib (the common library for the tests) and a > number of the tests are built at the same time. But if the library build > has not completed before the build of a test, the latter will fail > because the library it needs is not yet available. > > There are several fixes. Just run the build of the tests again; manually > buid add-test-lib first; turn off parallel build in VS2015. But, as I > say, this does not seem to be the problem you are seeing > > > It seems to me that the key is the following style warning which appears > 10 times as well: > > > > > > > "C:\Users\xxxx\mpir-2.7.2\build.vc14\mpir-tests\mpn.dc_bdiv_q_n\mpn.dc_bdiv_q_n.vcxproj" > > (default target) (1) -> > > (DoLinkOutputFilesMatch target) -> > > C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets(1189,5): > warning MSB8012: > TargetPath(C:\Users\xxxx\mpir-2.7.2\build.vc14\mpir-tests\mpn.dc_bdiv_q_n\..\..\x64\Release\mpn.dc_bdiv_q_n.exe) > > does not match the Linker's OutputFile property value > (C:\Users\xxxx\mpir-2.7.2\build.vc14\mpir-tests\x64\Release\mpn.dc_bdiv_q_n.exe). > > This may cause your project to build incorrectly. To correct this, please > make sure that $(OutDir), $(TargetName) and $(TargetExt) property values > match the value specified in %(Link.OutputFile). > [C:\Users\xxxx\mpir-2.7.2\build.vc14\mpir-tests\mpn.dc_bdiv_q_n\mpn.dc_bdiv_q_n.vcxproj] > > > > > > 7 Warning(s) > > 0 Error(s) > > > > Time Elapsed 00:00:00.86 > > > > Related to this (I think), while almost all of the code compiles > silently, a few modules produce copious noise about 32<->64 bit issues. > These are very disconcerting to a user. It is hard for an inexperienced > user to see if the underlying code produces the warnings or > if it is just the tests that have issues. > > Yes, sadly there are hundreds if not thousands of these. We just don't > have the time to go through an awful lot of code to remove them. > > Brian > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at https://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
