SIG_BLOCK undeclared

[-EquinoX-]

I got the following error when compiling my code:

sender.c:156: warning: implicit declaration of function âsigemptysetâ
sender.c:157: warning: implicit declaration of function âsigaddsetâ
sender.c:160: warning: implicit declaration of function âsigactionâ
sender.c:170: warning: implicit declaration of function âsigprocmaskâ
sender.c:170: error: âSIG_BLOCKâ undeclared (first use in this function)
sender.c:170: error: (Each undeclared identifier is reported only once
sender.c:170: error: for each function it appears in.)
sender.c:193: error: âSIG_UNBLOCKâ undeclared (first use in this function)

any idea why? I've already included signal.h in the header file

[cas]

Are you building with -ansi or one of the -std flags? If so, that's the problem. Those functions and macros you're using are not part of standard C, and so when you tell your compiler to conform to the C standard, it won't declare them.

You have a few solutions. If you're trying to write portable standard C, then don't use those functions and macros.

If you're trying to write code for POSIX systems, then you can tell the implementation that by setting the _XOPEN_SOURCE macro to a suitable value (600, for SuSv3, is what I use). This is best accomplished on the command-line, as in:

gcc -std=c99 -pedantic -Wall -D_XOPEN_SOURCE=600

This is the proper way to enable POSIX support (proper being that defined by the POSIX standard itself).

[-EquinoX-]

Yes I am compiling it with -ansi, however I am not writing the code for a POSIX system.. I don't even know what that means.. so any other solutions to this?

[NINAD]

Yes I am compiling it with -ansi, however I am not writing the code for a POSIX system.. I don't even know what that means.. so any other solutions to this?

Can I ASK YOU A question

which is not related to your quote
please