Date: Thu, 22 Nov 2001 01:41:09 -0600 From: Alfred Perlstein <bright@mu.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Julian Elischer <julian@elischer.org>, arch@FreeBSD.ORG, Steve Kargl <sgk@troutmask.apl.washington.edu> Subject: Re: Kernel Thread scheduler Message-ID: <20011122014109.W13393@elvis.mu.org> In-Reply-To: <XFMail.011121233016.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Wed, Nov 21, 2001 at 11:30:16PM -0800 References: <20011122012838.V13393@elvis.mu.org> <XFMail.011121233016.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* John Baldwin <jhb@FreeBSD.org> [011122 01:30] wrote:
>
> On 22-Nov-01 Alfred Perlstein wrote:
> > * John Baldwin <jhb@FreeBSD.org> [011122 01:22] wrote:
> >>
> >> Perhaps if 'proc' is put under _KERNEL. Since proc embeds a kse, ksegroup,
> >> and thread, it can't very easily be defined w/o including those definitions.
> >
> >#if defined(_KERNEL) || defined(_REALLY_WANT_PROC)
>
> Yes, we already have _REALLY_WANT_PROC. It's called:
>
> #include <sys/proc.h>
>
> Unfortunately <sys/user.h> includes lots and lots of other garbage.
Why the hell is wine sucking it in, especially on FreeBSD?
I'm 99% sure i was able to blast through this breakage by
simply removing the #include from a wine file then everything
just worked.
What the hell is the point of a 'configure' script otherwise?
GRR.
Why do we even care? When was the last time wine was good for
anything besideds barely being able to run solitare on FreeBSD
anyhow?
--
-Alfred Perlstein [alfred@freebsd.org]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
http://www.morons.org/rants/gpl-harmful.php3
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011122014109.W13393>