April 2003 - Wine-Devel - list.winehq.org

Re: What happend to the Stdole2 / Stdole32 (RESEND) patch from Robert Shearman

by Robert Shearman

> what happend to the stdole32.tlb patch that Robert sent around 22.1? It was rejected on the grounds that we shouldn't have binary files in CVS and we can't generate the .tlb files at the moment. Rob

April 2, 2003

Re: Visual FoxPro 8 / Wine20030318 crash

by Sylvain Petreolle

Why does this thing need network activity to build an EXE ?? > fixme:wininet:InternetGetConnectedState always returning LAN > connection. ===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War ! "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

April 2, 2003

Agent and threads

by Rein Klazes

Hi, Agent news/email client spawns a new thread for each news/mail retrieval command. Something in the last week causes these threads not to be waited upon, leaving hundreds of <defunct> wine processes lying around. I wonder if this is a known issue with the new thread implementation work in progress, or if it is worth investigating? Rein. -- Rein Klazes rklazes(a)xs4all.nl

April 2, 2003

CVS Statistics for academic research

by Riccardo 'Jack' Lucchetti

Hi all, this message was originally sent to Alexandre Juilliard; I am resending this to the list on his suggestion. I am a wine user and a regular mailing list lurker. Beside that, however, I earn my living as an academic econometrician (halfway between an economist and a statistician) and I was considering the idea of doing some econometric research on open source development. At least initially, I would focus on Wine, for a number or reasons, not least the fact that the wine project is largely unknown in the economics community. My problem is that the data I need for my analysis can be theoretically extracted from the mailing list archives, but this definitely exceeds my VERY limited perl skills. The data I'd need would, ideally, be in the form of a CSV file, a typical record of which would be DATE,PN,PLA,PLD,PCN,CN,CLA,CLD where PN = number of patches received on day DATE PLA = number of code lines added in patches PLD = number of code lines deleted in patches PCN = number of patches contributors (ie number of coders submitting patches on that particular day) CN = CVS commits CLA = number of lines added in CVS CLD = number of lines deleted in CVS Of course, the longer the time span the data cover, the larger my sample, the happier I am. I understand this isn't trivial. Is there anyone out there willing to help me? I know some perl, so maybe all I need is to get started somehow. Thanks in advance, and keep up the good work! ---------------------------------------------------------- Riccardo `Jack' Lucchetti Dipartimento di Economia Università di Ancona jack(a)dea.unian.it http://www.econ.unian.it/lucchetti

April 2, 2003

Re: Unexpected message from winebuild...

by juraj

Hi Kevin, I had similar problem with winemaker when I used winemaker's --wrap option. I hacked winemaker script (see attachment) and managed to get rid of "...could not open .def file for...". If you see it, the difference is that .dll extension was removed from libnames in makefiles. I.e. there is only kernel32 instead of kernel32.dll, and so on. This helped me to get rid of problem with missing .def file.The second adjustment is related to incorrect generation of wrapper exe spec.c file. However, I'm not sure it's correct hack (that's the reason I didn't post it to wine-patches yet) since I have still troubles with running wrapped application - simple hello world example. The problem I have is that GetProcAddress couldn't find the WinMain() of my hello world app. After a little debugging and inspection of .spec.c file it seems the problem is with winebuild and not with winemaker (__wine_spec_exports is resolved to NULL and that's bad...). But I need to investigate little more yet. Anyways I got information from #winehq irc channel that winemaker is beeing deprecated, and that I should try to use winegcc with winewrap instead. But I'm not sure whether these two guys are able to cope with wrapping. I wasn't able to find some documentation about them and winewrap alone throws segmentation fault in my current build (updated & build today, about 3 hours ago). --Juraj Index: tools/winemaker =================================================================== RCS file: /home/wine/wine/tools/winemaker,v retrieving revision 1.63 diff -u -r1.63 winemaker --- tools/winemaker 27 Mar 2003 18:36:27 -0000 1.63 +++ tools/winemaker 31 Mar 2003 20:53:53 -0000 @@ -1001,7 +1001,7 @@ @$wrapper[$T_TYPE]=@$target[$T_TYPE]; @$wrapper[$T_INIT]=get_default_init(@$target[$T_TYPE]); @$wrapper[$T_FLAGS]=$TF_WRAPPER | (@$target[$T_FLAGS] & $TF_MFC); - @$wrapper[$T_DLLS]=[ "kernel32.dll", "user32.dll" ]; + @$wrapper[$T_DLLS]=[ "kernel32", "user32" ]; push @{@$wrapper[$T_LIBRARIES]}, "dl"; push @{@$wrapper[$T_SOURCES_C]},"@$wrapper[$T_NAME]_wrapper.c"; @@ -1650,7 +1650,6 @@ my $path=$_[0]; my $target=$_[1]; my $app_name=@$target[$T_NAME]; - $app_name=~ s/\.exe$//; return generate_from_template("$path${app_name}_wrapper.c","wrapper.c",[ ["APP_NAME",$app_name],

April 2, 2003

Re: winsock.h portability patch causing portability problem

by Gerald Pfeifer

On Wed, 1 Apr 2003, Alexandre Julliard wrote: > I changed the way we handle htonl a bit. Does it work better now? Yes, thanks a lot! Now it builds, though I'm getting warnings: In file included from /usr/include/sys/types.h:126, from ../../include/winsock.h:89, from ../../include/winsock2.h:47, from ../../include/windows.h:62, from icinfo.c:21: /usr/include/machine/endian.h:105: warning: `ntohl' redefined ../../include/winsock.h:87: warning: this is the location of the previous definition /usr/include/machine/endian.h:106: warning: `ntohs' redefined ../../include/winsock.h:88: warning: this is the location of the previous definition /usr/include/machine/endian.h:107: warning: `htonl' redefined ../../include/winsock.h:85: warning: this is the location of the previous definition /usr/include/machine/endian.h:108: warning: `htons' redefined ../../include/winsock.h:86: warning: this is the location of the previous definition (Do you see any way to avoid these warnings? They're quite numerious and hiding real portability problems I'm currently tracking down.) Thanks for fixing this so quickly! Gerald -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.pfeifer.com/gerald/

April 2, 2003

What happend to the Stdole2 / Stdole32 (RESEND) patch from Robert Shearman

by Uwe Bonnes

Hallo, what happend to the stdole32.tlb patch that Robertsent around 22.1? Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

April 2, 2003

Re: FindFirstFileExW

by Mike Hearn

I ran my test case on 98, and that produced a return value of 2 as well (same as XP), so unless my test case is stuffed up, I think this patch is correct. The test is attached, it's extremely simple. On Tue, 2003-04-01 at 16:37, Mike Hearn wrote: > > That sounds awfully much like the already pretty well-known Win9x vs. NT > > incompatibility in file not found GetLastError values. > > Awwww suckage. I thought that fix was too easy. File not found > differences are new to me. Well I have a little test case for this, I'll > email it home and find out what it returns on Win98. > > If so, then, how do you find out what version of windows we're supposed > to be emulating, so I can adjust the return value accordingly? > > > Please make sure this is indeed what we should do; I really think > > you'd break some Win9x programs when simply doing such a general replacement. > > Hmm, well, the old value appeared to break some NT programs. > > > As such, I suspect you did not "Correct" the error code returned; > > instead, you only fixed it "to please the other half" of Windows programs. > > ;-) > > Right. So we need to change the return value depending on the setting of > winver? -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

April 2, 2003

Re: Visual FoxPro 8 / Wine20030318 crash

by Uwe Bonnes

>>>>> "Paul" == Paul McNett <p(a)ulmcnett.com> writes: Paul> I crash when building an EXE in the new version of Visual Foxpro. Paul> Any ideas? "windows" = "nt351", all dlls built-in. Here's the Paul> output leading up to the crash: Paul> fixme:hook:NotifyWinEvent (32769,0x50032,1,0)-stub! Paul> fixme:pidl:SHLogILFromFSIL (pidl=0x4032b090) Paul> fixme:dc:LockWindowUpdate (0x50033), partial stub! Paul> fixme:shell:ISVBgCm_fnGetCommandString unknown command string Paul> fixme:shell:ISVBgCm_fnGetCommandString unknown command string Paul> fixme:shell:ISVBgCm_fnGetCommandString unknown command string Paul> fixme:dc:LockWindowUpdate ((nil)), partial stub! Paul> fixme:shell:ReadCabinetState 0x4071e2e0 0x000c stub Paul> fixme:hook:NotifyWinEvent (32773,0x30031,7,1)-stub! Paul> fixme:hook:NotifyWinEvent (32768,0x90032,1,0)-stub! Paul> fixme:hook:NotifyWinEvent (32769,0x90032,256,0)-stub! Paul> fixme:hook:NotifyWinEvent (32769,0x90032,1,0)-stub! Paul> fixme:ole:DispCallFunc Do not know how to handle pvargResult ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Paul> 0x4071e5cc. Expect crash ... fixme:ole:DispCallFunc Method Paul> returned 0 err:ole:TLB_ReadTypeLib Loading of typelib Paul> L"E:\\src\\vfp\\sbs\\sbs.exe" failed with error 0 Paul> fixme:seh:EXC_RtlRaiseException call to unimplemented function Paul> kernel32.dll.BeginUpdateResourceA fixme:process:CreateProcessA ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ For the first error, either try with a combo of the native OLE dlls (ole2,ole32,oleaut32, rpcrt4 and maybe more) or hope that some of the OLE gurus( Hey Marcus :-) picks up the problem. For the unimplemented function, perhaps try to add a stub implementation. Look in the archives how others did it ( find out the arguments, add the entry in the spec file, add a stub implementation in a .c file and send the patch). Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

April 2, 2003

Re: glibc tracker bug

by Dmitry Timoshkov

"Kevin DeKorte" <kdekorte(a)yahoo.com> wrote: > RedHat 8.0 up2date with glibc-2.3.2-4.80 > > Wine compiles fine, no extra options are needed. But if wine has been built > on the RedHat 8.0 OTB, then you should download a clean source tarball or if > you use CVS, you should delete your working dir and check it out again. That means that binary compatibility between glibc-2.3.2-4.80 and a previous version is broken. It would be very helpful to try to track it down or at least report this problem to RedHat. -- Dmitry.

April 2, 2003