On 05/06/2013 04:39 PM, Branko Čibej wrote: > On 06.05.2013 21:42, C. Michael Pilato wrote: >> On 05/06/2013 03:11 PM, Branko Čibej wrote: >>> It's always worked that way for me, but then, my APR doesn't change that >>> often. Sounds like a different APR is loaded at runtime than was >>> compiled against; but I can't understand why libsvn_subr would use the >>> apr_crypto API? >> See libsvn_subr/crypto.c. The logic is currently unused by trunk code. Was >> introduced for the body of work currently living on the master-passphrase >> branch. (gstein felt that the crypto bits should live on trunk even if the >> rest of the work was only on the branch.) > > Ah, I recall now, thanks. > > IIRC, the apr_crypto API was introduced in APR-Util 1.4; could it be > that you have an older somewhere that's being picked up by the bindings? > For example, my MacOS 10.8 comes with APR-Util 1.3.12.
Yeah, as I said earlier: I've got APR 1.4.5 and APR-Util 1.4.1 installed via a locally built Apache HTTP Server (in /usr/local/apache), and it's against those which all my Subversion stuff should be linked. (My system also has libapr1 1.4.6-1 and libaprutil1 1.3.12 installed via the OS package management stuffs, but nothing *should* be linked against those except other OS package contents.) My guess is also that the build was picking up the older system apr-util version, but I haven't been able to verify that yet. -- C. Michael Pilato <[email protected]> CollabNet <> www.collab.net <> Enterprise Cloud Development
signature.asc
Description: OpenPGP digital signature
