Re: function name collision on getcontext with ports/editors/joe

2002-02-17 Thread Daniel Eischen
On Sun, 10 Feb 2002, Kevin Day wrote: I'm the maintainer for ports/editors/joe, and just tried compiling it under -CURRENT. signal.h includes sys/signal.h which includes ucontext.h cc -O -pipe -c umath.c In file included from b.h:6, from bw.h:23,

Re: function name collision on getcontext with ports/editors/joe

2002-02-14 Thread Daniel Eischen
On Mon, 11 Feb 2002, Bruce Evans wrote: On Sun, 10 Feb 2002, Daniel Eischen wrote: What do you recommend we do? Should we not include sys/ucontext.h from sys/signal.h, or do what Solaris does, or just leave everything as is? Don't include sys/ucontext.h from sys/signal.h, and fix

Re: function name collision on getcontext with ports/editors/joe

2002-02-14 Thread Bruce Evans
On Fri, 15 Feb 2002, Daniel Eischen wrote: Finally getting buildworld to work again... More problems in the kernel though. ucontext_t is used as a parameter to sigreturn (and getsetcontext soon), so it is referenced in sys/sysproto.h. Lots of stuff includes sys/sysproto.h. Do we, a)

Re: function name collision on getcontext with ports/editors/joe

2002-02-12 Thread Bruce Evans
On Mon, 11 Feb 2002, Daniel Eischen wrote: On Mon, 11 Feb 2002, Garrett Wollman wrote: On Mon, 11 Feb 2002 12:16:44 -0500 (EST), Daniel Eischen [EMAIL PROTECTED] said: How do you easily forward declare something that is a typedef? There is a reason style(9) says not to use such

Re: function name collision on getcontext with ports/editors/joe

2002-02-12 Thread Bruce Evans
On Mon, 11 Feb 2002, Daniel Eischen wrote: On Mon, 11 Feb 2002, Terry Lambert wrote: Daniel Eischen wrote: Removing sys/ucontext.h from sys/signal.h prevents ucontext_t from being defined, so all users of signal.h would choke. We can change the prototype of sigreturn back to

Re: function name collision on getcontext with ports/editors/joe

2002-02-11 Thread Garrett Wollman
On Mon, 11 Feb 2002 12:16:44 -0500 (EST), Daniel Eischen [EMAIL PROTECTED] said: How do you easily forward declare something that is a typedef? There is a reason style(9) says not to use such typedefs. Unfortunately, this one it written into a standard. Since We Are The Implementation, there

Re: function name collision on getcontext with ports/editors/joe

2002-02-11 Thread Daniel Eischen
On Mon, 11 Feb 2002, Garrett Wollman wrote: On Mon, 11 Feb 2002 12:16:44 -0500 (EST), Daniel Eischen [EMAIL PROTECTED] said: How do you easily forward declare something that is a typedef? There is a reason style(9) says not to use such typedefs. Unfortunately, this one it written into a

Re: function name collision on getcontext with ports/editors/joe

2002-02-11 Thread Daniel Eischen
On Sun, 10 Feb 2002, Kevin Day wrote: I'm the maintainer for ports/editors/joe, and just tried compiling it under -CURRENT. signal.h includes sys/signal.h which includes ucontext.h cc -O -pipe -c umath.c In file included from b.h:6, from bw.h:23,

Re: function name collision on getcontext with ports/editors/joe

2002-02-10 Thread Daniel Eischen
On Sun, 10 Feb 2002, Kevin Day wrote: I'm the maintainer for ports/editors/joe, and just tried compiling it under -CURRENT. signal.h includes sys/signal.h which includes ucontext.h cc -O -pipe -c umath.c In file included from b.h:6, from bw.h:23,

Re: function name collision on getcontext with ports/editors/joe

2002-02-10 Thread Daniel Eischen
On Mon, 11 Feb 2002, Bruce Evans wrote: On Sun, 10 Feb 2002, Daniel Eischen wrote: Hmm, sys/signal.h includes sys/ucontext.h. I'm not sure why though. bde might know. sys/signal.h includes machine/signal.h for the normal namespace pollution that was needed to use sigreturn(2) (except