Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!mucs!logitek!grep!frank
From: frank@grep.co.uk (Frank Wales)
Newsgroups: comp.sys.hp
Subject: Re: usleep [Re: BSD and HPUX, The Questions Continue...]
Message-ID: <1991May24.152658.21322@grep.co.uk>
Date: 24 May 91 15:26:58 GMT
References: <1991May2.202710.5152@odin.diku.dk> <2130012@aspen.IAG.HP.COM>
Reply-To: frank@grep.co.uk (Frank Wales)
Organization: Grep Limited, LEEDS, UK
Lines: 16

In article <2130012@aspen.IAG.HP.COM> tai@aspen.IAG.HP.COM (Tai Jin) writes:
>In comp.sys.hp, s900387@minyos.xx.rmit.oz.au (Craig Macbride) writes:
>    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.
>
>The way to make this work is to link the libraries in the correct order
>ie. cc ... -lc -lBSD
>This finds signal in libc.a and also finds the b* routines in libBSD.a.

One could also build new libraries with the disparate parts separated out
by using ar(1), as HP could have done, then link with those instead.
--
Frank Wales, Grep Limited,             [frank@grep.co.uk<->uunet!grep!frank]
Kirkfields Business Centre, Kirk Lane, LEEDS, UK, LS19 7LX. (+44) 532 500303