Date: Tue, 30 Dec 2003 15:16:29 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: Ulrich Spoerlein <q@uni.de> Cc: Travis Poppe <tlp@LiquidX.org> Subject: Re: The latest WINE and /dev/mixer* Message-ID: <Pine.BSF.4.58.0312301445130.9068@naos.dbai.tuwien.ac.at> In-Reply-To: <20031230132813.GB847@galgenberg.net> References: <20031227144106.35943fff.tlp@LiquidX.org> <Pine.BSF.4.58.0312280037370.13134@acrux.dbai.tuwien.ac.at> <Pine.BSF.4.58.0312281341130.23314@acrux.dbai.tuwien.ac.at> <Pine.BSF.4.58.0312281416300.23314@acrux.dbai.tuwien.ac.at> <20031230132813.GB847@galgenberg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 30 Dec 2003, Ulrich Spoerlein wrote:
>> I don't know why, but within a few days we have now been able to fix to
>> very relevant FreeBSD-specific issue for Wine! :-)
> Wine is IMHO far from being "fixed" on FreeBSD. Have you tried running
> 'gmake test' after building Wine? Not much joy there (at least on my
> systems...)
Sure, you're right. But with last week's FreeBSD-specific changes, we now
have two ("to" above should have read "two") relevant issues fixed: one
related to forking on -CURRENT, the other to sound, and at least two users
now have applications working properly that didn't use to work.
Think positive! :-)
(Seriously, it has been my experience that while I try to keep Wine
buildable on FreeBSD and make portability fixes, it often was specific
users with specific applications/needs, like Travis now, that managed to
locate and debug some nasty issue. Now, if we had more guys like Travis!)
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.58.0312301445130.9068>