Problems compiling Wine CVS in FreeBSD 4.8

2003-08-28 Thread Daniel O'Connor
I am trying to compile Wine CVS to get Protel99SE working, but I am having some difficulty.. For example in dlls/glu32 - [chowder 16:50] ~/projects/wine-20030813/dlls/glu32 gmake gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include -D_REENTRANT -fPIC -D__WINESRC__ -Wall

Wine CVS Build Error

2003-08-14 Thread Casey McGinty
I'm trying to get Wine and/or Winex to build on my system with no luck. I get the same error in both releases, I was hoping someone would know how to fix this, or what I am doing wrong. I'm using GCC 3.2.3 and kerenl 2.4.21 on a Linux From Scratch distribution. The error output I get in Wine:

Re: Wine CVS Build Error

2003-08-11 Thread BiGgUn
Hi I'm using GCC 3.2.3 and kerenl 2.4.21 on a Linux From Scratch distribution. Did you try to compile your sources with a lower version of GCC ? I personnaly use GCC 3.0.4 for compiling. GCC 2.95 can be used as well. HTH, Stephan

Cabinet problems in latest wine cvs

2003-07-31 Thread Boris
When attempting to install Office 2000 under the latest wine from cvs, It stops half way through the installation with the following error. err:cabinet:FDICopy FDIIsCabinet failed. Any ideas?

Re: Cabinet problems in latest wine cvs

2003-07-31 Thread Gregory M. Turner
On Thursday 31 July 2003 02:57 pm, Boris wrote: When attempting to install Office 2000 under the latest wine from cvs, It stops half way through the installation with the following error. err:cabinet:FDICopy FDIIsCabinet failed. Any ideas? This rollup of the recent cabinet patches should fix

Latest wine cvs error

2002-12-06 Thread Boris
I tried compiling the latest cvs and heres the error I get. make[2]: Leaving directory `/root/wine/tools/wrc' make[1]: Leaving directory `/root/wine/tools' make[1]: Entering directory `/root/wine/dlls' make[2]: Entering directory `/root/wine/dlls/ntdll' make[3]: Entering directory

Again Warcraft 3 - Wine CVS 20021125

2002-11-27 Thread Leonardo Giordani
Ok, I set up the debugger, but it doesn't work anyway... This is the output: -bash-2.05b$ wine --debugmsg +seh,+opengl War3.exe Could not stat /home/leo/.wine/cdrom (No such file or directory), ignoring drive M: Loading required GL library /usr/X11R6/lib/libGL.so.1.2

Re: Again Warcraft 3 - Wine CVS 20021125

2002-11-27 Thread Sylvain Petreolle
'regedit winedefault.reg' regularily (if you follow wine-cvs mailing archives, you know exactly when doing that;)) ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

Re: Again Warcraft 3 - Wine CVS 20021125

2002-11-27 Thread Sylvain Petreolle
I say to you it isn't the case. :) Do not hate me, please. After download of CVS snapshot I compiled it from a dir in my home (/home/leo/wine). There is winedefault.reg, but I do not understand if wine reads it or the user.reg and system.reg in my .wine/ dir The emulation of registry is

Warcraft 3 - Wine CVS 20021125

2002-11-26 Thread Leonardo Giordani
Hi, I'm trying to run Warcraft 3 with wine CVS build 20021125. I followed the Jesse Allen HOWTO but I get these messages -bash-2.05b$ winelauncher War3.exe Loading required GL library /usr/X11R6/lib/libGL.so.1.2 err:ntdll:RtlpWaitForCriticalSection section 0x400f7190 ../../loader

Re: Warcraft 3 - Wine CVS 20021125

2002-11-26 Thread Sylvain Petreolle
I do not understand what is wrong... Here is my config file (only relevant sections). Someone is experiencing the same problem? Thanks This problem is not related to .wine/config file. Please read the documentation as suggested by wine, there is the key of your problem. wine: Unhandled

wine + cvs + proxy = ?

2002-08-12 Thread Fabian Cenedese
Hi all I'd like to stay up-to-date by using cvs on wine. Unfortunately cvs isn't able to go through a proxy if it isn't invisible, I can't enter the proxy info anywhere in cvs (confirmed on cvs mailing list). So I wondered if there is a better solution than to download the wine-snapshots and

Re: wine + cvs + proxy = ?

2002-08-12 Thread lawson_whitney
read the wine-cvs mailing list and fetch the individual patch files through a proxy using wget -i. I use this to extract the url's from the wine-cvs mail folder: #!/bin/sh grep Patch: /gp/pine/wine-cvs|sed 's/Patch:\ //g' ~/wgets mv /gp/pine/wine-cvs ~/cvslog/$(date -u -Iseconds) You might have

mIRC fails to start (Wine CVS 20020407)

2002-04-07 Thread mdew
heres a debug report [01:40pm 08-Apr-02]$ /usr/bin/wine --winver=nt2k -debugmsg +relay ./mirc32.exe 0806fcf8:Call kernel32.__wine_register_dll_16(40615c7c) ret=406131b4 0806fcf8:Ret kernel32.__wine_register_dll_16() retval=40615c7c ret=406131b4 0806fcf8:Call

Re: mIRC fails to start (Wine CVS 20020407)

2002-04-07 Thread mdew
my error...ignore it :) heres a debug report [01:40pm 08-Apr-02]$ /usr/bin/wine --winver=nt2k -debugmsg +relay ./mirc32.exe 0806fcf8:Call kernel32.__wine_register_dll_16(40615c7c) ret=406131b4 0806fcf8:Ret kernel32.__wine_register_dll_16() retval=40615c7c ret=406131b4

Re: wine-cvs

2000-12-02 Thread Eric Pouech
"Dimitrie O. Paun" wrote: The pipermail wine-cvs archive is out of date (no records for december). Can someone please fix it? BTW, Mailman 2.0 has been released, we should upgrade to the latest version. hypermail should be the "standard" mail interface (www.winehq.co

Re: wine-cvs

2000-12-02 Thread Dimitrie O. Paun
On Sat, 2 Dec 2000, Eric Pouech wrote: hypermail should be the "standard" mail interface (www.winehq.com/hypermail/wine-cvs/ in your case) (it *does* work for december commits) Thanks, it changed and I was not aware to upgrade my bookmark. -- Dimi.

wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread Patrik Stridvall
My last update was Tuesday 2000-09-19. However the CVS iteself has made progress since then. Any ideas?

Re: wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread David Howells
I've noticed that the wine-devel has gone very slow. In fact, wine2.winehq.com has ben refusing connections and the backup mailserver at Corel has been bouncing messages for no obvious reason. I don't know whether this helps David Howells

Re: wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread Ove Kaaven
Hey, shouldn't we organize the Wine-Developers Movement Against Majordomo? Let me see if I can remember some of the people I know don't like majordomo: - myself - Dimitrie O. Paun - Jutta Wrage - Peter Hunnisett - David Elliott - Andreas Mohr (anyone I forgot?) Compare with the people I know

Re: wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread Andreas Mohr
On Tue, Sep 26, 2000 at 01:09:38PM +0200, Ove Kaaven wrote: Hey, shouldn't we organize the Wine-Developers Movement Against Majordomo? *ACK* Let me see if I can remember some of the people I know don't like majordomo: - myself - Dimitrie O. Paun - Jutta Wrage - Peter Hunnisett - David

Re: wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread Uwe Bonnes
Andreas Mohr writes: On Tue, Sep 26, 2000 at 01:09:38PM +0200, Ove Kaaven wrote: ... (anyone I forgot?) Not that I know of. If the missing wine-cvs mails for the recent CVS commits are caused by majordomo, count me as another member of the Wine-Developers Movement Against Majordomo

Re: wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread Jason L Tibbitts III
"OK" == Ove Kaaven [EMAIL PROTECTED] writes: OK Hey, shouldn't we organize the Wine-Developers Movement Against OK Majordomo? Hoe exactly is Majordomo implicated in this? If delivery is slow, it is the MTA's fault because Majordomo does not do delivery. If messages are being refused, it is

Re: wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread Andreas Mohr
On Tue, Sep 26, 2000 at 06:52:08PM +0200, Patrik Stridvall wrote: Andreas Mohr writes: On Tue, Sep 26, 2000 at 01:09:38PM +0200, Ove Kaaven wrote: ... (anyone I forgot?) Not that I know of. If the missing wine-cvs mails for the recent CVS commits are caused

Re: wine-cvs mailing-list doesn't seem to work

2000-09-26 Thread Douglas Ridgway
On Tue, 26 Sep 2000, Andreas Mohr wrote: OK, let's stop bitchin' and flamin' now and let's get back to work ;-) So what to do ? For one, I'd prefer to keep the this discussion on the web-admin list, so that Wine development doesn't get crowded out by administrivia. (I just added you

Re: Wine CVS Documentation

2000-06-23 Thread John R . Sheets
On Thursday, June 22, 2000, Gerald Pfeifer [EMAIL PROTECTED] wrote: I do like DocBook as a source format. However, regular users should not have to deal with DocBook in any way. I think we can cover the users if we include the generated HTML (and possibly generated flat text) in with the

Re: Wine CVS Documentation

2000-06-22 Thread John R . Sheets
[ I somehow forgot to mail this... ] On Wednesday, June 21, 2000, Eric Pouech [EMAIL PROTECTED] wrote: WINE USER'S GUIDE For the day-to-day user; maintaining Wine on your system. How to configure the basic services, like fonts, printing, multimedia. perhaps what's missing is the

Re: Wine CVS Documentation

2000-06-22 Thread John R . Sheets
On Thursday, June 22, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote: Well, that is a problem for everything except pure text. I'm more intrested in specific DocBook problems. I'll try to come up with some more DocBook-specific limitations. Then we have all the in code documention of the

RE: Wine CVS Documentation

2000-06-22 Thread Patrik Stridvall
On Thursday, June 22, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote: Then we have all the in code documention of the Windows API that should be extracted and presented in an apropriate format (DocBook?). We would probably have to do this by hand (I assume you're referring to all

Re: Wine CVS Documentation

2000-06-21 Thread John R . Sheets
On Wednesday, June 21, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote: 3. Configuring Wine - Customizing .winerc - Builtin vs. native DLLs - x11drv - Look feel - Keyboard Even though the ttydrv doesn't currently work very well we probably should have a section

Re: Wine CVS Documentation

2000-06-21 Thread Alexandre Julliard
Eric Pouech [EMAIL PROTECTED] writes: a last point would be to have Alexandre's agreement to use DocBook as primary format for documentation. I remembered one of his remarks where he wished to have at least all docs in text format so anyone could read them (it doesn't mean of course docs

Re: Wine CVS Documentation

2000-06-21 Thread Marcus Meissner
On Wed, Jun 21, 2000 at 12:14:30PM -0700, Alexandre Julliard wrote: Eric Pouech [EMAIL PROTECTED] writes: a last point would be to have Alexandre's agreement to use DocBook as primary format for documentation. I remembered one of his remarks where he wished to have at least all docs in

Re: Wine CVS Documentation

2000-06-21 Thread John R . Sheets
a documentation patch he will need to do ./tools/make_documentation or something, but then similar thing are required even now for debug messages to take one example. It could also be a makefile target. For example: docs: db2html wine-cvs-docs.sgml The db2html script is part of the Cygnus

RE: Wine CVS Documentation

2000-06-21 Thread Patrik Stridvall
"make all". However all the ./tools/make_* files are hacks that should be removed somehow IMHO, eventhough I have no good suggestions as to how. docs: db2html wine-cvs-docs.sgml The db2html script is part of the Cygnus stylesheets, IIRC, and exists on Redhat and Debian and

Re: Wine CVS Documentation

2000-06-21 Thread John R . Sheets
On Wednesday, June 21, 2000, Patrik Stridvall [EMAIL PROTECTED] wrote: I have only look very briefly on DocBook but it doesn't look much more complicated than HTML and learning HTML was very easy. Yes, it's kind of verbose, especially with lists and tables, but for the most part, the tag

RE: Wine CVS Documentation

2000-06-21 Thread Patrik Stridvall
Patrik Stridvall psÉleissner.se writes: Well, we must of course include the generate text of the SGML source in the CVS tree. Requiring everybody that want to read documentation to install the SGML tools is not an option IMO. I'm not sure it has to be in CVS. Of course it doesn't

RE: Wine CVS Documentation

2000-06-21 Thread Patrik Stridvall
When Alexandre have applied a documentation patch he will need to do ./tools/make_documentation or something, but then similar thing are required even now for debug messages to take one example. On a tangential note, it seems to me that we're not really addressing the whole job:

Wine CVS Documentation

2000-06-20 Thread John R . Sheets
As part of an effort to improve the accessibility of the Wine documentation, I've converted (most of) the contents of the wine/documentation directory into DocBook (an SGML variant). Naturally, quite a bit of the content is old and crusty, and perhaps even flat out wrong, but hopefully that can