Hi Andy, > How come you were having trouble with .text segment alignment then? I I dont know... > mean if it's vanilla NASM COFF, then you shouldn't have had problem... > How old is your nasm version? Could you check this and maybe test more > up-to-date version? Or is it non-vanilla COFF? plain vanilla COFF and latest nasm versions; check self: D:\openssl-SNAP-20071203\crypto\aes\asm>aes-586.pl nw-nasm > a-nw.asm
D:\openssl-SNAP-20071203\crypto\aes\asm>nasmw -v NASM version 0.99.06 compiled on Nov 1 2007 D:\openssl-SNAP-20071203\crypto\aes\asm>nasmw -s -f coff a-nw.asm -o a-nw.o a-nw.asm:4: error: standard COFF does not support section alignment specificatio n D:\openssl-SNAP-20071203\crypto\aes\asm>e:\nasm-2.00rc1\nasm -v NASM version 2.00rc1 compiled on Nov 16 2007 D:\openssl-SNAP-20071203\crypto\aes\asm>e:\nasm-2.00rc1\nasm -s -f coff a-nw.asm -o a-nw.o a-nw.asm:4: error: standard COFF does not support section alignment specificatio n > ELF even on Win32? Then on Win32, do you compile under cygwin or mingw? > Or in other words is there working GNU make? The point is that HEAD plain Win32 OS with gnu make, no further autoconf tools required. > branch has certain support for cross-compilation, effectively meaning > that Unix-like build procedure can be applied (as opposite to generating > flat make-file and running some strange scripts), which is chosen to be > preferred. This in turn means that I'd appreciate if you could explore > this possibility. Basically read INSTALL.W32, look for cross-compile and > see if HEAD can be adapted for this even for netware. A. The Linux cross-builds are already non-mk1mf builds, and the libs are not an issue; but the executables like openssl.nlm are a bit a pain to get these properly created with configure-like builds; its better to control the exported symbols with export files - but if I use configure builds then just all symbols get exported as usual on Linux, and that's not what makes me happy since it might give naming clashes; so for now I would like to continue to use the working mk1mf builds on Win32. Also there's another problem were only with the 'official' Metrowerks compiler I can control struct alignments; gcc learned this only recently with 4.1.x version I think, but the available NetWare-cross gcc is still version 3.2.3 .... Another issue is that unless my patches go into HEAD I always have to patch around all few days to syncronize with the recent changes in HEAD; and that on two build platforms is a real pain... so once my other required patches are in HEAD I can certainly better look into any remaining issues or improvements such as trying a cross-build with MingW MSYS. here's my latest patch against recent snapshot: http://194.242.35.79/downloads/openssl/netware-openssl-SNAP-20071203.diff while trying to add the AES asm support I found that currently in HEAD the AES asm part is missing in mk1mf.pl - my patch does also add this part which I copied over from 0.9.8-stable where its included; however it seems that I'm missing something since it doesnt work: while I get the asm build rules in the netware makefile - somewhere else where the crypt library object files are build up there happens something strange = the asm object file is wrong; it gets prefixed with $(OBJ_D) and suffixed with '.o' which is wrong in this case; I've not yet found where this happens... thanks, Guenter. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
