On Jan 24, 2007, at 10:57, asdf wrote:
> 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
[snip]
> 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
[snip]
> 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?
[snip]
Hook scripts run with an empty environment (on non-Windows operating
systems) so the variables PATH and LD_LIBRARY_PATH are *not* set
when /usr/local/bin/python is trying to locate libstdc++.so.6.
I cannot explain why Subversion 1.3.2 would not have this problem.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 24 21:49:04 2007