Solaris compile time fixes for CVS wine

Robert Lunnon bobl at optushome.com.au
Tue Jan 13 16:19:49 CST 2004


On Thursday 08 January 2004 17:51, Dimitrie O. Paun wrote:
> On January 8, 2004 01:22 am, Robert Lunnon wrote:
> > Here are a buch of Solais compatibility patches for wine (Some but not
> > all of them). Within the enclosed tarball the diffs are structured
> > according to the wine cvs tree. There is a readme file accompanying each
> > diff to explain what the change is.
>
> Please break the archive into one patch per message, not compressed
> (preferably inlined). Here are a few pointers on how to send patches:
>     http://www.winehq.org/site/sending_patches
>
> BTW, what's the status of building Wine under Solaris? What architecture
> (i386, etc) are you using?


There are quite a few patches in that kit, they are organised as separate 
patches for each file and a description to make application easy. After 
extracting you could construct a single liner that would apply the entire 
kit.

It would be relatively easy to send a dozen or so emails though, providing you 
don't want me to collect up the dependencies into a single e-mail

As for status:

Wine works quite well under Solaris x86  (Possibly better than linux based on 
my experience with 18062003) but can't be built and run successfully without 
two key patches that Alexandre has elected not to accept, and one patch which 
is probably acceptable but I haven't sent yet (not sure if the semantics of 
the code are correct for the OS yet). I also distribute it with some 
experimental threading code which seems to work better than the CVS code. 
Again the project has elected not to accept this code at this time due to 
it's present implementation (Because it's experimental I have arranged things 
to be able to select the threading model at runtime through an environment 
variable) 

Hence my port is not a stock wine. I must maintain at least the critical 
patches locally to be able to offer wine under solaris. As per the (L)GPL the 
patches are all offered to the project and the diffs are distributed as a 
patch kit with the binary with a pointer to winehq for the rest of the 
source.

Right at this point I am trying to add cdrom support which is kinda tricky 
because the CDROM ioctl raw reading support is broken under Solaris x86 and 
you need to go right down to the SCSI level for raw read operations. 
Unfortunately this is restricted to root. But I'm doing it anyway for when it 
changes (less maintenance later).

Does this answer your questions, oh and should I resubmit the patches or will 
the kit do.

Bob



More information about the wine-devel mailing list