Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

runrig (3385)

runrig
  dougwNO@SPAMcpan.org

Just another perl hacker somewhere near Disneyland

I have this homenode [perlmonks.org] of little consequence on Perl Monks [perlmonks.org] that you probably have no interest in whatsoever.

I also have some modules [cpan.org] on CPAN [cpan.org] some of which are marginally [cpan.org] more [cpan.org] useful [cpan.org] than others.

Journal of runrig (3385)

Thursday January 19, 2006
01:16 PM

Svn dll hell

[ #28403 ]

After installing the perl svn bindings on a coworkers machine, and trying to run my latest utility, we got an error (something like entry point not found in libeay32.dll). Turns out he had old versions of a couple of dlls in c:\Windows\system32...and they were registered to some program in the registry (but we can't tell what) so we've just renamed them to ".sav" for now.

I upgraded my TortoiseSVN to the latest version, and if you're stuck with Windows, then you really must get TortoiseSVN, the revision graph is pretty, and much improved over how it used to be.

It occured to me that I had 3 copies of the svn related libraries (svk/svn/TortoiseSVN), so just for kicks, I uninstalled svk and svn (svn needed upgrading anyway), put the Tortoise dlls in the PATH, installed the latest perl svn bindings, and tried running my Perl/Tk/svn utility. I got an error: 'procedure entry point _apr_time_ansi_put@8 could not be located in the dynamic link library libapr.dll'. So the libraries are not compatible...drag. I installed svn 1.3.0 and everything worked again.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.