Date: Thu, 22 Nov 2001 08:46:20 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Alfred Perlstein <bright@mu.org> Cc: John Baldwin <jhb@FreeBSD.org>, Julian Elischer <julian@elischer.org>, arch@FreeBSD.org Subject: Re: Kernel Thread scheduler Message-ID: <20011122084620.A94105@troutmask.apl.washington.edu> In-Reply-To: <20011122014109.W13393@elvis.mu.org>; from bright@mu.org on Thu, Nov 22, 2001 at 01:41:09AM -0600 References: <20011122012838.V13393@elvis.mu.org> <XFMail.011121233016.jhb@FreeBSD.org> <20011122014109.W13393@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 22, 2001 at 01:41:09AM -0600, Alfred Perlstein wrote: > * John Baldwin <jhb@FreeBSD.org> [011122 01:30] wrote: > > > > On 22-Nov-01 Alfred Perlstein wrote: > > Why the hell is wine sucking it in, especially on FreeBSD? This has been fixed. Apparently, wine needs some linux specific stuff from <sys/user.h>. > 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? The offending code was #ifdef HAVE_SYS_USER_H #include <sys/user.h> #endif configure found <sys/user.h>. > 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? Apparently, you don't work in an environment where people send you MSWord documents or Excel spreadsheets everyday. If, and when, wine reachs maturity, I'll never have to reboot to edit a Word document. -- Steve 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?20011122084620.A94105>