Hi, If I try to build for win32 I do: > perl Configure VC-WIN32 --prefix=c:\some\openssl\dir
then (via ms\do_nasm.bat) > perl util\mkfiles.pl >MINFO > perl util\mk1mf.pl dll nasm VC-WIN32 >ms\ntdll.mak I get ms\ntdll.mak that includes asm support, such as: > $(TMP_D)\x86cpuid.asm: crypto\x86cpuid.pl > $(PERL) crypto\x86cpuid.pl win32n $(CFLAG) >$@ > > $(OBJ_D)\x86cpuid.obj: $(TMP_D)\x86cpuid.asm > $(ASM) -o $@ $(TMP_D)\x86cpuid.asm When I run the same process for NetWare: > perl Configure netware-libc > perl util\mkfiles.pl >MINFO > perl util\mk1mf.pl nw-nasm netware-libc >Netware\netware-libc.mak the resulting .mak file has none of the asm targets or objects in the libraries and (consequently) linking of nlm's fail. (A build of OSSL without asm support builds correctly). In builds of OSSL 0.9.8 the NetWare asm files were built separately (in Netware\build.bat) but see no reason why targets similar to that for win32 (above) cannot be used (with proper variable substitution) for NetWare, thereby standardising the build process... Any assistance for resolving the absence of asm targets for NetWare is appreciated. Regards, Norm ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
