James Carlson wrote:
Darren Reed writes:
[EMAIL PROTECTED] wrote:
As meem said "because no-one else has this split and it makes developing
code harder"...
Meem is wrong about this.
HP-UX (at least some versions of 10.* and 11.*) have a seperate nsl library.
Whether anyone cares about that is another matter...
The System V holdouts are rare and few. Virtually all other systems
don't torture application writers in this way, and the existing split
*does* make things tough on users. It's not uncommon at all to try to
compile source code, see a pile of undefined "socket" references, and
have to hack around with LDFLAGS or ./configure options or some such
to get things to work right.
Some users just assume that Solaris doesn't support BSD sockets and
end up walking away.
Note that I was referring to libnsl only, not libsocket.
In this instance, HP-UX doesn't have a libsocket, only libnsl.
For some reason IRIX slipped under my radar...but I'm not at
all sure which versions of that require one or both of these
(I don't currently have any access to IRIX boxen.)
I would be interested to see a survey of System V Unixes to
see which still had libnsl/libsocket, when they transitioned (if
they have), etc.
I'm curious to know if you're referal to "System V holdouts" is
more a reference to the existance of current/modern "System V"
unix as opposed to Linux/BSD (which seem to dominate a large
portion of the space today.)
Darren
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
