> Now, the first thing that jumps out is that some of the actual parameters
are 0x or 0x1000; for example:
> #14 0x13f639fd8 in serve(conn=(svn_ra_svn_conn_st *) 0x,
params=(serve_params_t *) 0x, pool=(apr_pool_t *) 0x) at
> which might suggest a stack smash, or
Mark Raymond wrote on Sat, Oct 20, 2012 at 21:48:11 +0100:
> > - C:\sasl\sasldb was created on an Ubuntu system using:
> > saslpasswd2 -c -f ~/sasldb -u madanra mark when ~/sasldb did not exist
> > before running the command, and then ~/sasldb was copied across to the
> &
> > - svnserve was then started using
> > svnserve -d -r C:\repo --log-file C:\temp\svn.log
>
> Doesn't -r need to specify a parent directory of repos to serve, not a
single repo itself?
I believe that's a common way of doing things, but it's not enforced; last
time I set up svnserve I pointed -r
Hello,
I've set up svnserve on Windows before using the inbuilt CRAM-MD5
authentication, using my own compile of SVN. I'm now trying to set up
svnserve to use SASL and DIGEST-MD5, but I'm having difficulties getting it
working.
My setup is:
- I'm on Windows 7 Professional x64
- I'm using the Tor
Thank you! This solved the XML linking issue.
The SSL_SESSION_cmd issue was solved by going back to openssl-0.9.8, as that
function was removed in openssl-1.0.0.
Mark.
From: kmra...@rockwellcollins.com [mailto:kmra...@rockwellcollins.com]
Sent: 12 March 2012 19:55
To: Mark Raymond
Cc: users
Hi,
I've been attempting to compile Subversion on Windows (64-bit). I've been
able to solve most of the issues I had when compiling, but there's just one
file left that is refusing to compile - libsvn_ra-1.dll.
The build environment is Visual Studio 2008 on Windows 7 64-bit, using the
x64 Cross To
