On 08/14/2010 04:30 AM, Stephen Warren wrote:
On 08/13/2010 01:27 AM, Phil Dibowitz wrote:
On 08/13/2010 04:40 AM, Stephen Warren wrote:
On 08/12/2010 10:16 AM, Phil Dibowitz wrote:
On Thu, Aug 12, 2010 at 04:55:25PM +0100, Chris Mayo wrote:
In 0.22 libconcord.py sets: ABI_VERSION = 2
On 08/14/2010 08:50 PM, Stephen Warren wrote:
No, that's not correct; it should be 1 given the current libconcord.so
settings. If you run ldd on the concordance application, you'll see that
it searches for libconcord.so.1 (the soname), which is then symlinked
to libconcord.so.1.1.0 (the
On 08/14/2010 11:14 PM, Phil Dibowitz wrote:
On 08/14/2010 08:50 PM, Stephen Warren wrote:
No, that's not correct; it should be 1 given the current libconcord.so
settings. If you run ldd on the concordance application, you'll see that
it searches for libconcord.so.1 (the soname), which is
On 08/13/2010 04:40 AM, Stephen Warren wrote:
On 08/12/2010 10:16 AM, Phil Dibowitz wrote:
On Thu, Aug 12, 2010 at 04:55:25PM +0100, Chris Mayo wrote:
In 0.22 libconcord.py sets: ABI_VERSION = 2
causing it to look for libconcord.so.2
Crap. That should have gone 0 - 1, not 0 - 2.
I have
On 08/12/2010 10:16 AM, Phil Dibowitz wrote:
On Thu, Aug 12, 2010 at 04:55:25PM +0100, Chris Mayo wrote:
In 0.22 libconcord.py sets: ABI_VERSION = 2
causing it to look for libconcord.so.2
Crap. That should have gone 0 - 1, not 0 - 2.
I have to release a 0.23 this weekend anyway, I'll fix
