On Dec 16, 2004, at 12:38 PM, Paul Thomas wrote:

Unfortunately, there is no connection between the quoted Man-Page-snippet
and QNX.

So what's the "TCP/IP Library Reference", whence that man page snipped came, a manual for?


I Googled for "TCP/IP Library Reference" and "System Library Functions" and found

        http://ecos.sourceware.org/docs-2.0/ref/tcpip-library-reference.html

eCos is an OS for use in real time embedded applications, just as that's at least one use for QNX, but, as far as I know, they're different OSes. (I guess the folks at Cygnus were the ones who forgot to fix the man page to speak of the version of eCos in which "getifaddrs()" first appeared rather than the version of OpenBSD in which it first appeared.)

Is the "getifaddrs()" you're using part of QNX4, or is it from some add-on library, e.g. taking the eCos implementation and porting it to QNX4?

If it's part of QNX4, then is it in a documented library?

If so, does its documentation talk about <ifaddrs.h>? If so, then QNX-the-company *should* support it, modulo having put QNX4 on life support. If not, then what does the documentation say it should include?

        If not, you might have to ask QNX for help in using it.

If it's part of some add-on library, then is the possibly-eCos documentation the official documentation for it? If so, then whoever supplied the library should also supply the header file. If not, is there official documentation and, if so, what does it say?

That would be different if this were QNX6 ("Neutrino/Momentics"), which
suggests the possibility that I might be able to get the missing file(s) from that
source as well as OpenBSD (which is free, or even FreeBSD for that matter).

There's no guaranteed that the "getifaddrs()" implementation you're using necessarily matches the header file for another implementation - they might have different definitions of "struct ifaddrs". That might not be *likely*, but it's not impossible....


-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.

Reply via email to