I have applied both the patch from Roumen Petrov and the Fixup from Alon
Bar-Lev.
I don't have a mingw environment to actually verify the correct
operation. Please check out the next snapshot and verify that everything
is working now as expected.
Best regards,
Lutz
Thank you!!!
Will check.
On 4/17/08, Lutz Jaenicke via RT [EMAIL PROTECTED] wrote:
I have applied both the patch from Roumen Petrov and the Fixup from Alon
Bar-Lev.
I don't have a mingw environment to actually verify the correct
operation. Please check out the next snapshot and verify that
10x Lutz,
I just synchronize my local version with cvs and left one non-important
difference - some tabs see openssl-cvs-2008018.diff.gz (may be I lost
them after copy/paste diff from browser into local file).
Alon Bar-Lev wrote:
Thank you!!!
Will check.
On 4/17/08, Lutz Jaenicke via RT
This patch is for current (0.9.8) stable.
I expect future stable version to use same name for libraries/engines
(except prefix/suffix) for different OS-es. This require more work - as
example to change build for other win32 compilers.
In simple test cases mingw (gcc 3.4.5) work well as
On Jun 26 10:46, Roumen Petrov via RT wrote:
If a remember well borland compiler don't export variables. It seems to
me that gcc (mingw) don't export too. So that should use
OPENSSL_XXX_GLOBAL for both variables?
gcc and FSF ld for i386 PE targets allow to export data symbols.
A DATA keyword
I would like to propose following patch to openssl-0.9.8e source (see
attachment openssl-0.9.8e-mingw.patch.gz).
This patch is intended to create executables compatible with other win32
compilers.
Modifications:
./Makefiles.shared:
- link_o.cygwin(used to build engines): modified use def-files
Hello Roumen,
There is partial work in snapshots regarding cross compile.
MinGW still does not work well.
I've created the following ticket:
http://rt.openssl.org/Ticket/Display.html?id=1451user=guestpass=guest
But no progress has been made in determine what is wrong.
Anyway, I think you will
