On Sun, 10 Feb 2002, Kevin Day wrote:
>
> I'm the maintainer for ports/editors/joe, and just tried compiling it under
> -CURRENT.
>
> includes which includes ucontext.h
>
> > cc -O -pipe -c umath.c
> > In file included from b.h:6,
> > from bw.h:23,
> > from
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 . Lots of stuff includes
> . Do we,
>
> a) Include conditional
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
> > from , or do what Solaris does, or just leave
> > everything as is?
>
> Don't include from , and fix whatever
> breaks. I think applications that use
On Mon, 11 Feb 2002, Daniel Eischen wrote:
> On Mon, 11 Feb 2002, Terry Lambert wrote:
> > Daniel Eischen wrote:
> > > Removing from prevents ucontext_t
> > > from being defined, so all users of would choke.
> > >
> > > We can change the prototype of sigreturn back to struct sigcontext *,
> >
On Mon, 11 Feb 2002, Daniel Eischen wrote:
> On Mon, 11 Feb 2002, Garrett Wollman wrote:
> > <<[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
On Sun, 10 Feb 2002, Kevin Day wrote:
>
> I'm the maintainer for ports/editors/joe, and just tried compiling it under
> -CURRENT.
>
> includes which includes ucontext.h
>
> > cc -O -pipe -c umath.c
> > In file included from b.h:6,
> > from bw.h:23,
> > from
I'm the maintainer for ports/editors/joe, and just tried compiling it under
-CURRENT.
includes which includes ucontext.h
> cc -O -pipe -c umath.c
> In file included from b.h:6,
> from bw.h:23,
> from umath.c:5:
> rc.h:41: conflicting types for `getcontext'
>
On Mon, 11 Feb 2002, Garrett Wollman wrote:
> <<[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, th
<
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 is no difficulty in simply writing the
appropriate structure type into t
On Sun, 10 Feb 2002, Daniel Eischen wrote:
> On Mon, 11 Feb 2002, Bruce Evans wrote:
> > includes for the normal namespace
> > pollution that was needed to use sigreturn(2) (except sigreturn(2)
> > itself isn't actually declared anywhere). Including
> > gives the corresponding namespace pollu
On Mon, 11 Feb 2002, Bruce Evans wrote:
> On Sun, 10 Feb 2002, Daniel Eischen wrote:
>
> > Hmm, includes . I'm not sure why though.
> > bde might know.
>
> includes for the normal namespace
> pollution that was needed to use sigreturn(2) (except sigreturn(2)
> itself isn't actually declared
On Sun, 10 Feb 2002, Daniel Eischen wrote:
> Hmm, includes . I'm not sure why though.
> bde might know.
includes for the normal namespace
pollution that was needed to use sigreturn(2) (except sigreturn(2)
itself isn't actually declared anywhere). Including
gives the corresponding namespace
On Sun, 10 Feb 2002, Kevin Day wrote:
>
> I'm the maintainer for ports/editors/joe, and just tried compiling it under
> -CURRENT.
>
> includes which includes ucontext.h
>
> > cc -O -pipe -c umath.c
> > In file included from b.h:6,
> > from bw.h:23,
> > from
I'm the maintainer for ports/editors/joe, and just tried compiling it under
-CURRENT.
includes which includes ucontext.h
> cc -O -pipe -c umath.c
> In file included from b.h:6,
> from bw.h:23,
> from umath.c:5:
> rc.h:41: conflicting types for `getcontext'
>
14 matches
Mail list logo
