[721] in Zephyr_Bugs
Re: Zephyr stuff
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Nov 6 13:53:08 1995
Date: Mon, 6 Nov 1995 13:53:51 -0500
From: Greg Hudson <ghudson@MIT.EDU>
To: Dejan Vucinic <dejan@mit1.fnal.gov>
Cc: bug-zephyr@MIT.EDU
In-Reply-To: "[720] in Zephyr_Bugs"
Thanks for the feedback.
> checking size of short... configure: error: can not run test program while
> cross compiling
I've gotten a report of this error before. Evidently something
changed in Solaris 2.4 to break our configure script. I don't
currently have time to investigate this problem (I'm taking a few
months off to graduate from college before becoming full-time staff
here), but I expect to have it fixed in late December or early
January. (It's mainly a matter of finding a convenient Solaris 2.4
environment to build in and looking at the problem.)
> 2. In ZOpenPort.c, you create a socket with
> if ((__Zephyr_fd = socket(AF_INET, SOCK_DGRAM, 0)) < 0)
> Strictly speaking, this is wrong.
The BSD 4.4 socket() man page lists AF_* as the possible values of the
domain parameter to socket(), and the first example in the BSD 21.ipc
document (from BSD 4.4, but it probably hasn't changed since dinosaurs
roamed the earth) reads "s = socket(AF_INET, SOCK_STREAM, 0);".
Although <netinet/in.h> does distinguish between address families and
protocol families, I think you're mistaken about the nature of the
domain argument to socket().
> Are you interested in incorporating [the VxWorks client] in the
> source tree?
I don't think so, for three reasons: we don't have a VxWorks system to
maintain the code on, we haven't had any demand for such a client, and
I think it would be a bad precedent to incorporate single-platform
clients for anything other than MacOS and Win32 (and there only
because of their popularity).
