September 2002 - Wine-Devel

Open-GL Mesa patches (http://cvs.winehq.com/patch.py?id=5527)

by Uwe Bonnes

Hallo, the Open-GL Mesa patches (http://cvs.winehq.com/patch.py?id=5527) in wine/dlls/ddraw/mesa_private.h unconditional inclused GL/gl.h and GL/glx.h. On my Suse V8.0 system ( with the mesa package installed and the mesa-devel package not installed) this leads to: make[2]: Wechsel in das Verzeichnis Verzeichnis »/home/bon/tmp/wine/compile/wine-realclean/wine/dlls/ddraw« gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ -D_REENTR ANT -I/usr/X11R6/include -o dsurface/main.o dsurface/main.c In file included from dsurface/main.c:27: mesa_private.h:32: GL/gl.h: Datei oder Verzeichnis nicht gefunden mesa_private.h:33: GL/glx.h: Datei oder Verzeichnis nicht gefunden make[2]: *** [dsurface/main.o] Fehler 1 Probably it's a bad idea to only install mesa and not mesa-devel, but I think wine should cope with this situation or at least warn the user about that. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Sept. 28, 2002

Re: A problem reading configuration file

by Sylvain Petreolle

Me too. I made some programs with assembly under MS-DOS in the 90s before switching to Linux ;) > I think its normal. Findfirst finds the first entry, and findnext > returns only > the next :) > I'm sure it works that way. I have tried to check that in some > documentation, > but if I remember right then I have used those in something like > Borland > Delphi at the university. But I dont have Delphi at home... > > If that is ok, then do you have some idea, what could be the problem? > There was a patch applied few days ago on findnext... perhaps it's it. http://www.winehq.com/hypermail/wine-patches/2002/09/0243.html ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

Sept. 28, 2002

Re: A problem reading configuration file

by Sylvain Petreolle

Remarque : message transféré en pièce jointe. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

Sept. 28, 2002

Re: Fix for msvcrt sscanf/swscanf

by Uwe Bonnes

>>>>> "Jukka" == Jukka Heinonen <jhei(a)iki.fi> writes: Jukka> Wine msvcrt sscanf and swscanf implementations incorrectly expect Jukka> strings to end with EOF. This crashes some applications which did Jukka> work with older versions of Wine that just forwarded msvcrt Jukka> sscanf to libc sscanf. Jukka> Changelog: Functions sscanf and swscanf now expect strings to be Jukka> terminated with null (0) instead of EOF (-1). I asked some weeks ago about the test framework for msvcrt, but nobody jumped on the waggon. The mix of msvcrt and libc was something I couldn't do myself. Perhaps somebody can come up with someting. It sure is important to codify findings like Jukkas. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Sept. 28, 2002

Re: dlls/ completion nit

by Dmitry Timoshkov

"Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > Much better, thanks! I was subconsciously aware of the feature, but since > I've never used it, it never got considered. A small note: it is not > obvious that (1) it is possible to do that, and (2) how to do it! I do the following: 1. copy WineHQ CVS tree to ~/wine_hq_src 2. mkdir ~/wine; cd ~/wine 3. ../wine_hq_src/configure; make depend; make to create diffs: diff -urN ~/cvs/WineHQ/wine ~/wine_hq_src -- Dmitry.

Sept. 28, 2002

Re: [Controversial] Developper only CVS sandbox

by Dimitrie O. Paun

On September 27, 2002 11:48 pm, Dan Kegel wrote: > I'm also somewhat opposed to CVS. The big problem with CVS is > that it makes it *too* easy to contribute changes, and too > hard to disentangle changes later when trying to contribute > them back to the main tree. (This kind of thing has caused > huge nightmares in the past.) CVS is not the best, granted, but have you seen the ChangeSet scripts we're using? -- Dimi.

Sept. 28, 2002

CVS server broken ?

by Sylvain Petreolle

Hi, trying to do a cvs update I get nothing on screen today, even when trying to do a simple cvs status (normally it would take seconds). cvs.winehq.com responds to ping though, could an admin look at it ? Thanks for your action. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

Sept. 28, 2002

Re: dlls/ completion nit

by Dimitrie O. Paun

On September 27, 2002 04:17 pm, Alexandre Julliard wrote: > The standard way to cope with that is to build outside of the source > tree. Then you get all the object files out of the way, not only the > dlls. Much better, thanks! I was subconsciously aware of the feature, but since I've never used it, it never got considered. A small note: it is not obvious that (1) it is possible to do that, and (2) how to do it! I'll dig through the mail archives for the info... -- Dimi.

Sept. 28, 2002

Re: RFC: Winsock todo's

by Dan Kegel

Martin Wilck wrote: > Although I had a relevant part in implementing the asynchronous IO in > winsock, I am not quite content with it because it is not really > asynchronous. And not really high-performance, I bet (though I wouldn't know, I haven't looked at the code or tested it). > Alexandre is against using threads. Me, too. glibc uses threads to emulate aio, and the performance is poor. On platforms that natively support AIO, I bet you *really* want to implement Wine AIO using Posix AIO if you can. > On Linux at least, Ben > LaHaise's asyncio can be expected to become part of the > 2.6 kernel series, and if that happens the wine asynchronous IO > functionality should be rewritten to use the asyncio API on systems that > support it. Yes. Exactly. > (I still havent't figured out whether aio will support > sockets, though). It will. SGI's kaio does already, and Ben's will support it when he's finished. That should give good performance. - Dan p.s. Looks like the threads implementation for the 2.6 kernel will rock, too. See http://www.kegel.com/c10k.html#threaded (Somebody remind me why Wine has its own threads implementation again? Is it because the semantics are too different from Posix threads?)

Sept. 28, 2002

Status of *ongoing* wine improvements?

by Dan Kegel

The To-Do list Steven Edwards is putting together looks like a nice menu of Things That Need To Be Done But Have Not Been Started Yet. A similar list, of ongoing work, might be useful in a different way. Check out http://www.kernelnewbies.org/status/ It has a number of nice features: * status of each proposed enhancement (planned / started / alpha / beta / ready / merged) * each line is a link to a wine-devel post or web page describing the proposed work * each line has the names of people actually working on them * items changed since last week are bold * only items expected to be finished before the feature freeze for the next release are included This list might be pretty short for Wine, but it'd be a nice way of tracking progress. - Dan

Sept. 28, 2002