On Thu, Jul 31, 2008 at 04:15:10PM +0100, Andy Whitcroft wrote:
> Now that we have tools (such as hugectl) which interact directly with the
> library it is good to know the versions of both in the debugging output
> and good to check that the versions match. Where they do not report that
> as a WARNING.
>
> I checked that the library does not currently report its own version, so
> this is not duplicate any output. I also moved this whole lot out of
> elflink.c to debug.c where (as Nish suggested) it fits better. Finally
> I made the variable more specific to its job.
Hrm. I have mixed feelings about this.
In general compatibilities between libraries and tools should be
handled by using a different soname for incompatible library versions.
Now I realise that we have some unusual considerations here, we're not
exactly a typical shared library. But I still wonder whether rolling
our own version matching system is wise.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libhugetlbfs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel
