Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!nsc!amos
From: amos@nsc.nsc.com (Amos Shapir)
Newsgroups: comp.sys.nsc.32k
Subject: Re: SYS V.3 signals on an OPUS 32532, where is sigset?
Message-ID: <13529@nsc.nsc.com>
Date: 18 Jan 90 01:14:07 GMT
References: <44258@wlbr.IMSD.CONTEL.COM>
Organization: National Semiconductor,  Santa Clara
Lines: 14

In article <44258@wlbr.IMSD.CONTEL.COM> sfl@wlv.imsd.contel.com (Steve LeFevre) writes:
>My problem is that on a OPUS 32532 system running V.3 I
>get unresolved references for _sigset when I try the above method. A search
>through the libraries doesn't find sigset, signal is in libc; but no sigset.
>I already know OPUS didn't implement shared libraries in their V.3, did they
>forget the new signals also? If not where did they hide sigset?

Sigset was added to sysV.3.2 only since V.3.2; I think Opus's port is
of an earlier version.

-- 
	Amos Shapir				My other CPU is a NS32532
National Semiconductor, 2900 semiconductor Dr., Santa Clara, CA 95052-8090
amos@nsc.com or amos%taux01@nsc.com