It seems clear that trac-admin is linking with version of some library that it wasn't built against. Since you compiled everything on your machine, it's probably just a matter of making it find the version you built it with first.
Use the LD_LIBRARY_PATH environment var to specify places that the linker should look *first* (before system lib directories). If that doesn't work, I'd use 'ldd' to figure out exactly what's going on. One thing you could do is compare the results of ldd -r /path/to/bin/svn and ldd -r /path/to/bin/trac-admin That will tell you which versions of what libraries are getting loaded. Good luck, Matt Chris Carline wrote: > Hi folks, > > I've been battling with a subversion/trac installation under SuSE 9.2 > (x86) for the best part of a week, and I really don't know what's > going wrong. Subversion (1.3.0) appears to have successfully > installed, along with the python bindings (under swig) and all of the > appropriate dependencies. > > Unfortunately, when it comes to actually setting up a project instance > using trac-admin, things start to go wrong, with the error > "libsvn_diff-1.so.0: undefined symbol: svn_stream_printf_from_utf8" -- > a quick 'nm' confirms this. > > I cannot for the life of me work out what is causing this problem -- > googling (a lot!) has lead me all over the place in terms of trying > different things, but all for nought. I just wondered if anyone else > had experienced anything like this, and could offer any suggestions as > to what I must be doing wrong? > > All of the dependencies have been compiled from source (no rpms or > conflicts with previously-installed versions of packages, as far as I > can tell) but I simply can't seem to get the installation to work > (although subversion itself seems perfectly happy). > > I've successfully built an svn/trac system before (against version 1.1 > of svn) and even though that was a little fraught due to swig > shenanigans, the libraries at least seemed to compile and work as > expected. > > The only thing that differs from before is that I've built all of the > libraries and dependencies in a non-standard place (added correctly to > ld.so.conf, followed by an ldconfig), due to me not wanting to pollute > other parts of the server installation. > > So if anyone has any ideas, I'd greatly appreciate your input (and if > this seems to be a more subversion-oriented issue I'd be happy to take > it off to the appropriate places). > > A 'python -c "from svn import client"' reports no errors, but I'm > guessing that what I'm seeing is caused by something a bit deeper down > the toolchain. > > I'm not quite sure what additional detail I could/should supply beyond > the information in this email, so if there's anything else that might > be helpful in getting to the bottom of this, please let me know and > I'll post it back to the list. > > Thanks, > > Chris > _______________________________________________ > Trac mailing list > [email protected] > http://lists.edgewall.com/mailman/listinfo/trac _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
