Re: 1.7 check-swig-py failure

2011-08-03 Thread tsteven four
Thanks for your consideration of this issue. Unfortunately I have to apologize, this is not an issue with r878293. The issue arises when you are building subversion against apr/apu that has already been installed in a special location, was built with the internal expat, and there is another incom

Re: 1.7 check-swig-py failure

2011-08-01 Thread Daniel Shahaf
I can't keep track of the chain of reversions there. Can you post this to dev@ please with a description of the regression --- i.e., how specifically the results you get from invocation X in 1.6.x differ from the results of X in 1.7.0-beta2, and where do you think configure.ac/Makefile.in are wron

Re: 1.7 check-swig-py failure

2011-08-01 Thread tsteven four
I believe I have chased this down to r878293, a change to apr.m4 and aprutil.m4. SVN_APR_LIBS and SVN_APRUTIL_LIBS used to be set based on --link-libtool, now they are set on --link-ld. But when building the swig-py target the libraries are linked with libtool and thus according to the apr-1-conf

Re: 1.7 check-swig-py failure

2011-07-29 Thread Daniel Shahaf
Stefan Sperling wrote on Fri, Jul 29, 2011 at 18:32:40 +0200: > On Fri, Jul 29, 2011 at 09:12:57AM -0600, tsteven four wrote: > > ldd and readelf shown above. Is there some method to get python use the > > RPATH in libsvn_ra_serf as ldd does so the correct libapr is found, or is > > the python che

Re: 1.7 check-swig-py failure

2011-07-29 Thread tsteven four
> > Is libpython.*.so in /usr/lib64, by chance? > yes In my build I get this (quote from swig/python/_wc.la:) Not sure what the is about, but in my _wc.la file the only reference to /usr/lib64 is in dependency_libs, which includes /usr/lib64/libexpat.la. My apr-util is built with the internal e

Re: 1.7 check-swig-py failure

2011-07-29 Thread Stefan Sperling
On Fri, Jul 29, 2011 at 10:48:47AM -0600, tsteven four wrote: > Thanks, I will look at your workarounds. > > On my system the troubles seem to be because /usr/lib64 gets put into RPATH > in all the .so libs in subversion/bindings/swig/python/* (including the > subdirectories). It is put in RPATH

Re: 1.7 check-swig-py failure

2011-07-29 Thread tsteven four
Thanks, I will look at your workarounds. On my system the troubles seem to be because /usr/lib64 gets put into RPATH in all the .so libs in subversion/bindings/swig/python/* (including the subdirectories). It is put in RPATH before the path element for the apr, apr-util that I have built. If I u

Re: 1.7 check-swig-py failure

2011-07-29 Thread Stefan Sperling
On Fri, Jul 29, 2011 at 09:12:57AM -0600, tsteven four wrote: > ldd and readelf shown above. Is there some method to get python use the > RPATH in libsvn_ra_serf as ldd does so the correct libapr is found, or is > the python check overriding RPATH with > some method like LD_LIBRARY_PATH? Yes, you

1.7 check-swig-py failure

2011-07-29 Thread tsteven four
I get the following error when trying to make check-swig-py: /usr/bin/python > /apps/install/subversion-1.7.0-beta2-Linux_x86_64/subversion/bindings/swig/python/tests/run_all.py > Traceback (most recent call last): > File > "/apps/install/subversion-1.7.0-beta2-Linux_x86_64/subversion/