I am seeing strange errors (EINVAL) logged from binaries compiled under
DEC Unix 3.2D if run under True64 5.0 (but the same binary runs fine
under 4.0x). These errors pop up in recvmsg and sendmsg system calls. A
quick and dirty test with one of the many modules tells me that if I
recompile under 5.0 that the problem goes away.
From perusing the struct msghdr I would believe this could be due to the
change of of the type of msg_iovlen in one of the variants, but
shouldn't this change be invisible to old binaries? Or is binary
compatibility limited in this area and 3.2 stuff does not run on 5.0?
Jens-Uwe Mager <pgp-mailto:62CFDB25>