Date: Thu, 22 Nov 2001 01:21:39 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: Alfred Perlstein <bright@mu.org> Cc: John Baldwin <jhb@FreeBSD.org>, arch@FreeBSD.ORG, Steve Kargl <sgk@troutmask.apl.washington.edu> Subject: Re: Kernel Thread scheduler Message-ID: <Pine.BSF.4.21.0111220121140.41963-100000@InterJet.elischer.org> In-Reply-To: <20011122014109.W13393@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
apparently they DIDN'T need user.h they just thought they did.... On Thu, 22 Nov 2001, Alfred Perlstein wrote: > * 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?Pine.BSF.4.21.0111220121140.41963-100000>