Johannes Schmidt-Fischer wrote:
I think it's not sufficient to check whether nlist64() is available but configure must check to whether the kernel is a 32-bit or 64-bit kernel (well, the second check is only necessary if nlist64() exists). This just in case that even with a 32-bit kernel the 64-bit functions are available in the system libraries (they might not work there - but that's another thing).
Exactly. See my other recent message in this thread.
When building binary tarballs for IRIX it's then necessary to decide what versions should be supplied (if any are to be supplied at all): - 32-bit binaries using nlist() - 32-bit binaries using nlist64() - 64-bit binaries using nlist64()
This'd be the consequence of doing the decision at compile-time, yes. Isn't this actually the best reason for deferring the decision to runtime instead? Isn't it just The Right Thing To Do anyway? :-)
+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 Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
