November 2002 - Wine-Devel - list.winehq.org

Wine conformance tests with MSVC headers

by Vincent Béron

Hello, I tried to compile the various conformance tests with MSVC 6.0. There are two different configurations for each project: with MSVC or Wine headers. With the MSVC headers configuration, it doesn't find "wine/test.h" (since wine/include is not in the include path). Is it a known behavior? With the Wine headers configuration, I don't get those errors (but there are a bunch of warnings concerning signed/unsigned comparisons, for which I'll try to send a patch tonight). Vincent

Nov. 29, 2002

ppdebug

by Michael Sauer

since some versions of wine (actually i checked today's version out) I get the following error messages while compiling (i ignored them the last two times, assuming i want ppdebug set to 0 and patching the code that way) : gcc -g -O2 -Wall -mpreferred-stack-boundary=2 -o widl header.o proxy.o utils.o widl.o y.tab.o lex.yy.o -L../../tools/wpp -lwpp -L../../library -lwine -L../../u nicode -lwine_unicode -lfl ../../tools/wpp/libwpp.a(wpp.o)(.text+0x14b): In function `wpp_set_debug': /opt/src/build/wine/tools/wpp/wpp.c:74: undefined reference to `ppdebug' ../../tools/wpp/libwpp.a(lex.yy.o)(.text+0x3533): In function `push_buffer': /opt/src/build/wine/tools/wpp/./ppl.l:1147: undefined reference to `ppdebug' ../../tools/wpp/libwpp.a(lex.yy.o)(.text+0x38c0): In function `pop_buffer': /opt/src/build/wine/tools/wpp/./ppl.l:1232: undefined reference to `ppdebug' collect2: ld returned 1 exit status make[2]: *** [widl] Error 1 make[2]: Leaving directory `/opt/src/build/wine/tools/widl' make[1]: *** [widl] Error 2 make[1]: Leaving directory `/opt/src/build/wine/tools' make: *** [tools] Error 2 mIc P.S.: sorry if this mail reaches the list twice, but the first one i send with some private e-mail address and the list moderator will (hopefully) erase it (as he does it every time).

Nov. 29, 2002

ppdebug

by Michael Sauer

since some versions of wine (actually i checked today's version out) I get the following error messages while compiling (i ignored them the last two times, assuming i want ppdebug set to 0 and patching the code that way) : gcc -g -O2 -Wall -mpreferred-stack-boundary=2 -o widl header.o proxy.o utils.o widl.o y.tab.o lex.yy.o -L../../tools/wpp -lwpp -L../../library -lwine -L../../u nicode -lwine_unicode -lfl ../../tools/wpp/libwpp.a(wpp.o)(.text+0x14b): In function `wpp_set_debug': /opt/src/build/wine/tools/wpp/wpp.c:74: undefined reference to `ppdebug' ../../tools/wpp/libwpp.a(lex.yy.o)(.text+0x3533): In function `push_buffer': /opt/src/build/wine/tools/wpp/./ppl.l:1147: undefined reference to `ppdebug' ../../tools/wpp/libwpp.a(lex.yy.o)(.text+0x38c0): In function `pop_buffer': /opt/src/build/wine/tools/wpp/./ppl.l:1232: undefined reference to `ppdebug' collect2: ld returned 1 exit status make[2]: *** [widl] Error 1 make[2]: Leaving directory `/opt/src/build/wine/tools/widl' make[1]: *** [widl] Error 2 make[1]: Leaving directory `/opt/src/build/wine/tools' make: *** [tools] Error 2

Nov. 29, 2002

RE: msvcmaker

by Patrik Stridvall

> program/winetest doesn't exist anymore. Creating it empty is > enough for > msvcmaker to work, but is not the proper fix. I don't have the time > right now to check all the winetest references in msvcmaker > (there are > more than i thought). Working on it.

Nov. 29, 2002

Re: COM vtable inconsistencies with g++ (was SIGSEGV in IDirectDrawImpl_EnumDisplayModes)

by Dan Kegel

Sylvain wrote: >> Thanks! >> It works fine with the version 2.96 I use. > Do you know RedHat's gcc 2.96 has SERIOUS bugs and that its support has > been totally dropped ? Support has been dropped by whom? Not Red Hat; they are still releasing updates for gcc-2.96-RH. The latest was 18 days ago, https://rhn.redhat.com/errata/RHBA-2002-200.html > It's update time. I agree, gcc 3.2[.1] is a better choice than gcc-2.96-RH these days. It is very close to compliance with the C++ ABI, and it's an official Gnu release rather than a vendor snapshot. (I'm building wine for the first time with gcc3.2 today, I hope I'm right about it being a better choice :-) - Dan

Nov. 29, 2002

msvcmaker

by Vincent Béron

Hi all, program/winetest doesn't exist anymore. Creating it empty is enough for msvcmaker to work, but is not the proper fix. I don't have the time right now to check all the winetest references in msvcmaker (there are more than i thought). Vincent

Nov. 29, 2002

RE: Janitorial Projects

by Patrik Stridvall

> What we need next: > 1. a way to run all tests. A batch file would do the job nicely. > Patrik, can that be added to msvcmaker? Planned but not done. However, since you asked for it, I will look into it right away.

Nov. 29, 2002

RE: Winapi_check warnings

by Patrik Stridvall

> On November 29, 2002 01:53 pm, Patrik Stridvall wrote: > > Not really, you haven't run ./configure on that tree have you? > > winapi_check assumes that this is done, but I can fix it if > > it irritates you. > > Oh, I have separate src/build trees, and I was running it in > the source tree. In fact, I _have_ to run it in the source > tree, and then I get the errors... OK. I will fix winapi_check to support that.

Nov. 29, 2002

Re: Janitorial Projects

by Dustin Navea

----- Original Message ----- From: "Francois Gouget" <fgouget(a)free.fr> To: "Dimitrie O. Paun" <dpaun(a)rogers.com> Cc: "Wine Devel" <wine-devel(a)winehq.com> Sent: Friday, November 29, 2002 2:06 PM Subject: Re: Janitorial Projects > > Here's a proposed addition to the Janitorial projects: > > Fix the conformance tests wo that they pass on Windows!!! > > > Rationale: Running just the kernel tests on NT4 I could not help bu > notice that: > * drive crashed and then was would not run unattended and then had many > failures > * environ crashed and then had many failures > * file has one failure > * path has 133 failures! > * process has 4 failures > > Testing on Windows 98 also yielded a crash for environ, followed with 20 > failures, followed with failures for pretty much every Unicode test out > there. > > So according to our tests Windows 98 and NT4 do not conform to the > Windows behavior! > > In other words many of our tests are plain incorrect. I strongly suspect > they were written and tested with Wine and never run on Windows > (actually when I tried compiling them some time ago most of them would > not even compile). > > Now we have a way to pretty easily compile them on Windows. Here's the > procedure: > > * get the Wine source > * run ./tools/winapi/msvcmaker --no-wine > (it's a perl script so you might even be able to do it on Windows) > * make those source accessible by a Windows machine (e.g. export them > via Samba) > * load winetest.dsw in Visual C++ > * hit that build button > > What we need next: > 1. a way to run all tests. A batch file would do the job nicely. > Patrik, can that be added to msvcmaker? > 2. people to fix the tests so that they actually pass on *all* Windows > platforms > 3. volunteers who will run the tests their Windows platform of choice > on a regular basis so that we quickly fix incorrect tests > > The people doing 2 could definitely use the help of a couple of people > doing 3 since they will probably not have access to all Windows > platforms. > > Once the initial fixing is done we will really need people doing 3 to > prevent bad tests from comming back. > Are we going to divide this up by Major (Win98/NT4/2k) or Major and Minor (SP1, SR1, SE, etc)? I can volunteer for Win2k (SP3 if Major and Minor) -Dustin P.S. If needed I could probably find some free space or an old drive to install Win98 Regular on and run some tests...

Nov. 29, 2002

Re: Janitorial Projects

by Francois Gouget

Here's a proposed addition to the Janitorial projects: Fix the conformance tests wo that they pass on Windows!!! Rationale: Running just the kernel tests on NT4 I could not help bu notice that: * drive crashed and then was would not run unattended and then had many failures * environ crashed and then had many failures * file has one failure * path has 133 failures! * process has 4 failures Testing on Windows 98 also yielded a crash for environ, followed with 20 failures, followed with failures for pretty much every Unicode test out there. So according to our tests Windows 98 and NT4 do not conform to the Windows behavior! In other words many of our tests are plain incorrect. I strongly suspect they were written and tested with Wine and never run on Windows (actually when I tried compiling them some time ago most of them would not even compile). Now we have a way to pretty easily compile them on Windows. Here's the procedure: * get the Wine source * run ./tools/winapi/msvcmaker --no-wine (it's a perl script so you might even be able to do it on Windows) * make those source accessible by a Windows machine (e.g. export them via Samba) * load winetest.dsw in Visual C++ * hit that build button What we need next: 1. a way to run all tests. A batch file would do the job nicely. Patrik, can that be added to msvcmaker? 2. people to fix the tests so that they actually pass on *all* Windows platforms 3. volunteers who will run the tests their Windows platform of choice on a regular basis so that we quickly fix incorrect tests The people doing 2 could definitely use the help of a couple of people doing 3 since they will probably not have access to all Windows platforms. Once the initial fixing is done we will really need people doing 3 to prevent bad tests from comming back. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ f u kn rd ts, ur wy 2 gky 4 ur wn gd.

Nov. 29, 2002