Opened 10 years ago
Closed 10 years ago
#46 closed defect (fixed)
libtool
Reported by: | Silvan Scherrer | Owned by: | dmik |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | libtool | Version: | |
Severity: | Keywords: | ||
Cc: |
Description
when a -release is sent to libtool it creates a wrong dll name.
as example:
-release 0.18.1 gives -0.18.1.0.0
Change History (6)
comment:1 by , 10 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:2 by , 10 years ago
comment:3 by , 10 years ago
I expect to have a similar scheme, as with -version.
libname + some suffix. Because we are limited with the length it's hard to use use all release part. As it could be xx.yy.zz. and even with points removed we would still have 6 chars. somehow going the same math as is done with -version would be ideal.
comment:4 by , 10 years ago
Note that autogen.sh
from the gettext package (which exposed the defect described by this ticket) didn't call libtoolize at all (in order to bring the appropriate libtool for the target platform). I had to fix it, see r950.
comment:5 by , 10 years ago
comment:6 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The libtool 2.4.2-8 RPM is released. Please update and test.
BTW, could you clarify what exactly do you expect in this case, which DLL name? Just to make sure I do it right.