- Wine-Devel - list.winehq.org

Wine-20040408 Compile Bug
by greensh＠knology.net April 9, 2004

April 9, 2004

Had a problem compiling this latest version on my Dell Latitude laptop... here is the exact make error; gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include -D__WINESRC__ -DBINDIR="\"/usr/local/bin\"" -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o keyboard.o keyboard.c keyboard.c: In function `X11DRV_ToUnicodeEx': keyboard.c:2128: error: `XK_EuroSign' undeclared (first use in this function) keyboard.c:2128: error: (Each undeclared identifier is reported only once keyboard.c:2128: error: for each function it appears in.) make[2]: *** [keyboard.o] Error 1 make[2]: Leaving directory `/data/0MD2/wine-20040408/dlls/x11drv' make[1]: *** [x11drv] Error 2 make[1]: Leaving directory `/data/0MD2/wine-20040408/dlls' make: *** [dlls] Error 2 Compilation failed, aborting install. Looks like it's wrong in detecting the keyboard. A fix was to comment out the if statement entirely; < if (keysym == XK_EuroSign) < { < bufW[0] = 0x20AC; < ret = 1; < goto found; < } --- > /* > if (keysym == XK_EuroSign) > { > bufW[0] = 0x20AC; > ret = 1; > goto found; > } > /* Then it compiled/installed fine. Shaun

1 0

Serial Port Problem
by TN April 9, 2004

April 9, 2004

Hi I already posted this on gmane.comp.emulators.wine.user but didn't get a response, maybe I have more luck here. I'm running wine-20040309 on a SuSE 8.2 system and trying to get Keil µVision2 Evaluation Version (Integrated Development Environment for Microcontrollers) working. So far, I've been pretty successful - most of it works. However, connecting a µC-Board at the serial port fails. The traces I get are as follows: fixme:comm:GetCommProperties (0xa0 0x408bf6f0 ) trace:comm:SetCommTimeouts (0xa0,0x42be02f8) trace:comm:SetCommMask handle 0xa0, mask 1 trace:comm:GetCommState handle 0xa0, ptr 0x42be02d8 trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 9600 fParity 0 Parity 0 stopbits 1 trace:comm:GetCommState IXON ~IXOFF trace:comm:GetCommState CRTSCTS trace:comm:SetCommState handle 0xa0, ptr 0x42be02d8 trace:comm:SetCommState bytesize 8 baudrate 9600 fParity 0 Parity 0 stopbits 1 trace:comm:SetCommState IXON ~IXOFF trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:WaitCommEvent (0xa0 0x42f00180 0x42be0328 ) trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:COMM_WaitCommEventService iosb 0x42be0328 trace:comm:GetCommMask handle 0xa0, mask 0x42f00184 trace:comm:ClearCommError handle 0xa0 cbInQue = 1 cbOutQue = 0 err:file:GetOverlappedResult PENDING status after waiting! trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:PurgeComm handle 0xa0, flags f trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:ClearCommError handle 0xa0 cbInQue = 0 cbOutQue = 0 trace:comm:WaitCommEvent (0xa0 0x42f00180 0x42be0328 ) Any help would be greatly appreciated. Thanks. Regards, Thomas

2 1

inheriting exec-shield avoidance
by Peter Riocreux April 9, 2004

April 9, 2004

I am intermittently trying to get Wine to play nicely with a big EDA tool, and it is doing not too badly today with the 20040309 snapshot on Fedora Core 1. The thing that I think is stopping it working is that whatever is done to stack-shield by the prepending "setarch i386" on invocation is not inherited by the .exe that the program calls. Net result is that I get the "..... security-patched kernel ?" error message from the child process instead of the parent. Progress of a sort. Is there anything, short of turning off exec-shield entirely, that can be done about this? The full set of messages it emits (with program identities obscured to avoid identifying the much-cheaper-when-bought-as-windows-binary application) is below. The printer message mentions an extant queue. ----8<--------8<--------8<--------8<--------8<--------8<---- err:dosmem:setup_dos_mem Cannot use first megabyte for DOS address space, please report err:dosmem:setup_dos_mem Cannot use first megabyte for DOS address space, please report err:dosmem:setup_dos_mem Cannot use first megabyte for DOS address space, please report fixme:console:SetConsoleCtrlHandler (0x41a8af,1) - no error checking or testing yet err:comm:GetCommState tcgetattr error 'Invalid argument' fixme:commdlg:PRINTDLG_OpenDefaultPrinter Could not open printer pica_duplex?! fixme:console:SetConsoleCtrlHandler (0x7800f03e,1) - no error checking or testing yet err:virtual:map_image Standard load address for a Win32 program (0x00400000) not available - security-patched kernel ? wine: could not load L"G:\\path\\to\\my\\child.exe" as Win32 binary ----8<--------8<--------8<--------8<--------8<--------8<---- Peter

4 8

Re: CryptoAPI
by dataphile April 9, 2004

April 9, 2004

I read in one of the list archives that someone was working on implementing CryptoAPI functionality via libgcrypt on the backend. Anyone have any more info on this?

1 0

Re: wine/dlls/msvcrt math.c
by Hans Leidekker April 9, 2004

April 9, 2004

On Thursday 08 April 2004 21:49, Alexandre Julliard wrote: > Modified files: > dlls/msvcrt : math.c > > Log message: > Portability fix. > > Patch: http://cvs.winehq.org/patch.py?id=11915 This isn't needed anymore. MinGW has accepted my patch that adds the defines to their header. I think that's the proper fix: they export fpclass() so they should export the corresponding defines for it's return values too. -Hans

1 0

Re: ShellExecute IE compatibility problems
by Martin Fuchs April 9, 2004

April 9, 2004

On 09.04.2004 02:03:37 Francois Gouget wrote: > > This patch fixes two IE compatibility problems. > > The first one is a mundane issue. IE calls ShellExecuteEx with a NULL > verb. Our implementation fails when it should use some sophisticated > algorithm described in the MSDN to choose a default verb. Well most of > the time we just want 'open' anyway so that's what this patch does. I've > left it as an exercise to the reader to head over to the MSDN and > implement the series of fallbacks we're supposed to implement. This is what SHELL_FindExecutable() tries to do when enumerating the registry keys. What is wrong with that - doesn't this work for you? I don't think we should go back and use "open" again if the verb parameter is NULL. Please correct the current algorithm, if it's not fully compliant. Regards, Martin

1 0

Re: Workaround a SoundBlaster 16 OSS bug
by Andreas Mohr April 9, 2004

April 9, 2004

Hi, On Fri, Apr 09, 2004 at 02:27:19AM +0200, Francois Gouget wrote: > Note: AFAIK Andreas' kernel patch has never been applied :-( In fact it has been, fortunately, just about two weeks ago... By Andreas Kies in 2.4.26-pre3. He'd already patched 2.6.x a bit earlier. I've been trying to get the slightest bit of attention about that DoS at that time, but after two very detailed fruitless mails to LKML, I just gave up: http://www.uwsg.iu.edu/hypermail/linux/kernel/0206.0/0087.html http://www.uwsg.iu.edu/hypermail/linux/kernel/0206.2/0033.html Andreas Kies told me that it seemed that they now cared a slight wee bit more about small fringe problems such as DoSes in 2.4.x... </sarcasm> > (now you know how to mount a DOS on these systems!) Ow, watch your words! This can be VERY easily misinterpreted as mounting a DOS partition somewhere!? (in fact I did fall for it the first couple of seconds) > Patch the fragment size if it does not match the current sound > format. This saves us from trigerring a kernel freeze on some OSS 2.4 + > SounBlaster 16 systems. Crap, I thought I'd sent a Wine patch at that time; it would have been the easiest thing to do. Anyway, glad to see it fixed now. Greetings, Andi (been finishing my wireless driver any single day for about 5 months now :))

2 1

Re: Regression
by Ivan Leo Murray-Smith April 8, 2004

April 8, 2004

> Tried to install on an updated (like 45 min old) CVS version to test it, > seems to get in an endless loop here. Alexandre committed a fix http://www.winehq.com/hypermail/wine-cvs/2004/04/0095.html Everything seems OK again, and hopefully will stay so. Ivan.

2 1

Re: Regression
by Ivan Leo Murray-Smith April 8, 2004

April 8, 2004

> Tried to install on an updated (like 45 min old) CVS version to test it, > seems to get in an endless loop here. You're wright, it loops :( Ivan.

1 0

Re: Re: inheriting exec-shield avoidance
by chmorgan＠charter.net April 8, 2004

April 8, 2004

Any idea when the kernel and wine changes will be going in? Then we can start asking people with Fedora to disable exec-shield and prelinking OR upgrade to kernel 2.6.X and the latest wine. There are people everyday that come onto #winehq with problems due to prelinking/exec-shield. Thanks, Chris > > From: "Dimitrie O. Paun" <dimi(a)intelliware.ca> > Date: 2004/04/08 Thu PM 03:10:35 EDT > To: Mike McCormack <mike(a)codeweavers.com> > CC: Peter Riocreux <par+wine_devel(a)silistix.com>, <wine-devel(a)winehq.org> > Subject: Re: inheriting exec-shield avoidance > > On Thu, 8 Apr 2004, Mike McCormack wrote: > > > I've attached the source code. The idea is to run it like this: > > > > wld /home/mike/wine/loader/wine-pthread my.exe > > Cool. One small nit: for consistency, can we name it wineld instead? > Or is it winepreld more apropriate? I'm thinking that wineld will > seem to be the counterpart of winegcc... > > -- > Dimi. > > > >

1 0