Stephen R. van den Berg wrote:
I've reenabled socketpair_ultra in a few more cases (for systems where UNIX_SOCKETS_WORKS_WITH_SHUTDOWN hasn't been set).
Is the recent MacOSX breakage a result of this capability not properly being diagnosed in configure?
Found and (sort of) fixed this.
Summary of the changes: - Closing a socket one-way, results in errors when still trying to get OOB data from it. I.e. the OS signals an error because it knows that OOB data cannot be sent anymore. - At least Linux returns EOPNOTSUPP in this case. - At least FreeBSD returns ECONNRESET in this case. - MacOSX returns EOPNOTSUPP, with a value of errno == 102. However, with MACOSX_DEPLOYMENT_TARGET=10.3 set in smartlink, the compilation results in a EOPNOTSUPP definition of 45, which doesn't work if the kernel still returns 102. Therefore I disabled the MACOSX_DEPLOYMENT_TARGET=10.3 macro. Not sure what negative impact this has. People with MacOSX experience, please look into it (I merely tested it on my Leopard MacBook).