Given the 1.0.2 release is forthcoming in the near future, it would be good if someone could look at this issue. It looks like there were a lot of changes made to sha1-586.pl in 1.0.2 to support the new Intel SHA extensions, which aren't available until Skylake.
Is there a new tool chain requirement for building 1.0.2 on Windows? Has the build procedure changed? Or is this simply a bug in sha1-586.pl? On 01/08/2015 03:41 PM, John Foley wrote: > Is the Windows build broken on 1.0.2-stable, am I doing something wrong, > or is this a tool chain issue? I'm using VS 2013. Using the following > steps works on 1.0.1-stable: > > perl Configure VC-WIN32 > ms\do_ms.bat > nmake -f ms\nt.mak > > > Here's the log from the broken 1.0.2 build: > > http://173.39.238.160:8080/view/1.0.2%20Stable/job/1_0_2_windows/1/console > > Here's the log from the working 1.0.1 build: > > http://173.39.238.160:8080/view/1.0.1%20Stable/job/1_0_1_windows/6/console _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
