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

svn 1.4.2 tests fail on Solaris 9

From: asdf <fia_wrc_fanatic_at_yahoo.com>
Date: 2007-01-24 17:57:21 CET

I have built svn 1.4.2 on Solaris 9 using gcc-3.4.6 with the following
configure line:

./configure --enable-shared=yes --without-berkeley-db --without-ssl
--with-devrandom=/dev/urandom

When I run the test suite (make check), a number of the tests fail:

Running all tests in commit_tests.py...FAILURE
Running all tests in prop_tests.py...FAILURE
Running all tests in log_tests.py...FAILURE
Running all tests in diff_tests.py...FAILURE
Running all tests in trans_tests.py...FAILURE
Running all tests in svnsync_tests.py...FAILURE

all other tests passed. A closer look at test suite log file,
subversion-1.4.2/tests.log, reveals that the tests are failing because
they are all using hook scripts that call Python and the Python binary
failed to load/run:

EXPECTED STDOUT:
Sending svn-test-work/working_copies/commit_tests-34/iota
Transmitting file data .
Committed revision 2.

Warning: 'post-commit' hook failed with error output:
Post-commit hook failed
ACTUAL STDOUT:
Sending svn-test-work/working_copies/commit_tests-34/iota
Transmitting file data .
Committed revision 2.

Warning: 'post-commit' hook failed with error output:
ld.so.1: /usr/local/bin/python: fatal: libstdc++.so.6: open failed: No
such file or directory

EXCEPTION: SVNLineUnequal
FAIL: commit_tests.py 34: post commit hook failure case testing

And this is the same error that occurs for all the other failing tests.

What I find strange is that I am able to run Python without any
problems otherwise since /usr/local/bin is already in my PATH and
/usr/local/lib is also already in LD_LIBRARY_PATH.

I have Python 2.4.3 installed to /usr/local via the standard
"./configure && make all && make install" and this installation of
Python is also used for Subversion 1.3.2 which is currently installed
on this Solaris 9 system and which passed all of its tests without a
problem.

Can anyone explain why the Python binary would fail to load when called
from the hook scripts in the specific tests failing above?

There was one other user who reported a similar (identical perhaps?)
problem in Nov. 2006 when running the test suite on Solaris 9 but there
were no resolutions to it.

Thanks.

PS: It is worth mentioning that I built svn-1.4.2 on an AIX 5.3 machine
in a similar manner where Python is also installed to /usr/local/bin
and the test suite ran to completion without any failures.

 
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 24 17:57:53 2007

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