Re: svn 1.4.2 tests fail on Solaris 9

--- Ryan Schmidt <subversion-2007a@ryandesign.com> wrote:

> [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.
>

That explains it - I also checked the FAQ and I tested one of the
failing hook scripts as suggested in the FAQ and I got the same error
about being unable to load libstdc++.so.6 when trying to run the python
binary.

The question is: how can one run the test suite when both gcc and
python are both installed to /usr/local? Surely one ought to be able
to run the test suite irrespective of where the python binary (and its
dependencies) are installed to, no?

Judging by the (general) lack of responses to my original post, it
doesn't appear that too many people have tripped up on this issue.

>
> I cannot explain why Subversion 1.3.2 would not have this problem.
>

Perhaps because none of the tests in the 1.3.2 test suite had custom
hooks calling the Python binary?

Thanks.

PS: I am already subscribed to the list, so need to CC: me on replies. :)

 
____________________________________________________________________________________
Have a burning question?
Go to www.Answers.yahoo.com and get answers from real people who know.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 25 17:07:25 2007