On 5/21/2013 2:04 AM, Phillip Hellewell wrote:
On Mon, May 20, 2013 at 1:12 PM, Phillip Hellewell <ssh...@gmail.com> wrote:
Should I try to patch it myself?
FYI, the linker error is occurring because nasm is failing with a ton
of errors on x86_64-g2m.asm, I think maybe because it is creating the
wrong type of asm.
So I tried masm instead, and it is working sometimes, but sometimes I get this:
tmp32dll\x86_64-gf2m.asm(1) : error A2088:END directive required at end of file
Assuming I can get past that, the conclusion is that I have to use
masm for 64-bit and nasm for 32-bit. And since do_win64a.bat and
other spots are set up to just use nasm automatically when available,
I have to play a silly game in my build script where I hide nasm.exe
from my path while building 64-bit, then put it back in my path while
building 32-bit.
I have previously built 1.0.x for Win64 on x86_64 using Visual Studio
2005 with little or no problems, and the resulting libs link nicely with
VS2010, but I have not tested building OpenSSL itself on VS2010.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
