Re: trouble comiling on NeXT

• Date: Fri, 22 Dec 1995 09:37:17 PST
• From:
  Pavel Curtis <pavel@parc.xerox.com>
• In-reply-to: Ray Bloom's message of "Thu, 21 Dec 1995 18:50:14 PST" <9512220250.AA20289@dsd.camb.inmet.com>

Ray Bloom writes:
> >my-signal.h:34: undefined type, found `sigset_t'
> >my-signal.h:35: undefined type, found `sigset_t'
> >my-signal.h:39: undefined type, found `sigset_t'
> >my-signal.h:39: undefined type, found `sigset_t'
> 
> I'm having the same problem compiling 1.7.9p2 on NeXT.

The problem is that the NeXT folks provide certain POSIX functions
(sigemptyset, sigaddset, and sigprocmask) but don't declare the type of their
arguments (sigset_t) in the right header file <signal.h>.  If someone will tell
me where they *do* declare that type (*if* they do), I'll try to add a case to
the configuration script to work around NeXT's bug.

	Pavel

• Re: trouble comiling on NeXT
• From: Matthew Wojcik <woj@k2.ccs.neu.edu>

• Re: trouble comiling on NeXT
• From: bloom@dsd.camb.inmet.com (Ray Bloom)

• Prev: Re: trouble comiling on NeXT
• Next: Re: trouble comiling on NeXT
• Index: MOO-cows
• Thread: MOO-cows