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

["Joseph A. Knapka" <jknapka@earthlink.net>]

Guennadi Liakhovetski wrote:
> 
> On Fri, 6 Apr 2001, Joseph A. Knapka wrote:
> 
> > There are probably exceptions to the rule above, for code that
> > does very Linux-centric, non-portable tasks that are not supported
> > by glibc.
> 
> Yes, I believe, this was the case - I used a 'non-standard' patch to the
> kernel, so I needed to include those headers. What do I do in this case?

Well, I have never done it, but you could try #define __KERNEL__
and see what breaks. You are really going to be on your
own in this case, since only you know what kernel definitions
your custom user-space code requires.

Another approach would be to re-define the kernel items
that you need in your own headers, thereby avoiding dependency
problems between kernel headers. And that way you get only
exactly what you need; but on the other hand you have to
maintain the definitions in your own code when the kernel
definitions change.

Probably someone else on kernelnewbies can help you more.

Good luck,

-- Joe

> Thanks
> Guennadi

-- Joe Knapka
"It was just a maddened crocodile hidden in a flower bed. It could
 have happened to anyone." -- Pratchett
// Linux MM Documentation in progress:
// http://home.earthlink.net/~jknapka/linux-mm/vmoutline.html
* Evolution is an "unproven theory" in the same sense that gravity is. *
-
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/