It might be better if you specify how you set up your environment, what versions of perl and nasm you used, and what sequence of commands you used.
I usually do a cut-down static build in an environment based on the Windows Driver Kit, and I've built 1.0.1e using nasm without problems. I just tried a default DLL build in the same environment; it assembled x86_64-gf2m.asm and built libeay32.dll with no issues; it failed on its way to the other DLL for reasons which I think are caused by my peculiar build environment. The Shining Light distribution says it is a default build, makes no mention of having had to disable assembler. They don't give a lot of details of the build process, but I'd have thought disabling assembler would get a mention. I'm sure an x64 assembler DLL build is possible with the right tools. > From: Phillip Hellewell [mailto:ssh...@gmail.com] > Sent: Tuesday, May 21, 2013 1:04 AM > > 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. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
