Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!munnari.oz.au!goanna!minyos.xx.rmit.oz.au!s900387 From: s900387@minyos.xx.rmit.oz.au (Craig Macbride) Newsgroups: comp.sys.hp Subject: Re: BSD and HPUX, The Questions Continue... Message-ID: <1991May20.122602.6838@minyos.xx.rmit.oz.au> Date: 20 May 91 12:26:02 GMT Article-I.D.: minyos.1991May20.122602.6838 References: <1991May2.202710.5152@odin.diku.dk> <67870026@hpcupt1.cup.hp.com> <28356926.3abe@petunia.CalPoly.EDU> Organization: Royal Melbourne Institute of Technology, Melbourne, Australia Lines: 32 jdudeck@polyslo.CalPoly.EDU (John R. Dudeck) writes: >I don't understand. I just wasted many tens of hours trying to port a >large package (the PP X.400 system) to HP/UX, which broke signal() >because I was trying to use -lBSD in order to get the b*() functions. Join the club. I love the way the on-line docs say how signal() works and how the BSD sigset() (etc) commands work, and then HP slips a BSD signal() into the same library as bzero(), etc, so that you can't use these routines without breaking (or rewriting) all your signal-handling. >I finally had to take out -lBSD and use macros for the b* stuff. Ditto. >Why would you want to force -lBSD when it breaks SYS5 code? You wouldn't. If HP had had any brains, they would have kept the utility funtions (bzero, etc) separate from functions which break existing code. But then, if HP were really into doing things properly, they'd have ported NCS in its entirety, too, or at least not kludged it by having servers send themselves signals every second. (!) They also haven't bothered to include usleep(), so BSD programs which want that routine can't be compiled without a bit of work either. -- _--_|\ Craig Macbride / \ \_.--.*/ v