[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Problems with BDB file access

From: Jens Peters <jpeters7677_at_gmx.de>
Date: 2006-01-21 17:52:43 CET

> I don't think you have to patch all header files. Usually,
> there's one header file which is included in every other
> header file. At least, that's the case for all apr libs and
> Subversion.

Actually at the time when I wrote this email I was still playing with
compiling bdb. The libs had compilid well, but I got some error in the
example programs (excxx...exe) because they did not include db_config.h I
could easily fix it by putting the define at the top of the source files but
I don't wanted to do that for eventually other problems in other sources and
so I looked for a more global solution. Anyway, I added

#ifndef _CRT_SECURE_NO_DEPRECATE
#define _CRT_SECURE_NO_DEPRECATE
#endif
#ifndef _CRT_NONSTDC_NO_DEPRECATE
#define _CRT_NONSTDC_NO_DEPRECATE
#endif
#ifndef _USE_32BIT_TIME_T
#define _USE_32BIT_TIME_T
#endif

at the top of my crtdefs.h and

#ifndef _CRT_SECURE_NO_DEPRECATE
#define _CRT_SECURE_NO_DEPRECATE
#endif

at the top of my sys\types.h. After doing so I were able to compile all the
stuff (openssl,bdb,apache, even gettext :) ) without problems.

My own test shows that accessing an old bdb repos went fine and the standard
subversion test suite succeeded as well (expect two tests with the
property/wildcard things, but this is expected and already fixed in trunk as
far as I know). So I still feel a little bit weird about changing the crt
includes, but it seems to work :)

.
.

By the way, in a first attempt I compiled subversion with the new
neon-0.25.5 without the sspi support (#undef have_sspi). When I started the
svn test suite the first time with mod_dav_svn the tests were failing
instantly, because commands like:

svn --username rjandom --password ...

arrived at the apache with my domainname in front of it: domain\\rjandom. Of
course apache returned a authorization failed. I took the 0.25.4 version,
disabled sspi support, and got the same result. Did you got something like
this in your builds?

Now I'm running the suite with 0.25.5 sspi enabled and the tests are running
quite well. But in this case --username and --password is simply completely
ignored and neon always passes my own credentials. I don't know if I like
that, I would prefer the old situation over that. But I already read that
the neon guys have plans to implement changing the authenticate method at
runtime. So lets wait for svn 1.4.

Greetings,
Jens

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Jan 21 17:53:52 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.