I downloaded the very convenient clapack-3.2.1-CMAKE package, chose Visual Studio 9 32 bit, did an ALL_BUILD in RelWithDebInfo, the RUN_TESTS and everything passed -- very nice.

Then I attempted the same choosing Visual Studio 9 64 bit, everything built fine, but all tests after xlintsts_stest_in failed (and all tests prior to that succeeded). Below are the last 3 successes and first 3 failures:

I am not sure if this is causing me a problem or not since with the x64 cmake compiled version I get different results using a coworkers program versus a binary .lib compiled for Visual Studio 2005 x86.

I'm getting a very similar error. I was using VS2008, and both 32 and 64 bit CMAKE generated solutions compiled just fine and passed all tests. Then I got a new machine and VS2010, patched (ad nauseum) with Windows Update and VS2010 SP1. A nice fresh new VS2010 32-bit solution generated with clapack-3.2.1-CMAKE and CMake 2.8.6 compiles and passes all tests, both Debug and Release. However, a 64-bit generated solution compiles, but fails every test from xlintsts_stest_in onward:

I have used the 32-bit libraries to correctly run the example project as suggested below, but the example doesn't have a 64-bit configuration, so I can't be sure if the problem with the 64-bit is in the actual logic or with the testing framework, but I tend to suspect the latter. I regret that I am not yet familiar enough with CMake generated projects to know where/how to debug this, any assistance would be greatly appreciated.

admin wrote:Hi,Sorry to get to you so late.From what I see, BLAS Testing are successful but not the CLAPACK Testing in 64 bit configuration.To check that something is actually working.Could you try running the example http://icl.cs.utk.edu/lapack-for-window ... ml#running (part 2)

This problem happens only under Windows, CLAPACK 64 bit works fines under Linux system with CMAKE.My Windows machine is down at the moment, but I will try to take a look later.Julie

Hi, I just tried this and it works fine, regardless of the errors when running the tests.

In light of this thread necromancy, my CLAPACK tests are also failing when trying to build CLAPACK in 64 bit mode from a CMake generated VS2010 solution on Windows 7.

admin wrote:Hi,Sorry to get to you so late.From what I see, BLAS Testing are successful but not the CLAPACK Testing in 64 bit configuration.To check that something is actually working.Could you try running the example http://icl.cs.utk.edu/lapack-for-window ... ml#running (part 2)

This problem happens only under Windows, CLAPACK 64 bit works fines under Linux system with CMAKE.My Windows machine is down at the moment, but I will try to take a look later.Julie

Hi, I just tried this and the example works fine, regardless of the errors when running the tests.

In light of this thread necromancy, my CLAPACK tests are also failing when trying to build CLAPACK in 64 bit mode from a CMake generated VS2010 solution on Windows 7.

I believe I am experiencing the same problem. when I attempt to run a test such as "xeigtsts < nep.in > snep.out" I receive this message: the system cannot execute the specified program. This problem only occurs with the executables in the TESTING directory for the an x64 build on windows. Everything works great on Linux and on windows, there are no problems with anything if you compile in 32 bit and the BLAS tests work correctly for a 64 bit build. If anyone has found a solution of has a good idea of what may be causing this problem I would greatly appreciate any help.

This has something to do with the size of the stack. I believe that the size of the stack is changed with some regex expression if you are compiling in 32 but it is not is you are compiling in 64. I just know if I append /STACK:40000000 to the end of the link line in visual studio xeigstst, the test runs as it should and with out doing that, when I run it the system says it cannot execute the specified program on the system.

The problem here is that the requested stack size is extremely large. I don't know why that is allowed to fly on 32 bit and not 64, but it is. In the CMakeList.txt file in TESTING, there is a regex which places /STACK:900,000,000,000,000,000 in the link line. That's a pretty big number. If you replace that number with 40000000 everything works. I suggest that change be made to the next cmake clapack release if anyone on here has the power to do that but it is a pretty easy fix if you just wanna get the tests running with the existing release.