On Wed, Jul 22, 2009, Guenter wrote: > Hi, > in addition to the issue below I see another one when I try to build > with ASM support: although the *.asm files get generated, the mk1mf.pl > script seems no longer to put the asm objects nor the asm build rules > into the generated makefile ... > I've looked though the mk1mf.pl, but lost track somehow - the 0.9.8 one > seemed more clear to me ... :) >
The 1.0.0 code for WIN32 changed the ASM handling and a fair bit of the other handling too. Since WIN32 uses mk1mf.pl this may affect other platforms using mk1mf.pl too. OpenSSL used to partially duplicate all sorts of functionality in mk1mf.pl that was more than adequately handled by Configure anyway. In 1.0.0 it reads several options for the top level Makefile Configure generates. For assembly language files another change has been made. In common with other platforms the assembly language files are included in the relevant line in Configure. Also instead of building them in the batch script these have been moved to auto generate them from the perl scripts in the makefile. The rather random naming convention has also been changed. Now we just change the suffix so: foo.pl generates foo.asm which is assembled into foo.obj. For netware you should be able to get the necessary rules by adding the assembly language files into the Configure entry. You might want to handle things in a way similar to windows by chekcing out the function win32_import_asm in util/pl/VC-32.pl a lot of the functionality which was done in the batch file can then be removed. 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
