On 09/11/2012 00:01, Dann Corbit wrote: > All of the projects build for me except for the tune project. The mpir-tests > project had three failures to build, but the three failures for mpir-tests > built OK on a second pass (I suspect that there is a missing dependency for > those three projects and the first pass built some object or library that > they needed). I just opened all of the projects one at a time and did build > solution for 32 and 64 bit release (and MPIR was built for Nehalem since I > have I7).
Hi Dan, The Visual Studio tune solution contains the project fft-tune that is no longer needed since FFT tuning is now a part of the main tune project. I should have removed fft-tune but, unfortunately, I missed this. So the fft-tune project should be ignored. Sadly Jason and I were going to work on improving tune, including getting it to work on Windows, but we now that Jason is no longer with us we need voluinteers for this. In the meantime, I am afraid that tune is not reliable on Windows although it should build correctly. The issue with the MPIR tests where there are build failures for a few sub-projects which then succeed second time round is caused by Visual Studio doing multiple project builds in parallel. There is a common library for the tests and when a parallel build is started this is built in parallel with several of the tests. But if the tests complete building before the common library, the library binary doesn't yet exist so the builds fail. The second time round, the library has been built so it is not rebuilt and the tests that failed previously now succeed as they can find the library. A simple solution is to turn off parallel builds in Visual Studio (a VS configuration option) but this slows down the build. I personally prefer the faster parallel build so I just manually select and build the library project (the first listed) on its own before building the remainder of the tests. As Bill mentions the tests must be built and run immediately after MPIR is built. So if you are building and testing several versions of MPIR the tests have to be interleaved with the MPIR builds. I'll look at the issues with mpir_bench when I have some time for this. Brian -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
