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

Re: 1.7 check-swig-py failure

From: tsteven four <tsteven4_at_gmail.com>
Date: Fri, 29 Jul 2011 11:33:32 -0600

>
> 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 expat to avoid a dependency on
/usr/lib64/libexpat in other libs such as libaprutil,
libsvn_subr, etc. because that was bringing in /usr/lib64 which caused the
wrong libapr to be found. The internal
expat solved that, but the same issue has cropped up again now in the
binding libraries.

Interestingly all installed libs are correct, it is just an issue before
installation. All the installed libs refer to the correct
libexpat, libapr, libaprutil.
Received on 2011-07-29 19:34:05 CEST

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