[Trac] Re: Solaris: FAILURE in tests
we use the same and we could not get the swig library built, did you? therefor we start appreciating: * trac using genshi with 0.11 * use hg(mercurial) as addition to svn more and more. only goodie would be a mercurial plugin which would support multiple repositories. another alternative might be http://trac.edgewall.org/wiki/TracOnSolaris and use blastwave? -solo On 11/13/06, Thomas Sturm [EMAIL PROTECTED] wrote: Thomas Sturm wrote: Hello, on './configure; make; make check' I get these FAILURES: . . . Running all tests in commit_tests.py...FAILURE Running all tests in update_tests.py...success Running all tests in switch_tests.py...FAILURE Running all tests in prop_tests.py...FAILURE Running all tests in schedule_tests.py...success Running all tests in log_tests.py...FAILURE Running all tests in copy_tests.py...success Running all tests in diff_tests.py...FAILURE 1.) My system is an Solaris: 5.8 Generic_117350-29 sun4u sparc and I use the 'gcc' version 3.4-gnupro-04r1-6p1 2.) Running 'commit-tests.py': EXPECTED STDOUT: /utils/src/build/subversion-1.4.2/subversion/tests/cmdline/svn-test-work/repositories/commit_tests-15 /utils/src/build/subversion-1.4.2/subversion/tests/cmdline/svn-test-work/repositories/commit_tests-15 1 /utils/src/build/subversion-1.4.2/subversion/tests/cmdline/svn-test-work/repositories/commit_tests-15 2 ACTUAL STDOUT: EXCEPTION: SVNLineUnequal XFAIL: commit_tests.py 15: hook testing EXPECTED STDOUT: Sendingsvn-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: Sendingsvn-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: post-commit: fatal: libstdc++.so.6: open failed: No such file or directory EXCEPTION: SVNLineUnequal FAIL: commit_tests.py 34: post commit hook failure case testing -- 3.) It sounds very complicated _not_ to use './configure; make; make check; make install;' :( 4.) If I rerun 'make check' some other tests FAIL and some failed tests PASS??? Regrads -- Thomas Sturm ALCATEL Transport Solutions Deutschland GmbH Colditzstrasse 34-36 ALCA-Tel. 2520 3714 D 12099 Berlin, Germany Tel. +49 30 7002 3714 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Solaris: FAILURE in tests
Thomas Sturm wrote: Thomas Sturm wrote: Hello, on './configure; make; make check' I get these FAILURES: . ... 1.) My system is an Solaris ... and I use the 'gcc' ... This has nothing to do with Trac. Please have a look at http://trac.edgewall.org/wiki/TracSubversion#AskingforMoreSupportAboutSubversion -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Solaris: FAILURE in tests
Thomas Sturm wrote: Hello, on './configure; make; make check' I get these FAILURES: . . . Running all tests in commit_tests.py...FAILURE Running all tests in update_tests.py...success Running all tests in switch_tests.py...FAILURE Running all tests in prop_tests.py...FAILURE Running all tests in schedule_tests.py...success Running all tests in log_tests.py...FAILURE Running all tests in copy_tests.py...success Running all tests in diff_tests.py...FAILURE 1.) My system is an Solaris ... and I use the 'gcc' ... 2.) Running 'commit-tests.py': EXPECTED STDOUT: /utils/src/build/subversion-1.4.2/subversion/tests/cmdline/svn-test-work/repositories/commit_tests-15 /utils/src/build/subversion-1.4.2/subversion/tests/cmdline/svn-test-work/repositories/commit_tests-15 1 /utils/src/build/subversion-1.4.2/subversion/tests/cmdline/svn-test-work/repositories/commit_tests-15 2 ACTUAL STDOUT: EXCEPTION: SVNLineUnequal XFAIL: commit_tests.py 15: hook testing EXPECTED STDOUT: Sendingsvn-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: Sendingsvn-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: post-commit: fatal: libstdc++.so.6: open failed: No such file or directory EXCEPTION: SVNLineUnequal FAIL: commit_tests.py 34: post commit hook failure case testing -- 3.) It sounds very complicated _not_ to use './configure; make; make check; make install;' :( 4.) If I rerun 'make check' some other tests FAIL and some failed tests PASS??? Regrads -- Thomas Sturm ALCATEL Transport Solutions Deutschland GmbH Colditzstrasse 34-36 ALCA-Tel. 2520 3714 D 12099 Berlin, Germany Tel. +49 30 7002 3714 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Solaris: FAILURE in tests
It looks like your subversion swig-py bindings are missing, which by the make set your using there they almost definatly are. Plus you havn't given us any information on how you did you dependancies for subversion and whether your running this system on an apache server or using tracd and svnserve or some other configuration. As such I'm just going to dump a series of notes here that cover all the fun issues I've had with Subversion in a linux enviroment. First: You should not under any circumstance allow subversion to build it's dependancies as part of its ./configure and make commands. They never work correctly and they use a bunch of defunct default compile commands that will pretty much guarantee they never work correctly. -SO- move all the dependancies that are important (apr, apr-util and neon. Leave zlib it works fine). Then build them yourself, if you're using apache do not build apr and apr-util, you want to use your apache servers versions (or nothing will ever work correctly, trust me.) so build neon with shared and static libs enabled as part of it's configure command, you can do other things here too it has a copius amount of options. Then go back to your subversion build, before you build it you need to do 2 things. Run apr-config --version and apu-config --version, if they are less than version 1 do a locate for apr-1-config and apu-1-config (this all assumes your using apache 2.2 which creates these files) these are the actual copies you want to be using for apr / apr-util. -SO- rename the old apr-config and apu-config, then symbolic link the apr-1-config and apu-1-config to where they used to be. Now run ./configure for subversion and tell it where the apxs binary is for apache (again assuming you are using apache) and give it any other config commands you might want like telling it to build with python support (important for trac). Instead of the default make that you showed use this: make make swig-py. Let that cook then you can try make check (not sure if there is a make check-swig-py). And finally do a make install make install-swig-py. This should get your python bindings configured correctly. -Garrett McGrath --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Solaris: FAILURE in tests
Thomas Sturm wrote: Hello, on './configure; make; make check' I get these FAILURES: . . . Running all tests in commit_tests.py...FAILURE Running all tests in update_tests.py...success Running all tests in switch_tests.py...FAILURE Running all tests in prop_tests.py...FAILURE Running all tests in schedule_tests.py...success Running all tests in log_tests.py...FAILURE Running all tests in copy_tests.py...success Running all tests in diff_tests.py...FAILURE . . . Has anybody successfuly build and tested 'subversion 1.4.2' on Solaris? You should probably ask on the SVN mailing list [EMAIL PROTECTED] - this one is for Trac. -- Gary Thomas | Consulting for the MLB Associates |Embedded world --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
