June 2010 - Wine-Devel - list.winehq.org

Re: [PATCH 3/3] shlwapi: Implement SHSetIniStringW
by testbot＠testbot.winehq.org June 6, 2010

June 6, 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=2490 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:604: Test failed: GetShellSecurityDescriptor should fail ordinal.c:627: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1776: Test failed: got 25 ordinal.c:1826: Test failed: got 25 ordinal.c:1834: Test failed: got 25 ordinal.c:1842: Test failed: got 36, length 37 ordinal.c:1853: Test failed: got 39 === W7PROX64 (32 bit ordinal) === ordinal.c:1776: Test failed: got 22 ordinal.c:1826: Test failed: got 22 ordinal.c:1834: Test failed: got 22 ordinal.c:1842: Test failed: got 31, length 32 ordinal.c:1853: Test failed: got 34 === W7PROX64 (64 bit ordinal) === ordinal.c:1776: Test failed: got 22 ordinal.c:1826: Test failed: got 22 ordinal.c:1834: Test failed: got 22 ordinal.c:1842: Test failed: got 31, length 32 ordinal.c:1853: Test failed: got 34

1 0

Re: [PATCH 2/3] shlwapi: Implement SHGetIniStringW
by testbot＠testbot.winehq.org June 6, 2010

June 6, 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=2489 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:603: Test failed: GetShellSecurityDescriptor should fail ordinal.c:626: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1775: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 25 ordinal.c:1841: Test failed: got 36, length 37 ordinal.c:1852: Test failed: got 39 === W7PROX64 (32 bit ordinal) === ordinal.c:1775: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 22 ordinal.c:1841: Test failed: got 31, length 32 ordinal.c:1852: Test failed: got 34 === W7PROX64 (64 bit ordinal) === ordinal.c:1775: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 22 ordinal.c:1841: Test failed: got 31, length 32 ordinal.c:1852: Test failed: got 34

1 0

Re: [PATCH 1/3] shlwapi: Be less strict on which type of IShellFolder can be enumerated
by testbot＠testbot.winehq.org June 6, 2010

June 6, 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=2488 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:595: Test failed: GetShellSecurityDescriptor should fail ordinal.c:618: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1767: Test failed: got 25 ordinal.c:1817: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 36, length 37 ordinal.c:1844: Test failed: got 39 === W7PROX64 (32 bit ordinal) === ordinal.c:1767: Test failed: got 22 ordinal.c:1817: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 31, length 32 ordinal.c:1844: Test failed: got 34 === W7PROX64 (64 bit ordinal) === ordinal.c:1767: Test failed: got 22 ordinal.c:1817: Test failed: got 22 ordinal.c:1825: Test failed: got 22 ordinal.c:1833: Test failed: got 31, length 32 ordinal.c:1844: Test failed: got 34

1 0

Re: appwiz: Add the Polish translation
by Sven Baars June 6, 2010

June 6, 2010

Hey Łukasz, all your translations are written in UTF-8, but to actually use UTF-8, you also have to include a #pragma code_page(65001) on top of the file. In this case for example +#include "res.h" + +LANGUAGE LANG_POLISH, SUBLANG_DEFAULT + +#pragma code_page(65001) Atm, if you compile wine with this patch applied you see: sven(a)sven-desktop:~/wine-git/dlls/appwiz.cpl$ make LD_LIBRARY_PATH="../../libs/wine:$LD_LIBRARY_PATH" ../../tools/wrc/wrc --nostdinc -I. -I. -I../../include -I../../include -D__WINESRC__ -foPl.res Pl.rc Warning: string "Aby doda� program z dysku, p�yty CD-ROM lub dyskietki, kliknij przycisk Zainstaluj" seems to be UTF-8 but codepage 1250 is in use. Warning: string "To oprogramowanie mo�e by� usuni�te automatycznie. Aby usun�� program lub zmieni� jego zainstalowane komponenty, zaznacz go z listy i naci�nij Zmie�/Usu�." seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Zmie�..." seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Usu�..." seems to be UTF-8 but codepage 1250 is in use. Warning: string "Podane informacje mog� by� przydatne przy otrzymaniu pomocy technicznej dla %s:" seems to be UTF-8 but codepage 1250 is in use. Warning: string "Dodaj/Usu� programy" seems to be UTF-8 but codepage 1250 is in use. Warning: string "Pozwala na instalacj� nowego lub usuni�cie ju� istniej�cego oprogramowania z twojego komputera." seems to be UTF-8 but codepage 1250 is in use. Warning: string "Nie mo�na uruchomi� programu odinstalowuj�cego, '%s'. Czy chcesz usun�� wpis o tym programie z rejestru?" seems to be UTF-8 but codepage 1250 is in use. Warning: string "Nie okre�lone" seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Usu�..." seems to be UTF-8 but codepage 1250 is in use. Warning: string "&Zmie�/Usu�..." seems to be UTF-8 but codepage 1250 is in use. You get warnings like this for every patch that you sent in. You can check it yourself by running "make depend" from the git directory and then "make" from the directory that contains the program or dll. This is at least how I got them. Regards, Sven P.S. You're not the only one making this mistake. I also made it the first time ;) Łukasz Wojniłowicz wrote: > --- > dlls/appwiz.cpl/Makefile.in | 1 + > dlls/appwiz.cpl/Pl.rc | 84 +++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 85 insertions(+), 0 deletions(-) > create mode 100644 dlls/appwiz.cpl/Pl.rc >

1 0

Release plans
by Alexandre Julliard June 6, 2010

June 6, 2010

Folks, The 64-bit support is now more or less complete, and we have most of the fancy new icons, so it's time to think about the next stable release. Unless some major problems come up, 1.1.44 will be the last of the 1.1.x series. The next release will be 1.2-rc1, which will mark the beginning of the code freeze. This should result in a 1.2 final sometime in June. As usual the code freeze will become more and more drastic as we get closer to release, so if you have major changes to make, now is pretty much the last minute. I'd encourage everyone to look through the list of nominated 1.2 bugs, and also to check the regression reports for anything that might be in your area. We should strive to have as few regressions from 1.0 as possible, so regressions fixes will have priority during code freeze. And of course changes that don't impact the code, like translations or test fixes, can go in until quite late. -- Alexandre Julliard julliard(a)winehq.org

14 26

re: Advice about a new project, and similarity to Wine's start
by Dan Kegel June 6, 2010

June 6, 2010

Alessandro Pignotti wrote: > how did Wine choose the feature set to support first? Pragmatically - by trying to get particular popular apps running. (Starting with solitaire :-) > Did people use the early releases of Wine, even if they were missing features? Yes, as soon as they ran their favorite app. So in your case, as soon as your flash player can handle youtube.com (or whatever free software afficianados can't live without), a few people will start using it. > Is the AppDB software available for use on other projects? Should be. > Any misc advice? The Wine project started moving faster when we switched to test-driven development. I highly recommend it. Do you have a test suite? And/or can you share existing test suites ( e.g. http://wiki.gnashdev.org/Testcases ) ? That said, visual stuff is hard to test automatically, so mostly our automated tests only test the API level. Visual tests are done manually and much less often (say, only when changing directly affected code). Automated performance benchmarks are a good idea, though we haven't done as much of that. Good luck! - Dan

2 1

Advice about a new project, and similarity to Wine's start
by Alessandro Pignotti June 6, 2010

June 6, 2010

Hi everyone, first of all congratulations. The current maturity of Wine is really, really impressive. Thanks for your work. Let's introduce myself, I'm the author of the Lightspark project (http://lightspark.sf.net) a modern, open source, flash player implementation. The project is currently in a very good shape, featuring scripting support, a JIT compiler and OpenGL accelerated rendering. But, although the core VM is mostly complete, a huge part of the runtime library is still missing. I'm asking advice here because this is probably a condition similar to the one faced by early Wine developers. I'm currently pretty confused about the roadmap of my project. Although some interest gathered after the announcement of the 0.3.0 release and some bug reports appeared I've not yet managed to gather the needed community feedback. Moreover, beside supporting the most popular flash applications (e.g. YouTube, which is mostly supported), I've no idea about what to do later and how to prioritize features. So my question is: how did Wine choose the feature set to support first? Did people use the early releases of Wine, even if they were missing features? Is the AppDB software available for use on other projects? Any misc advice? Thanks a lot for your help. and sorry for the quite OT message, Alessandro Pignotti

2 1

Wine code comments
by John Voltz June 5, 2010

June 5, 2010

Hi everyone, I have a question about comments in the Wine code. I noticed while tracking down a bug that a lot of the code comments are using the block comment marker /*. This is a royal pain when trying to comment out large sections of code where there are a bunch of /* foo */ comments. Why is this allowed? Is there are way around it without having to change them all to //? Regards, John Voltz

6 8

Re: shdoclc: Add the Polish translation (try 2)
by Paul Vriens June 5, 2010

June 5, 2010

On 06/05/2010 01:38 PM, Łukasz Wojniłowicz wrote: > + MENUITEM "&Odœwie¿ > +", _IDM_REFRESH Hi Łukasz, Something went wrong here. -- Cheers, Paul.

1 0

Re: [PATCH 1/3] shlwapi: Be less strict on which type of IShellFolder can be enumerated
by Nikolay Sivov June 5, 2010

June 5, 2010

On 6/3/2010 23:35, Andrew Eikum wrote: > > This fixes a bug with Internet Explorer 6's Favorites menu. > > This function used to be named IUnknown_EnumObjects, so my guess is > that the original implementor thought it'd be wise to verify the type > of the object before executing IShellFolder's methods on it. Since > it's now called IShellFolder_EnumObjects and explicitly takes an > LPSHELLFOLDER parameter, I see no reason to do the typecheck. And where is a test for that? > > --- > dlls/shlwapi/ordinal.c | 19 +------------------ > dlls/shlwapi/tests/Makefile.in | 2 +- > dlls/shlwapi/tests/ordinal.c | 32 ++++++++++++++++++++++++++++++++ > 3 files changed, 34 insertions(+), 19 deletions(-)

2 9

Re: shdoclc: Add the Polish translation
by Paul Vriens June 5, 2010

June 5, 2010

On 06/04/2010 04:33 PM, Łukasz Wojniłowicz wrote: > + > +LANGUAGE LANG_POLISH, SUBLANG_NEUTRAL > + > +IDR_BROWSE_CONTEXT_MENU MENU Hi Łukasz, Sorry if I wasn't clearer before. You are having effectively two blocks with the same translations now. The reason the English resource file has two blocks is because it has effectively two translations (one for SUBLANG_DEFAULT and one for SUBLANG_NEUTRAL). There is no need to do that in most of the other resource files like Polish as there is only one Polish language (as far as resource files are concerned). Could you also add something to the Subject when resending? So for example "(Resend)" when sending the same patch again or "(Try x)" when you sent a new version of the patch. -- Cheers, Paul.

1 0

Wine on MIPS?
by André Hentschel June 5, 2010

June 5, 2010

Hi, i just read that MIPS is planning to get on the mobil market. It will be available in 4G Smartphones with Android. Wine has a MIPS port which should also run those obsolete Win32 MIPS Apps, so i guess the winelib side is more interesting. So here my question: did anyone recently tried to compile Wine on MIPS and did it worked? If not, is anybody able to? -- Best Regards, André Hentschel

1 0

Re: [1/2]wineps.drv: make use of MAKEINTRESOURCEW
by Dmitry Timoshkov June 4, 2010

June 4, 2010

André Hentschel <nerv(a)dawncrow.de> wrote: > +#define PAPER 99 > #define IDD_PAPERS 100 > #define IDD_ORIENT_PORTRAIT 101 > #define IDD_ORIENT_LANDSCAPE 102 You could try to find a less generic name for this. -- Dmitry.

1 0

Re: [2/2]wineps.drv: Import comctl32 instead of loading it
by Dmitry Timoshkov June 4, 2010

June 4, 2010

André Hentschel <nerv(a)dawncrow.de> wrote: > -IMPORTS = user32 gdi32 winspool advapi32 kernel32 > +IMPORTS = user32 gdi32 winspool advapi32 kernel32 comctl32 It's being loaded for a reason. You can make it delay loaded though. -- Dmitry.

1 0

Re: [PATCH] msi/tests: Fix install tests for Win9x
by testbot＠testbot.winehq.org June 4, 2010

June 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=2470 Your paranoid android. === WNT4WSSP6 (32 bit install) === Timeout === W7PROX64 (32 bit install) === install.c:5411: Test failed: Expected "C:\Program Files (x86)\msitest\maximus", got "Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\84A88FD7F6998CE40A22FB59F6B9C2BB\InstallProperties" install.c:5430: Test failed: Expected "01\msitest\augustus", got "Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\84A88FD7F6998CE40A22FB59F6B9C2BB\InstallProperties" install.c:5455: Test failed: Expected "C:\Program Files (x86)\msitest\maximus", got "Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\84A88FD7F6998CE40A22FB59F6B9C2BB\InstallProperties" install.c:5474: Test failed: Expected "01\msitest\augustus", got "Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\84A88FD7F6998CE40A22FB59F6B9C2BB\InstallProperties" === W7PROX64 (64 bit install) === install.c:3534: Test failed: Expected 314, got 1 install.c:8264: Test failed: RegQueryValueExA failed 2 (0)

1 0

Re: shdoclc: Add the Polish translation
by Paul Vriens June 4, 2010

June 4, 2010

On 06/04/2010 01:05 PM, Łukasz Wojniłowicz wrote: > + > +LANGUAGE LANG_ENGLISH, SUBLANG_NEUTRAL This doesn't look correct for Polish ;) -- Cheers, Paul.

1 0

Re: appwiz: Add the Polish translation
by Paul Vriens June 4, 2010

June 4, 2010

On 06/04/2010 01:05 PM, Łukasz Wojniłowicz wrote: > dlls/appwiz.cpl/Makefile.in | 1 + > dlls/appwiz.cpl/Pl.rc | 84 +++++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 85 insertions(+), 0 deletions(-) > create mode 100755 dlls/appwiz.cpl/Pl.rc Hi Łukasz, Wrong mode here. Should be the normal 100644 (like you other recent patches). -- Cheers, Paul.

1 0

Re: [PATCH 2/2] cmd: Update Dutch translation
by Frédéric Delanoy June 4, 2010

June 4, 2010

2010/6/2 Sven Baars <sven.wine(a)gmail.com> > --- > programs/cmd/Nl.rc | 194 > ++++++++++++++++++++++++++++----------------------- > 1 files changed, 106 insertions(+), 88 deletions(-) > Hi Sven, Some remarks: - You shouldn't change the line length as it makes the patch unnecessarily big, for no change in text (for the affected hunks) - "bestaat keert de controle terug naar het bestand dat het aanriep. DE CALL\n\" => "DE" should be "De" Frédéric

3 2

[RFC] advapi32 -- GetNamedSecurityInfo
by GOUJON Alexandre June 4, 2010

June 4, 2010

Hi, I'm trying to fix bug 18071 but I don't know anything about ACLs. I wrote some tests (see attached patch and https://testbot.winehq.org/JobDetails.pl?Key=2442) and I modified the source according to my understanding of the issue (wich may be totally wrong). But as I'm not familiar with ACLs and because my changes are quite important, I'm sending here my patches hoping a advapi32 coder could have a look at it. Thanks in advance

2 2

CUDA Wrapper err:module:import_dl
by Seth Shelnutt June 4, 2010

June 4, 2010

Alright, I'm stumped and everyone else is too. Few years ago we did everything we are doing now and it all worked fine. Now using wine 1.2rc2 we can't get a wrapper I compiled to work. What this wrapper does is it translates/wraps the calls made to the cuda runtime dll (cudart.dll or nvcuda.dll, same file different names) and sends it to the linux library. The linux library and windows are identical except for some missing dx functions in the linux library. My sources can be found here. http://shelnutt2.host56.com/cudart/ and http://shelnutt2.host56.com/cufft/(However we aren't even getting to the second dll yet). Anytime we try to run folding at home in wine, we are getting the following. FAH checks for nvcuda.dll first because that comes with the driver installs on windows, if it doesn't find it, it defaults to cudart.dll which is packaged with fah, or can be installed separately. We have replaced all the cuda dlls with the compiled wrapper or sum linked to the compiled wrapper, just like we use to with the original cuda wrapper that we came up with. err:module:import_dll Loading library nvcuda.dll (which is needed by L"Z:\\home\\sidicas\\.FAHGPU3\\FahCore_11.exe") failed (error c0000020). err:module:import_dll Loading library cudart.dll (which is needed by L"Z:\\home\\sidicas\\.FAHGPU3\\FahCore_11.exe") failed (error c0000020). sidicas(a)Belldandy:~/.FAHGPU3$ ls -al *.dll -rw-r--r-- 1 sidicas sidicas 1617920 2010-06-03 01:48 amdcalcl.dll -rw-r--r-- 1 sidicas sidicas 2486272 2010-06-03 01:48 amdcalrt.dll -rw-r--r-- 1 sidicas sidicas 124540 2010-06-02 07:50 cudart32_30_14.dll -rw-r--r-- 1 sidicas sidicas 124540 2010-06-02 07:50 cudart.dll -rw-r--r-- 1 sidicas sidicas 82699 2010-06-01 21:39 cufft32_30_14.dll -rw-r--r-- 1 sidicas sidicas 82699 2010-06-01 21:39 cufft.dll lrwxrwxrwx 1 sidicas sidicas 10 2010-06-03 02:12 nvcuda.dll -> cudart.dll sidicas(a)Belldandy:~/.FAHGPU3$ sidicas(a)Belldandy:~/.FAHGPU3$ uname -a Linux Belldandy 2.6.26-2-amd64 #1 SMP Sun Jun 21 04:47:08 UTC 2009 x86_64 GNU/Linux sidicas(a)Belldandy:~/.FAHGPU3$ nvcc --version nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2009 NVIDIA Corporation Built on Fri_Feb_19_18:18:31_PST_2010 Cuda compilation tools, release 3.0, V0.2.1221 sidicas(a)Belldandy:~/.FAHGPU3$ ldd ./cudart.dll linux-gate.so.1 => (0xf7ee3000) libcudart.so.3 => /usr/local/cuda/lib/libcudart.so.3 (0xf7e83000) libwine.so.1 => /usr/lib/libwine.so.1 (0xf7d2d000) libm.so.6 => /lib32/libm.so.6 (0xf7d09000) libc.so.6 => /lib32/libc.so.6 (0xf7bb6000) libdl.so.2 => /lib32/libdl.so.2 (0xf7bb2000) libpthread.so.0 => /lib32/libpthread.so.0 (0xf7b9b000) librt.so.1 => /lib32/librt.so.1 (0xf7b92000) libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf7aa4000) libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf7a97000) /lib/ld-linux.so.2 (0xf7ee4000) sidicas(a)Belldandy:~/.FAHGPU3$ sidicas(a)Belldandy:~/.FAHGPU3$ ldd ./cufft.dll linux-gate.so.1 => (0xf7f29000) libcufft.so.3 => /usr/local/cuda/lib/libcufft.so.3 (0xf7308000) libwine.so.1 => /usr/lib/libwine.so.1 (0xf71b2000) libm.so.6 => /lib32/libm.so.6 (0xf718e000) libc.so.6 => /lib32/libc.so.6 (0xf703b000) libdl.so.2 => /lib32/libdl.so.2 (0xf7037000) libpthread.so.0 => /lib32/libpthread.so.0 (0xf7020000) libcudart.so.3 => /usr/local/cuda/lib/libcudart.so.3 (0xf6fdf000) libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf6ef1000) libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf6ee4000) /lib/ld-linux.so.2 (0xf7f2a000) librt.so.1 => /lib32/librt.so.1 (0xf6eda000) sidicas(a)Belldandy:~/.FAHGPU3$ sidicas(a)Belldandy:~/.FAHGPU3$ More thorugh testing has been done, http://foldingforum.org/viewtopic.php?f=54&t=14673&start=105#p146177 . When we makes reference to gpu2 wrapper, that is our original cuda wrapper designed for cuda 2.0-2.2 built couple years ago. The GPU3 wrapper is what we are having problems with. It is our cuda 3.0 wrapper. The .dll files are in the folder (we even tried in system32), ldd shows they are properly linked, yet it does not work. If we use the old wrapper compile before it works fine with cuda 2.x or with cuda 3.0 we just have to sym link the cuda lib to the old name it's expecting. I've tried compiling the old wrapper and linking it to cuda 2.3 however this fails. So I am thinking that if when I compile the old wrapper which is shown to work (when an old compiled version is used) but does not work when I compile on my funtoo box it must be some weird compiling issue. I have wine installed (without 64bit support), and I installed cuda runtime from nvidia's site as the one in portage installs to /opt/ and I wanted to make sure there wasn't any weird issues linking with that. I do get a few warnings when I compile but they aren't anything that would effect this. s.shelnutt(a)funtoo-64 ~/gpu3/wrapper/cudart $ make winegcc -c -mno-cygwin -m32 -I/usr/local/cuda/include/ -o cudart.o cudart.c In file included from /usr/local/cuda/include/cuda_runtime_api.h:53, from /usr/local/cuda/include/crt/host_runtime.h:108, from cudart.c:7: /usr/local/cuda/include/host_defines.h:57:1: warning: "__cdecl" redefined <command-line>: warning: this is the location of the previous definition cudart.c: In function 'wine_cudaGetTextureReference': cudart.c:430: warning: passing argument 1 of 'cudaGetTextureReference' from incompatible pointer type /usr/local/cuda/include/cuda_runtime_api.h:189: note: expected 'const struct textureReference **' but argument is of type 'struct textureReference **' cudart.c: In function 'wine_cudaRegisterFatBinary': cudart.c:800: warning: return makes pointer from integer without a cast cudart.c: In function 'wine_cudaUnregisterFatBinary': cudart.c:805: warning: 'return' with a value, in function returning void cudart.c: In function 'wine_cudaRegisterVar': cudart.c:810: warning: 'return' with a value, in function returning void cudart.c: In function 'wine_cudaRegisterTexture': cudart.c:815: warning: 'return' with a value, in function returning void cudart.c: In function 'wine_cudaRegisterShared': cudart.c:820: warning: 'return' with a value, in function returning void cudart.c: In function 'wine_cudaRegisterSharedVar': cudart.c:825: warning: 'return' with a value, in function returning void cudart.c: In function 'wine_cudaRegisterFunction': cudart.c:831: warning: 'return' with a value, in function returning void winegcc -shared cudart.dll.spec -mno-cygwin -o cudart.dll.so cudart.o -L/usr/local/cuda/lib/ -lcudart -lodbc32 -lole32 -loleaut32 -lwinspool -lodbccp32 -luuid If anyone has any ideas about why this doesn't work, that would be great. I've exhausted everything I could think of. Thanks, Seth Shelnutt

2 1

Re: advapi32: Fix GetSecurityInfo with NULL descriptor
by testbot＠testbot.winehq.org June 4, 2010

June 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=2467 Your paranoid android. === WNT4WSSP6 (32 bit security) === No test summary line found

1 0

Re: advapi32: Fix GetSecurityInfo with NULL descriptor (try2:typo)
by testbot＠testbot.winehq.org June 4, 2010

June 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=2466 Your paranoid android. === WNT4WSSP6 (32 bit security) === No test summary line found

1 0

Re: [PATCH 3/3] shlwapi: Implement SHSetIniStringW
by testbot＠testbot.winehq.org June 3, 2010

June 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=2454 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:604: Test failed: GetShellSecurityDescriptor should fail ordinal.c:627: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1770: Test failed: got 13 ordinal.c:1776: Test failed: got 27 ordinal.c:1791: Test failed: got 10 ordinal.c:1804: Test failed: got 13 ordinal.c:1812: Test failed: got 13 ordinal.c:1826: Test failed: got 27 ordinal.c:1834: Test failed: got 27 ordinal.c:1864: Test failed: got 22 ordinal.c:1875: Test failed: got 25 === W7PROX64 (32 bit ordinal) === ordinal.c:1776: Test failed: got 25 ordinal.c:1826: Test failed: got 25 ordinal.c:1834: Test failed: got 25 ordinal.c:1842: Test failed: got 34, length 35 ordinal.c:1853: Test failed: got 37 === W7PROX64 (64 bit ordinal) === ordinal.c:1776: Test failed: got 25 ordinal.c:1826: Test failed: got 25 ordinal.c:1834: Test failed: got 25 ordinal.c:1842: Test failed: got 34, length 35 ordinal.c:1853: Test failed: got 37

1 0

Re: [PATCH 2/3] shlwapi: Implement SHGetIniStringW
by testbot＠testbot.winehq.org June 3, 2010

June 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=2453 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:603: Test failed: GetShellSecurityDescriptor should fail ordinal.c:626: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1769: Test failed: got 13 ordinal.c:1775: Test failed: got 27 ordinal.c:1790: Test failed: got 10 ordinal.c:1803: Test failed: got 13 ordinal.c:1811: Test failed: got 13 ordinal.c:1825: Test failed: got 27 ordinal.c:1833: Test failed: got 27 ordinal.c:1863: Test failed: got 22 ordinal.c:1874: Test failed: got 25 === W7PROX64 (32 bit ordinal) === ordinal.c:1775: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 25 ordinal.c:1841: Test failed: got 34, length 35 ordinal.c:1852: Test failed: got 37 === W7PROX64 (64 bit ordinal) === ordinal.c:1775: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 25 ordinal.c:1841: Test failed: got 34, length 35 ordinal.c:1852: Test failed: got 37

1 0

Re: [PATCH 1/3] shlwapi: Be less strict on which type of IShellFolder can be enumerated
by testbot＠testbot.winehq.org June 3, 2010

June 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=2452 Your paranoid android. === W2KPROSP4 (32 bit ordinal) === ordinal.c:595: Test failed: GetShellSecurityDescriptor should fail ordinal.c:618: Test failed: returned value is not valid SD No test summary line found === W7PRO (32 bit ordinal) === ordinal.c:1767: Test failed: got 27 ordinal.c:1817: Test failed: got 27 ordinal.c:1825: Test failed: got 27 ordinal.c:1833: Test failed: got 38, length 39 ordinal.c:1844: Test failed: got 41 === W7PROX64 (32 bit ordinal) === ordinal.c:1767: Test failed: got 25 ordinal.c:1817: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 34, length 35 ordinal.c:1844: Test failed: got 37 === W7PROX64 (64 bit ordinal) === ordinal.c:1767: Test failed: got 25 ordinal.c:1817: Test failed: got 25 ordinal.c:1825: Test failed: got 25 ordinal.c:1833: Test failed: got 34, length 35 ordinal.c:1844: Test failed: got 37

1 0