Hi,
In the process of building the Debian package for 2.0.12, I noticed
Makefile.am contains VERSION_INFO=6:1:1, but the generated libs have all
SONAME=*.so.5
I'm still parsing through the build-system (I'm the new guy helping with
this package) trying to figure out what's going on, but decided t
On Fri, Jun 17, 2011 at 6:25 AM, Leo 'costela' Antunes
wrote:
> Hi,
>
> In the process of building the Debian package for 2.0.12, I noticed
> Makefile.am contains VERSION_INFO=6:1:1, but the generated libs have all
> SONAME=*.so.5
>
> I'm still parsing through the build-system (I'm the new guy hel
On 17/06/11 17:42, Nick Mathewson wrote:
> * AGE: With how many previous versions of the ABI is "Current"
> version backward-compatible? This increments whenever the ABI changes
> in a backward compatible way, and
h, that's the catch I merrily overlooked!
> According to the libtool source,
On Fri, Jun 17, 2011 at 12:11 PM, Leo 'costela' Antunes
wrote:
> On 17/06/11 17:42, Nick Mathewson wrote:
>> * AGE: With how many previous versions of the ABI is "Current"
>> version backward-compatible? This increments whenever the ABI changes
>> in a backward compatible way, and
>
> h, tha
Hi,
Sorry for the delayed answer.
On 20/06/11 19:52, Nick Mathewson wrote:
>> But since I got your attention, I'll plug a follow-up question about the
>> build-system: what's the reason for setting BUILD_WITH_NO_UNDEFINED only
>> for cygwin and win32?
>>
>> I'm currently patching the packages to
