If you figure out what it is let us know, would be good to identify a
"fix" if others run into the same problem.
On 08/12/2010 09:42 AM, Michi Mutsuzaki wrote:
Yeah, I tried installing libtool 2, but that caused some other issue. I'll
play around a bit more, and let you know if I find anything.
On 8/12/10 1:40 AM, "Patrick Hunt"<ph...@apache.org> wrote:
I've been running with v4 for a while and never noticed that issue...
You might try googling it, a quick search turned up:
"The meaning of "-static" changed between libtool 1.5 and libtool 2.x,
and libtool 2.x introduced "-static-libtool-libs" to provide the old
On 08/09/2010 11:28 AM, Michi Mutsuzaki wrote:
Running "ant jar" fixed the unit test failure.
I'm using g++ 3.4.6. Do I need later version to get rid of
$ g++ --version
g++ (GCC) 3.4.6 20060404 (Red Hat 3.4.6-9)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
On 8/7/10 11:57 PM, "Patrick Hunt"<ph...@apache.org> wrote:
What version of g++ do you have? Capture the test output and attach to
your response. However I suspect that the server is not running (it's
necessary to test the c client), did you "ant jar" (or similar - ie
build the server) before testing the client?
On 08/07/2010 04:57 PM, Michi Mutsuzaki wrote:
I'm having 2 issues while compiling/running c client unit test in
1. I get this error from "make check":
g++: unrecognized option `-static-libtool-libs'
2. testAsyncWatcherAutoReset is not working for me.
Zookeeper_simpleSystem::testAsyncWatcherAutoResetterminate called after
throwing an instance of 'CppUnit::Exception' what(): equality assertion
failed- Expected: -101- Actual : -4
Let me know if anybody has seen these errors.