September 2010 - Wine-Devel

Re: [setupapi] added tests of SetupDiGetINFClassA
by testbot＠testbot.winehq.org Sept. 4, 2010

Sept. 4, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=5023 Your paranoid android. === WNT4WSSP6 (32 bit devinst) === No test summary line found === W2K3R2SESP2 (32 bit devinst) === devinst.c:1465: Test failed: expected error ERROR_INSUFFICIENT_BUFFER, got 87 === WVISTAADM (32 bit devinst) === devinst.c:1465: Test failed: expected error ERROR_INSUFFICIENT_BUFFER, got 87 === W2K8SE (32 bit devinst) === devinst.c:1465: Test failed: expected error ERROR_INSUFFICIENT_BUFFER, got 87 === W7PRO (32 bit devinst) === devinst.c:1465: Test failed: expected error ERROR_INSUFFICIENT_BUFFER, got 87 devinst.c:1476: Test failed: expected error RPC_S_INVALID_STRING_UUID, got 87 === W7PROX64 (32 bit devinst) === devinst.c:1465: Test failed: expected error ERROR_INSUFFICIENT_BUFFER, got 87 devinst.c:1476: Test failed: expected error RPC_S_INVALID_STRING_UUID, got 87 === W7PROX64 (64 bit devinst) === devinst.c:1465: Test failed: expected error ERROR_INSUFFICIENT_BUFFER, got 87 devinst.c:1476: Test failed: expected error RPC_S_INVALID_STRING_UUID, got 87

1 0

Wine Introduction Page
by James McKenzie Sept. 4, 2010

Sept. 4, 2010

I was just going over this page and found a few things that I don't know about but have questions on for building Wine on the Mac: The lowest MacOSX version that Wine will build on from the native package is stated to be 10.4 (Tiger). Is this still true? The lowest XCode required is 2.4. Apple stopped supporting this a long time ago. I had XCode 2.5 for Tiger. Can anyone update these? James McKenzie

2 1

Wine Gecko 1.1.0 RC1
by Jacek Caban Sept. 4, 2010

Sept. 4, 2010

HI all, (If you're not interested in details, please read the last paragraph). It's been over year since the last Gecko update. A lot has happen since then. I've been planning to update our build a bit later, with Firefox 4 codebase, but plans have changed. We had some serious problems with previous build (like bug 22157 and bug 24059, both should be fixed in the new build). Also there is *a lot* happening in Mozilla world. With upcoming Firefox 4, the backward compatibility is no longer supported and the code is changing with an impressive speed. I try to follow these changes, but I need a good solid base so that I can take care of our needs in Mozilla. This build is based on Firefox 4 beta 4 (that is expected to be released this week). It goes with massive improvements, but it's less interesting here. We finally have sane building procedure. Thanks to mingw-w64 project, we no longer have to maintain our own fixes to headers and libraries. Also I've fixed a bug so that moztools is no longer needed for crosscompiling. It means that we no longer need any binary files, which should make open source fanatics (in a good sense) happy. Well... almost. We still need to create .cab file, which I do via Filzip on Windows. That's something we can work around. We use .cab files, because that's the only archive format that Wine can deal with. We can teach Wine to use other formats, which would finally make it possible for Wine packagers to do their own builds, if they like. The new Gecko is also the first to support Win64. Not all tests pass yet, but failing ones are due to missing DispCallFunc implementation for Win64, so it's not a Gecko problem. It's not yet fully tested and I need help with this. I'd appreciate any help with testing. Almost all changes required by the new Gecko were possible to be committed to current Wine. The attached patch contains remaining bits. All you need to test it is current Wine Git (must be today's or later), the attached patch and a new Gecko build. You can find new builds [1] and win64 build [2]. Put .cab files according to generic instructions [3] (obviously with different file names due to different Gecko versions). Please let me know of any regressions. Thanks, Jacek [1] http://gerwazy.lo3.wroc.pl/~jcaban/wine_gecko-1.1.0-rc1-x86.cab [2] http://gerwazy.lo3.wroc.pl/~jcaban/wine_gecko-1.1.0-rc1-x86_64.cab [3] http://wiki.winehq.org/Gecko

4 7

New winetricks 20100904: lots of little fixes. New verbs comdlg32.ocx, vcrun2010
by Dan Kegel Sept. 4, 2010

Sept. 4, 2010

Another fortnight, another Winetricks. Online as always at http://kegel.com/wine/winetricks or http://winezeug.googlecode.com (Bug reports to the issue tracker at the above URL, please.) Winetrickstest really paid off this time... it caught three problems before release. Changes: Dan Kegel: update shockwave sha1sum stop using busted sourceforge mirror revert change that broke dinput8 (unfixed issue 149) use XDG_CACHE_HOME. Fixes issue 124. fix checksum on macosx (thanks to slevytam for logs) add catchall dll-disabling verb, foo=disabled remove fakeie6, it hasn't been needed for a long time. Fred Joseph Ladd: nicer title and text for zenity dialog fix typo, misc string fixes (issue 146) add comdlg32.ocx add vcrun2010 add ISBn for 'Portable Shell Programming'. Austin English: add xapofx as a synonym to xact. (Issue 133) delete .Net registry keys before installing .Net. (Issue 158) remove ancient Mono versions add a synonym for wsh56js (jscript) Andrew Nguyen: add support for new gecko for wine-1.3.2 and up. (Note: gecko-dbg might not be happy yet, it fails winetrickstest.)

1 0

Re: [PATCH 7/7] CMD: Change the parameterization to be correct
by testbot＠testbot.winehq.org Sept. 3, 2010

Sept. 3, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=5018 Your paranoid android. === WNT4WSSP6 (32 bit) === batch.c:185: Test failed: unexpected char 0x43 position 0 in line 59 (got 'CD:''', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 60 (got 'CD:''', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 61 (got 'CD end:''', wanted 'CD end:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 62 (got 'C:\winetest\testdir', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 63 (got 'CD end:''', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 64 (got 'C:\winetest\testdir', wanted 'CD end:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 65 (got 'CD end:''', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 66 (got 'C:\winetest\testdir', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 67 (got 'CD end:''', wanted 'CD end:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 68 (got 'C:\winetest\testdir', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 69 (got 'CD end:''', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 70 (got 'C:\winetest\testdir', wanted 'CD end:'@pwd@'') batch.c:185: Test failed: unexpected char 0x2d position 0 in line 71 (got '-----------Testing parameterization -----------', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 72 (got 'p1: '1'', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 73 (got 'p2: ''', wanted 'CD end:'@pwd@'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 74 (got 'p3: ''', wanted '-----------Testing parameterization -----------') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 76 (got 'p2: '2'', wanted 'p2: ''') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 80 (got 'p3: '3'', wanted 'p3: ''') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 81 (got 'p1: '"b"'', wanted 'p1: '1'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 82 (got 'p2: ''', wanted 'p2: '2'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 83 (got 'p3: ''', wanted 'p3: '3'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 84 (got 'p1: 'a"b"c'', wanted 'p1: '"b"'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 87 (got 'p1: '"a"bc'', wanted 'p1: 'a"b"c'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 90 (got 'p1: 'a'', wanted 'p1: '"a"bc'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 91 (got 'p2: 'bc'', wanted 'p2: ''') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 93 (got 'p1: '"a=bc d'', wanted 'p1: 'a'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 94 (got 'p2: ''', wanted 'p2: 'bc'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 96 (got 'p1: 'a""b'', wanted 'p1: '"a=bc d'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 99 (got 'p1: 'a'', wanted 'p1: 'a""b'') batch.c:185: Test failed: unexpected char 0x70 position 0 in line 100 (got 'p2: 'b'', wanted 'p2: ''') batch.c:185: Test failed: unexpected char 0x69 position 0 in line 102 (got 'if exist test failed', wanted 'p1: 'a'') batch.c:196: Test failed: unexpected end of output in line 102, missing p2: 'b'

1 0

re: Opinions on priority for an enhancement that Dan suggested some time ago?
by Dan Kegel Sept. 3, 2010

Sept. 3, 2010

Tom Spear wrote: > I believe it would be prudent to have some warning appear when > certain native dll's are missing which required by the app being > run, and which we do not implement builtins for. I suppose a +winediag message might be appropriate for some commonly-needed DLLs. Probably there'd be a table of which DLLs to warn for. Nobody has hooked +winediag up to any flag-the-user system yet, but that's what I had in mind in http://bugs.winehq.org/show_bug.cgi?id=657#c39 I'm more focused on the idea of reducing the need for native DLLs than making it easy to install them. (Um, well, except for winetricks, which seems good enough for the moment.)

1 0

Re: [PATCH 6/7] CMD: Current directory needs saving in the environment even for cmd /c
by testbot＠testbot.winehq.org Sept. 3, 2010

Sept. 3, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=5017 Your paranoid android. === WNT4WSSP6 (32 bit batch) === batch.c:185: Test failed: unexpected char 0x43 position 0 in line 59 (got 'CD:''', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 60 (got 'CD:''', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 61 (got 'CD end:''', wanted 'CD end:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 62 (got 'C:\winetest\testdir', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 63 (got 'CD end:''', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 64 (got 'C:\winetest\testdir', wanted 'CD end:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 65 (got 'CD end:''', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 66 (got 'C:\winetest\testdir', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 67 (got 'CD end:''', wanted 'CD end:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 68 (got 'C:\winetest\testdir', wanted 'CD:'@pwd@'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 69 (got 'CD end:''', wanted 'CD:'@pwd@\testdir'') batch.c:185: Test failed: unexpected char 0x43 position 0 in line 70 (got 'C:\winetest\testdir', wanted 'CD end:'@pwd@'') batch.c:196: Test failed: unexpected end of output in line 70, missing CD:'@pwd@'

1 0

Re: [PATCH 5/7] CMD: Add support for echo "on"
by testbot＠testbot.winehq.org Sept. 3, 2010

Sept. 3, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=5016 Your paranoid android. === WNT4WSSP6 (32 bit) === batch.c:188: Test failed: unexpected end of output in line 53, expected 0x30

1 0

Opinions on priority for an enhancement that Dan suggested some time ago?
by Tom Spear Sept. 3, 2010

Sept. 3, 2010

Hi all, so it has been a long time since I have posted here. Much has changed; I now have 3 little ones. :-) Anyways, right to the point: I stumbled on an old bug of mine this evening while doing some long overdue mailbox maintenance. Bug 657: http://bugs.winehq.org/show_bug.cgi?id=657 Dan made a very good point back in 2007 that I believe now is the right time to possibly look at beginning an implementation of: [1] To summarize: Similar to the way that we now have a popup about wine-gecko missing, I believe it would be prudent to have some warning appear when certain native dll's are missing which required by the app being run, and which we do not implement builtins for. Similarly, I feel that it would be prudent for warnings to appear if certain linux shared objects are missing. More to the point is that there are quite a number of DLL's which won't be implemented soon, if ever, but yet we support running wine from the GUI both through shortcuts, and through binfmt_misc, thereby completely bypassing any hope of a user ever seeing some pretty critical errors that may occur. These errors could, if popped up on their screen, prevent a bunch of duplicates from appearing in Bugzilla, because the user can google for the error and be directed directly to a bug which someone else made, as opposed to not seeing anything and having no idea what to try googling for other than "app x does this +wine" As an example on the shared object side, on FC13 x86_64, using the rpm from the yum repo that RH provides, I can install wine, but since there is no RPM dependency currently for OpenAL (i686), I get "no such file/directory" warnings about the OpenAL shared objects when running certain programs (specifically, World of Warcraft and Starcraft II). Now granted the fact that OpenAL is not installed is, debatibly something to take up with the wine packager for RedHat and derivatives; I wanted to point out that with the way wine is at present, if I didn't run wine from a console, I would never have known that, and probably would still not have working sound, because there is nothing that says "Hey! You're missing OpenAL!" I'd like to hear opinions from others about what it might take, time-wise, if someone were to start now, to have something like this implemented. And also what kind of a priority this type of thing should have. Sure it is an enhancement, and so is naturally lower priority than, say a segfault in ntdll, but (imho) it's a pretty critical enhancement that is (again, imho) long overdue. Thoughts? Questions? [1] http://bugs.winehq.org/show_bug.cgi?id=657#c37 Also see comments of his below #37. Thanks Tom

1 0

Re: [PATCH 4/7] CMD: echo command needs to ignore whitespace
by testbot＠testbot.winehq.org Sept. 3, 2010

Sept. 3, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=5015 Your paranoid android. === WNT4WSSP6 (32 bit) === batch.c:188: Test failed: unexpected end of output in line 51, expected 0x30

1 0