signal.h conflicting with linux/signal.h (2.4.0)

[Guennadi Liakhovetski <g.liakhovetski@ragingbull.com>]

Hi

Yesterday I was writing a user-space programme, for which I thought I
needed (well, eventually I managed without it, but still...) linux/signal.h. 
Then I found out that everything there is hidden from user-space
programmes by the 
#ifdef __KERNEL__
instruction. Ok, although I actually needed one of those structs (namely
struct sigpending), I found a way around it. But, while I tried compiling
my programme, g++ complained about a conflicting declaration of sigset_t
in asm/signal.h, #included from linux/signal.h (so, there are some
declarations exposed to the user space there) and /usr/include/signal.h.
The latter one was included from some another and another and another
C++ header... So, is it so, that user-space programmes should not #include
linux/signal.h nor asm/signal.h (then why isn't sigset_t from asm/signal.h
hidden by #ifdef __KERNEL__ too?) or what?

Thanks
Guennadi
___

Dr. Guennadi V. Liakhovetski
Department of Applied Mathematics
University of Sheffield, U.K.
email: G.Liakhovetski@sheffield.ac.uk


-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.kernelnewbies.org/