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
aaaah, that's the catch I merrily overlooked!
> According to the libtool source, different shared-library systems
> build their version numbers in different ways. Linux does
> "{Current-age}.age.revision"; freebsd does "current.revision"; Irix
> gets downright weird, and so on.
>
> So yeah; nothing to worry about here. :)
Indeed, makes all the sense in the world now.
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 always use it (reasons outlined
here[0]) and haven't run into any problems, but maybe I'm overlooking
something obvious again.
If not, would you accept a patch to turn it into a configure-time
option? (besides keeping it on for cygwin and win32, of course)
Cheers
[0] http://wiki.debian.org/ToolChain/DSOLinking
--
Leo "costela" Antunes
[insert a witty retort here]
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://lists.monkey.org:8080/listinfo/libevent-users
