Re: symbol "_send_OBSOLETE_" unresolved
Thomas Anders <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
Humpolicek wrote: > I was looking for solution of this problem and I found that problem is in usage "send" and "recv" system calls. When I searched and replaced all occurences of send(*, *, *, *) with sendto(*, *, *, *, NULL, 0) and recv(*, *, *, *) with recfrom(*, *, *, *, NULL, 0) in net-snmp sources, above problems disappeared. If there's indeed a problem with send/recv on Tru64 Unix, is there any documentation on why? Any potential replacement of send() and recv() should be based on a proper configure check, of course. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users