I assume so. The makefile would need to change to remove SM1.x compiling and link the 64-bit library.

ATH: this is a work machine and I don't have administrator access. If I could turn off the AV software, malware could as well :)

Various classes of malware are known not to require administrator access to turn off so-called security software, that said :smile:

Here are the Msieve svn 988 versions I managed to compile for Haswell, Sandy Bridge and Core2.

Remember I got a lot of warnings during compiling, see post #10.

[URL="hoegge.dk/mersenne/msieve-svn988-haswell.zip"]msieve-svn988-haswell.zip[/URL]
[URL="hoegge.dk/mersenne/msieve-svn988-sandybridge.zip"]msieve-svn988-sandybridge.zip[/URL]
[URL="hoegge.dk/mersenne/msieve-svn988-core2.zip"]msieve-svn988-core2.zip[/URL]

Tried the Core 2 version, it complains about missing zlib1.dll. I guess zlib should be compiled in statically.

I did not compile zlib, it was preinstalled in MSYS2. I added "zlib1.dll" from MSYS2 to the zip files. Try and download it again.

Thank you, it appears to work now.

However, is there a way to disable GPU poly selection? It's trying and failing because I have a CUDA 1.x card.

I think as long as you don't use the "-g" parameter it should use CPU.

I tried that, it uses GPU no matter that. It doesn't even fall back in case of failure.

Perhaps it would work properly on a computer with a non-Nvidia GPU, but it's completely unusable if you have an older Nvidia.

Gotcha. If you go here: [url]http://gilchrist.ca/jeff/factoring/index.html[/url] you can find an i7/i5 version of MSieve 1.52. It's not the absolute latest version, but it should get the job done for you.

Yes, the SVN 883 version I mentioned in the 1st post (SVN 939 is good for poly selection only, it crashes in linear algebra). And it won't run on Core 2 - for that, the last version is 1.50 only.

[QUOTE=jasonp;420607]My problem is not that GMP doesn't work, it's that Windows 7 has some kind of background service that holds onto executables just long enough for the configure script to fail trying to delete temporary exe's that it generates. Thus configure doesn't work and I can't get to the next step.
[/QUOTE]

I have a similar problem using MSDEV. I always suspected the Virus scanner is checking the new EXE for a virus. It doesn't know the difference between downloading an EXE from the internet and a tool chain writing an EXE file.