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

undefined symbol endl__FR7ostream

From: Holzner Werner - Munich-MR - external <wholzner_at_munichre.com>
Date: 2004-06-22 13:41:56 CEST

> Hi all,
nobody on users mailing list can or wants to help me, so I try this dev mailing list as last chance.
I'm a newby to subversion and I try hard to get it running on my (old) Debian 2.2 LINUX computer. Since I want to use subversion in my home network and my whole family should use it. So I downloaded the source tarball and build the server and the client without any problems. But command line handling is no option on our heterogenous network (LINUX, WIN98, WIN2000) with non-technicians as users. As GUI which should be the same on all environments I want to use svnup. And here the problems begin!

> Building the javahl native shared library for Java 1.4.2_04 runs with some warnings in some C++ sources but ends up without error. After installing the libraries the start of the svnup-0.8.0 GUI breaks in an exception in the JNI Library libjvnjavahl.so: undefined symbol endl__FR7ostream.
The FAQ's on subversion.tigris.org don't mention this problem at all. A search on whole tigris.org site found no entries. GOOGLE provided a hint that the shared library will not be linked with C++ Libraries. But doing the last link explizitly with g++ (instead of the libtool generated gcc) will not change anything.I've checked the versions of autoconf, automake and libtool (but here subversion uses his own shell script!) and updated some tools to the actual versions found by GNU.

> So my questions: What's wrong here? Why can't I build the native javahl JNI Library on my computer?
> Gracefully awaiting any hint or help
> Werner Holzner

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 22 13:43:31 2004

This is an archived mail posted to the Subversion Users mailing list.

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