n8743196@unicorn.WWU.EDU (jeff wandling) (07/12/90)
I'm using a Motorola 68020 operating under sysV release 3. I'm trying to do some work with sockets. When I compile the code I get the response that the following are undefined: gethostname.o gethostbyname.o bzero.o inet_ntoa.o vfork.o sigmask.o sigblock.o sigsetmask.o These are supposed to be in some /usr/include file right? Or in some /usr/lib file? Which? I've grep'ed all over and can not find these calls any where in /usr/include and /usr/lib. I'm beginning to think our system does not support them. So, is there anyone out there willing to send me the source /usr/include, etc.. files that would support the calls (see above for list). If these calls are really on sysVr3 but under a different name, info on that would be helpful too. -- @desc me=jeff wandling n8743196@unicorn.wwu.edu jeff@arthur.wwu.edu
james@dlss2.UUCP (James Cummings) (07/12/90)
You're probably right, they're NOT THERE! System V (whatever ver) has IPC (inter-process communications) calls not sockets or, as I'm fond of calling them bsd-isms. Have fun porting from the BSD4.3 world to SysV! You'll have to re-write some of the code. -- =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ |Disclaimer: | James Cummings | | You can't blame me! | UUCP: | | I'm ignorant! | ..swblat!{texbell!texnet.. | |+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+| swgate!dlss1..}!dlss2!james | |Send flames to: | NET: | | sowc@devnull.com | jc@smunews | | | | =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
guy@auspex.auspex.com (Guy Harris) (07/14/90)
> You're probably right, they're NOT THERE! System V (whatever ver) >has IPC (inter-process communications) calls not sockets Wrong answer, next contestant please. S5R4 *does* have the socket calls; they're implemented atop streams and TLI. S5R3, as it comes from AT&T, doesn't have sockets, but it does have streams/TLI, which occupy pretty much the same ecological niche as sockets. Many TCP/IP packages for S5R3 come with a sockets emulation library, although they probably emulate less of the behavior of sockets than does the S5R4 emulation code. The IPC calls do *not* occupy the same niche in most systems; they don't work over networks.