Closed jgriffiths closed 10 months ago
Version-info of 2:0:1
should result in a .so.1.1.0
; that is correct.
I suspect the problem with the spaces may be that Make is including the whitespace between the variable values and the comment characters. Try putting the comments on their own lines.
Yep the comments were the problem, fixed and pushed, thanks!
In
src/Makefile.am
we now have:These values were introduced in dbbf1538aebc31ffd72a5b4b26072eeadde20b27, and have been updated for version 1.1.0 with the expectation that the resulting DSO will be numbered
.2.0.1
or possibly.2.1.0
if the comment in the makefile is correct,However, building now results in the following in
src/.libs
:i.e. revision and age appear to be ignored.
It seems like the call to
libtool
is passing-version-info 2 :0 :1
for some reason, possibly to do with the colon character. However, if I manually change the call inmakefile.am
to pass2:0:1
directly, I get the following insrc/.libs
:Which makes no sense to me at all.
I've tried various quoting options but no joy. @whitslack given the DSO versioning was added to support gentoo builds, can you take a look? I'm attempting to be a good citizen by bumping the version appropriately, but obviously that requires that this support works. This is mildly holding up the 1.1.0 release btw (I'm waiting for 2fa PyPI setup but otherwise the release is ready).