On Sat, 2008-07-26 at 15:11 +0100, Andy Whitcroft wrote: > Adam, how about this as an implementation of the version checks you > suggested.
This seems totally reasonable and definitely a bit simpler than I imagined... Probably due to using the HUGETLB_VERSION env variable instead of some library API call. > 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. > -apw > > Andy Whitcroft (4): > hugectl: report the version as part of the usage output > library: report the library version > hugectl: pass the tool version to the library for checking > library: check associated tools version where offered > > elflink.c | 5 +++++ > hugectl.c | 7 +++++++ > 2 files changed, 12 insertions(+), 0 deletions(-) > -- Adam Litke - (agl at us.ibm.com) IBM Linux Technology Center ------------------------------------------------------------------------- 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
