-Coders,
several of our mib modules only build on particular platforms. If a user
chooses to configure with a mib module that's not supported on his/her
platform, we currently tend to fail at compile time. A significant
number of postings on the mailing lists prove that the relationship
between the mib module being unsupported on platform X and the
particular (arbitrary) compiler error often is anything but obvious.
Do we agree that it's desirable to fail at *configure* time with a
helpful error message ("Module X is not supported on platform Y. Please
...") instead?
If so, how to accomplish this?
a) introduce some config_XXX in the mib module header files for the
*supported* platforms
b) introduce some config_XXX in the mib module header files for the
*unsupported* paltforms
c) do platform handling directly in configure[.in]
d) <insert your own>
I'd prefer a) over b) over c), unless someone comes up with a better d).
Technically, a) and b) could be done by using #ifdef and
config_warning/config_error or by a new config_arch_XXX.
Fire your comments.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
