[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bgl-discuss] SA_SIGINFO undeclared

Yes, the real issue here is what sort of asynchronous behavior you are looking for on the compute nodes. In general, the compute nodes do not support much in the way of async actions. So, the real question is what kind of async behavior do you need to support? Do you *really* need it? Would a simple timer interrupt provide the behavior you are looking for?

-Pete

On Sep 30, 2005, at 10:32 AM, Kazutomo Yoshii wrote:

Hi,

I think that POSIX signal(like sigaction) is not available for the
compute node.

You can use signal() instead of sigaction() if signal() fulfills your
requirement.

Thanks,
Kaz


When I try to compile some signal handling code on BGL (using
blrts_xlC) which uses "SA_SIGINFO" -> i.e one of the defined flags to
the sigaction() call, I get the following error:

"1540-0274 (S) The name lookup for "SA_SIGINFO" did not find a
declaration."

The code is inside a .cpp file and blrts_xlC is used.

I thought it was to do with some C++ issues, so I isolated the signal
code into a .c file and used blrts_xlc.

But then I still get this error:

"1506-045 (S) Undeclared identifier SA_SIGINFO."

Any ideas on how to make SA_SIGINFO visible?

thanks,
Aroon


- --------------------------------------------------------------------
To add or remove yourself from this mailing list, use the 'notifyme'
command on any BGL machine. To remove: notifyme -n, to add: notifyme -y.




--
Kazutomo Yoshii   http://www-unix.mcs.anl.gov/~kazutomo/

- --------------------------------------------------------------------
To add or remove yourself from this mailing list, use the 'notifyme'
command on any BGL machine. To remove: notifyme -n, to add: notifyme -y.



- --------------------------------------------------------------------
To add or remove yourself from this mailing list, use the 'notifyme'
command on any BGL machine. To remove: notifyme -n, to add: notifyme -y.