On Thu, Dec 26, 2002 at 12:27:43PM -0600, Dan Nelson wrote:

> In the last episode (Dec 26), Donn Miller said:
> > Just tried compiling the mgv port on current.  It bombs out with the 
> > following error message:
> > 
> > >Making all in toolbar
> > >cc -DPACKAGE=\"mgv\" -DVERSION=\"3.1.5\" -DHAVE_PUTENV=0 -DUSE_DMALLOC=0 
> > >-DHAVE_XPM=1 -DHAVE_X11_XPM_H=1 -DHAVE_MOTIF=1 -DHAVE_LIBHELP=0 
> > >-DHAVE_EDITRES=1  -I. -I. -I. -Iwlib -I/usr/X11R6/include -O2 -Os -pipe 
> > >-march=pentium3 -D_POSIX_SOURCE  -I/usr/X11R6/include -c Ghostview.c
> > >Ghostview.c: In function `Input':
> > >Ghostview.c:487: structure has no member named `sa_handler'
> > >Ghostview.c: In function `StopInterpreter':
> > >Ghostview.c:1529: structure has no member named `sa_handler'
> > >*** Error code 1
> > >
> > >Stop in /usr/ports/print/mgv/work/mgv-3.1.5.
> > >*** Error code 1
> > >
> > >Stop in /usr/ports/print/mgv.
> > 
> > It looks like it should compile, but it doesn't.  I mean, <sys/signal.h> 
> > does have a #define for sa_handler.
> 
> But not in the -D_POSIX_SOURCE case.  Could someone with the POSIX spec
> see whether sa_handler is supposed to be visible or not?

>From the SUSv3 System Interfaces volume (excuse the bad formatting):

41429 The structure sigaction, used to describe an action to be taken,
      is defined in the <signal.h>
41430 header to include at least the following members:
41431
41432 Member Type       Member Name     Description
41433 void(*) (int)     sa_handler      SIG_DFL, SIG_IGN, or pointer to a
                                        function.
43434 sigset_t          sa_mask         Additional set of signals to be
                                        blocked during execution of
                                        signal-catching function.
41437 int               sa_flags        Special flags to affect behavior of
                                        signal.
41438 void(*) (int,
41439 siginfo_t *, void *) sa_sigaction Signal-catching function.

41440 The storage occupied by sa_handler and sa_sigaction may overlap,
      and a conforming application
41441 shall not use both simultaneously.


Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to