Hi Stefan,
I made some test with Subversion 1.3.0 binaries. With the command line
client it works fine, with TSVN I have the problem reported earlier. I
realized, that Subversion uses OpenSSL version 0.9.8.0 and TSVN version
0.9.8.1.
Are sure that you set up correct compiler options? Reading the OepnSLL FAQ
(http://bs2000.fujitsu-siemens.com/download/Goodies/SMAWPlus/SMAWPossl/FAQ),
I found:
As per 0.9.8 the above limitation is eliminated for .DLLs. OpenSSL
.DLLs compiled with some specific run-time option [we recommend the
default /MD] can be deployed with application compiled with different
option or even different compiler. But there is a catch! Instead of
re-compiling OpenSSL toolkit, as you would have to with prior versions,
you have to compile small C snippet with compiler and/or options of
your choice. The snippet gets installed as
<install-root>/include/openssl/applink.c and should be either added to
your project or simply #include-d in one [and only one] of your source
files. Failure to do either manifests itself as fatal "no
OPENSSL_Applink" error.
Thanks, Jan
> > That is quite strange. TSVN is properly installed, I switched my WC
> > from https to http over VPN tunnel and it works. I rebooted several
> > times after the upgrade. The p12 certificate is correct, it worked
> > with previous version of TSVN and still works with
> IE/Mozilla. You use
> > the *same* version of OpenSSL as in TSVN 1.2.6?
>
> Other than the fact that we changed the compiler to build
> those dll's, nothing changed.
>
> Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sat Feb 18 12:32:30 2006