On Thu, Apr 08, 2010, NormW via RT wrote:
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.
This is a new feature in OpenSSL 1.0.0: some MK1mF build targets support
automatic build of assembly language source from perlasm. I got this working
in the only platforms I knew about, others kept the old functionality.
You should be able to copy the Win32 perl scripts to get the same
functionality in NetWare.
Something like this...
1. Update Configure target (add asm modules similar to VC-WIN32).
2. Update the Netware makefile generator module in util/pl/netware.pl, check
out the stuff called win32_import_asm() in util/pl/VC-32.pl you also have to
set $perl_asm to 1.
3. If you get it working submit a patch to rt ;-)
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
