Re: symbol "_send_OBSOLETE_" unresolved

On 13/02/2008, Thomas Anders <[email protected]> wrote:
> >       I was looking for solution of this problem and I found that problem
> > is in usage "send" and "recv" system calls.


> If there's indeed a problem with send/recv on Tru64 Unix, is there
> any documentation on why?

A quick Google search for Tru64 documentation shows that there
seem to be two declarations for the send() call:

    ssize_t send(int socket,
          const void *buffer, size_t length, int flags );
and

    int send(int socket,
          char *message, int length, int flags );

Further poking around seems to indicate that the first is for
X/Open-style sockets, while the second is the BSD format.

The use of send() in the Net-SNMP library is mostly confined
to the various snmplib/*Domain.c files (in the relevant
netsnmp_{transport}_send() routine), and follow the BSD model.

A couple of these already use "sendto" (IPX, UDPv4 & v6),
and the others could probably be amended pretty quickly.

My one surprise is that this actually fixes the problem, since
the same BSD/XOpen difference exists with sento/recvfrom as well.

Dave

-------------------------------------------------------------------------
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