- wine-devel - winehq.org

winmm:wave testing
by Jakob Eriksson 04 Nov '04

04 Nov '04

How should this be handled, is this a buggy driver? http://test.winehq.org/data/200411021000/2000_BennyGoemans/winmm:wave.txt wave.c:998:found 1 WaveOut devices wave.c:664: 0: "SB PCI" (\\?\pci#ven_1274&dev_1371&subsys_13711274&rev_08#3&61aaa01&0&68#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave) 5.0 (1:100) wave.c:667: channels=65535 formats=00fff support=002c wave.c:669: WAVECAPS_VOLUME WAVECAPS_LRVOLUME WAVECAPS_SAMPLEACCURATE wave.c:524:Playing 1 second silence at 22050x 8x1 WAVE_FORMAT_PCM wave.c:420:waveOutGetPosition(0): TIME_MS not supported, returned TIME_SAMPLES wave.c:443:waveOutGetPosition(0): TIME_SMPTE not supported, returned TIME_SAMPLES wave.c:549: Test failed: The sound played for 1342 ms instead of 1000 ms

1 0

Wine dll testing state of affairs
by Jakob Eriksson 04 Nov '04

04 Nov '04

I looked around in the Wine dlls tree to see how many dlls had a "tests" directory in them. Quite a few had, but these did not: Just thought it could be interesting to see. . ./advpack ./amstream ./atl ./avicap32 ./avifil32 ./cabinet ./capi2032 ./cards ./cfgmgr32 ./comcat ./commdlg ./crtdll ./crypt32 ./ctl3d ./d3d8 ./d3d9 ./d3dim ./d3drm ./d3dx8 ./d3dxof ./dbghelp ./dciman32 ./devenum ./dinput ./dinput8 ./dmband ./dmcompos ./dmime ./dmloader ./dmscript ./dmstyle ./dmsynth ./dmusic ./dmusic32 ./dplay ./dplayx ./dpnet ./dpnhpast ./dswave ./dxdiagn ./dxerr8 ./dxerr9 ./dxguid ./glu32 ./glut32 ./hhctrl.ocx ./iccvid ./icmp ./ifsmgr.vxd ./imagehlp ./imm32 ./itss ./lzexpand ./mmdevldr.vxd ./monodebg.vxd ./mpr ./msdmo ./mshtml ./msi ./msimg32 ./msisys ./msnet32 ./msrle32 ./msvcrt20 ./msvcrt40 ./msvidc32 ./msvideo ./mswsock ./newdev ./odbc32 ./oleacc ./olecli ./oledlg ./olepro32 ./olesvr ./opengl32 ./qcap ./rasapi32 ./richedit ./secur32 ./serialui ./setupapi ./shdocvw ./shfolder ./snmpapi ./sti ./strmiids ./tapi32 ./ttydrv ./twain ./unicows ./url ./uuid ./uxtheme ./vdhcp.vxd ./vdmdbg ./vmm.vxd ./vnbt.vxd ./vnetbios.vxd ./vtdapi.vxd ./vwin32.vxd ./win32s ./winaspi ./wined3d ./winedos ./wineps ./winnls ./wintab32 ./wintrust ./wow32 ./wsock32 ./x11drv These have tests: ./advapi32/tests ./comctl32/tests ./ddraw/tests ./dsound/tests ./gdi/tests ./iphlpapi/tests ./kernel/tests ./mapi32/tests ./mlang/tests ./msacm/tests ./mscms/tests ./msvcrt/tests ./msvcrtd/tests ./netapi32/tests ./ntdll/tests ./ole32/tests ./oleaut32/tests ./psapi/tests ./quartz/tests ./rpcrt4/tests ./rsabase/tests ./shell32/tests ./shlwapi/tests ./urlmon/tests ./user/tests ./version/tests ./wininet/tests ./winmm/tests ./winsock/tests ./winspool/tests

1 0

Update region patch
by Alexandre Julliard 04 Nov '04

04 Nov '04

Here's the first step of moving the update region management to the server. The refresh on window moves is not optimized yet, so it will probably flicker quite a bit, but things should still be painted properly in the end. If you feel like giving this a try, I'm interested in hearing about any case where things don't repaint correctly. -- Alexandre Julliard julliard(a)winehq.org

3 3

Re: Some conformance tests for msvcrt printf functions
by Aneurin Price 04 Nov '04

04 Nov '04

Is there any particular reason this patch hasn't been committed? Something wrong or just overlooked?

2 1

Access Tokens and Threads
by Elad Lahav 03 Nov '04

03 Nov '04

I've been looking into the annoying "Set ThreadImpersonationToken handle" messages. In order to fix this issue, I need to know a few things: 1. Does Wine maintain access tokens at all? It seems that most of the relevant functions (e.g., NtQueryInformationThread and NtSetInformationThread) simply ignore it. 2. It looks like the thread's token is a part of the so-called "security descriptor" member of the thread's SECURITY_ATTRIBUTES structure. Does anyone know what structure this descriptor points to? Elad

2 1

source level debugging with WineLib?
by Geoff K. Hart 03 Nov '04

03 Nov '04

Hello, We just started using WineLib, and have very basic question: which -g??? option do you use to do source level debugging with winedbg? I searched the documentation and mailing list for any step-by-step about this, but found nothing. So either the answer is so obvious that I just can't see it - or it doesn't work? By default, winemaker seems configure things for no debug - so I edited one Makefile manually, and added -g. Winedbg can attach to the process, and can even show the stack - but didn't know much beyond that. I tried all the -g variants that I could find, but only -gstabs and -gstabs+ seemed to help. They allowed the debugger to find the correct place in the source, and "whatis" seemed to work - however, if I tried to dereference something, it complained about "no type ...", like this: Wine-dbg>info process pid threads parent executable (all id:s are in hex) 00000008 3 00000000 'Z:\home\s\src\SysSrv \DataDistributionService\DDSServer2\ddsserver2.exe' Wine-dbg>attach 8 In 32 bit mode. 0x546387a2: ret Wine-dbg>bt Backtrace: =>1 0x546387a2 (0x10252c50) 2 0x48714a7e NTDLL_wait_for_multiple_objects+0x12e in ntdll (0x10252cf8) 3 0x48712fec vm86_return_end+0xc55 in ntdll (0x10252d1c) 4 0x1000b808 (0x10352d64) 5 0x48714a7e NTDLL_wait_for_multiple_objects+0x12e in ntdll (0x10352e0c) 6 0x48714afc NtWaitForMultipleObjects+0x6c in ntdll (0x10352e30) 7 0x61e57a95 WaitForMultipleObjectsEx+0xb5 in kernel32 (0x10352f60) 8 0x61e5797b WaitForSingleObjectEx+0x3b in kernel32 (0x10352f80) 9 0x1002878afixme:dbghelp:elf_new_wine_thunks Duplicate in ddsserver2<elf>: _ZZ17BroadCastIdentityPvmmE22lRepCntrClientDeletion<10037720-00000004> lRepCntrClientDeletion<10037720-00000000> fixme:dbghelp:elf_new_wine_thunks Duplicate in ddsserver2<elf>: _ZZ17BroadCastIdentityPvmmE20lRepKeepAliveCounter<10037724-00000004> lRepKeepAliveCounter<10037724-00000000> fixme:dbghelp:elf_new_wine_thunks Duplicate in ddsserver2<elf>: _ZZ17BroadCastIdentityPvmmE17lRepCntrBroadcast<1003771c-00000004> lRepCntrBroadcast<1003771c-00000000> _Z13DDSServerMainPv+0x88(lpParameter=0x44c47098) [/home/s/src/SysSrv/ DataDistributionService/DDSServer2/AcceptSocket.cpp:220] in ddsserver2 (0x10353150) 10 0x61e5eeda (0x10353228) 11 0x48716523 (0x10353a78) 12 0x1000508d (0x10353b0c) 13 0x660d255a (0x00000000) Wine-dbg>up 8 220 dwRetVal = ::WaitForSingleObjectEx (pServer- >m_hStopEvent, INFINITE, TRUE); Wine-dbg>p pServer 0x44c47098 Wine-dbg>p *pServer No type or type mismatch Wine-dbg>whatis pServer struct DDSServer* Wine-dbg> Any help? Geoff

5 4

Re: InternetGetConnectedStateExA
by Alexandre Julliard 03 Nov '04

03 Nov '04

Aric Stewart <aric(a)codeweavers.com> writes: > +BOOL WINAPI InternetGetConnectedStateExA(LPDWORD lpdwStatus, > + LPSTR lpszConnectionName, DWORD dwNameLen, DWORD dwReserved) > +{ > + INT len; > + LPWSTR lpwszConnectionName = NULL; > + BOOL rc; > + > + TRACE("(%p, %s, %ld, 0x%08lx)\n", lpdwStatus, debugstr_a(lpszConnectionName), dwNameLen, dwReserved); > + > + if (lpszConnectionName) > + { > + len = MultiByteToWideChar(CP_ACP, 0, lpszConnectionName, -1, NULL, 0); > + lpwszConnectionName= HeapAlloc(GetProcessHeap(), 0, len*sizeof(WCHAR)); > + MultiByteToWideChar(CP_ACP, 0, lpszConnectionName, -1, > + lpwszConnectionName, len); > + } > + > + rc = InternetGetConnectedStateExW(lpdwStatus,lpwszConnectionName, dwNameLen, lpszConnectionName is an output parameter, it should be converted on return from the W call. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: WINSOCK: Implement WSAAddressToStringA/W
by Alexandre Julliard 03 Nov '04

03 Nov '04

Hans Leidekker <hans(a)it.vu.nl> writes: > + if (stringW) > + { > + ret = WSAAddressToStringW( sockaddr, len, NULL, stringW, &lenstrW ); > + *lenstr = lenstrW / sizeof(WCHAR); To be really correct you have to use WideCharToMultiByte to compute the ASCII length. Though in this case it would probably be easier to just duplicate the code and do a simple sprintf in the A function instead of trying to call the W function. -- Alexandre Julliard julliard(a)winehq.org

1 0

compiling wine with msvc
by James Hawkins 03 Nov '04

03 Nov '04

I'm trying to get the wine tests to compile under msvc, so I ran msvcmaker in the wine source under cygwin (which was successful). Then I opened the winetest project and did a 'rebuild all'. When it tries to compile advapi32_test/security.c I get an warning and 102 errors: C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\rpc.h(89) : warning C4005: 'RPCRTAPI' : macro redefinition ..\..\..\include\rpc.h(45) : see previous definition of 'RPCRTAPI' :\Program Files\Microsoft Visual Studio\VC98\INCLUDE\rpcnsi.h(37) : error C2143: syntax error : missing ')' before 'type' C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\rpcnsi.h(37) : error C2491: 'RpcNsBindingExportA' : definition of dllimport function not allowed ......etc I'm pretty sure the problem is that the the msvc's rpc.h and rpcnsi.h files are being included when they shouldn't. Is that about right? If so, what could be a possible solution? BTW I'm compiling with MSVC++ 6.0. wine cvs from 11-01-2004. -- James Hawkins

3 6

Re: Fix for metafile test
by Dmitry Timoshkov 03 Nov '04

03 Nov '04

"Jakob Eriksson" <jakov(a)vmlinux.org> wrote: > Seems the test fails in non-interactive mode without this patch. No, the problem seems to be related to a window's visibility. Windows does not play EMF records if the DC was created for a not visible window. A lot of other tests fail due to exactly that problem: user32/win.c and user32/msg.c are the examples. The question is what makes the tests create invisible windows? Does winetest run as a service on a not visible desktop? Anything else? -- Dmitry.

4 5

Re: The Return of IE6 Problems
by Mike Hearn 03 Nov '04

03 Nov '04

> The common denominator for this situation is that these patches modified > some of the same files. Patch 13475 implemented itss.dll and modified > wine/dlls/Makefile.in, wine/configure.ac and wine/configure. A partial > implementation of advpack.RegInstall, Patch 13938 also modified > wine/dlls/Makefile.in, wine/configure.ac and wine/configure in addition > to adding /wine/dlls/advpack/reg.c. Although IE6 would still > initialize, patch 13937 added advpack to the repository. Hi Dan, Great work on the regression search! This is exactly the sort of information we need. ITSS was implemented by Mike - as it's a component of IE I guess it should at least work with it so I'm CCing him. It may be that he implemented it for some other app rather than IE and he doesn't have time to bring it up to scratch for IE right now. I'm not sure. The second patch suggests that we got RegInstall wrong. That needs to be fixed, but for now you can probably get IE back to a working state again by overriding both these DLLs as native (itss, advpack). If you look at the script I wrote back in January, quite a lot of what it does is simply overriding various incomplete DLLs. I no longer maintain that script (buy CrossOver! :) but if you want to take over maintenance by all means do so, I'd be happy to help you get up to speed. thanks -mike

2 1

RE: Test Drive failure
by Dagan Shai 03 Nov '04

03 Nov '04

This results in a helloworld executable. When I execute it I get lots of output lines, here's a sample: fixme:ttydrv:TTYDRV_GetBitmapBits (0x3bc, 0x77cafa7c, 32): stub fixme:ttydrv:TTYDRV_GetBitmapBits (0x3b8, 0x77cafa9c, 32): stub err:imagelist:ImageList_ReplaceIcon no color! fixme:ttydrv:TTYDRV_DC_StretchBlt (0x94, 288, 0, 16, 16, 0x3c4, 0, 0, 16, 32, 13 369376): stub fixme:ttydrv:TTYDRV_DC_StretchBlt (0x98, 288, 0, 16, 16, 0x3c4, 0, 0, 16, 32, 13 369376): stub fixme:ttydrv:TTYDRV_GetBitmapBits (0x3cc, 0x77cafa7c, 128): stub fixme:ttydrv:TTYDRV_GetBitmapBits (0x3c8, 0x77cafafc, 128): stub err:imagelist:ImageList_ReplaceIcon no color! fixme:ttydrv:TTYDRV_DC_StretchBlt (0xb0, 576, 0, 32, 32, 0x3d4, 0, 0, 32, 64, 13 369376): stub fixme:ttydrv:TTYDRV_DC_StretchBlt (0xb4, 576, 0, 32, 32, 0x3d4, 0, 0, 32, 64, 13 369376): stub These are all functions that helloworld does not use, so I don't understand the problem here. Regards, Shai Dagan -----Original Message----- From: Dimitrie O. Paun [mailto:dpaun@rogers.com] Sent: Tuesday, November 02, 2004 6:57 PM To: Dagan Shai Cc: Dimitrie O. Paun; wine-devel(a)winehq.org Subject: Re: Test Drive failure On Tue, Nov 02, 2004 at 06:40:57PM +0200, Dagan Shai wrote: > Thanks. > > Here they are. Winemaker is buggy, the generated Makefile has a small problem. Here's the fix: --- Makefile.orig 2004-11-02 09:52:59.000000000 -0500 +++ Makefile 2004-11-02 11:52:57.451738280 -0500 @@ -58,7 +58,7 @@ ### Generic targets -all: $(SUBDIRS) $(DLLS:%=%.so) $(EXES:%=%.so) +all: $(SUBDIRS) $(DLLS:%=%.so) $(EXES) ### Build rules @@ -106,7 +106,7 @@ $(helloworld_exe_MODULE).dbg.c: $(helloworld_exe_C_SRCS) $(helloworld_exe_CXX_SRCS) $(WINEBUILD) -o $@ --debug -C$(SRCDIR) $(helloworld_exe_C_SRCS) $(helloworld_exe_CXX_SRCS) -$(helloworld_exe_MODULE).so: $(helloworld_exe_MODULE).dbg.o $(helloworld_exe_OBJS) +$(helloworld_exe_MODULE): $(helloworld_exe_MODULE).dbg.o $(helloworld_exe_OBJS) $(CXX) $(helloworld_exe_LDFLAGS) -o $@ $(helloworld_exe_OBJS) $(helloworld_exe_MODULE).dbg.o $(helloworld_exe_LIBRARY_PATH) $(LIBRARY_PATH) $(helloworld_exe_DLLS:%=-l%) $(helloworld_exe_LIBRARIES:%=-l%) -- Dimi. ______________________________________________________________________ This email message has been scanned by PineApp Mail-Secure and has been found clean.

1 0

Re: EnumDateFormatsA: Add ru_RU locale and default DATE format
by Dmitry Timoshkov 03 Nov '04

03 Nov '04

"Vitaly Lipatov" <lav(a)etersoft.ru> wrote: > Changelog: > EnumDateFormatsA: > - Add ru_RU locale (0x419) That's a completely broken implementation, please do not extend it. It should retrieve the data from the kernel32 locale database (have a look at dlls/kernel/nls). > - Use DATE_SHORTDATE when dwFlags is 0 > - Ignore LOCALE_USE_CP_ACP bit in dwFlags (I can't find a difference in > Windows behavior with this flag) It would be nice to see a test case for that. Also please use a common indent 4 spaces as (almost) everywhere in Wine. -- Dmitry.

2 2

dinput - mouse
by Vitaliy Margolen 03 Nov '04

03 Nov '04

Is there are anyone working on it? It seems like there are some strange problem with mouse input, and I can't find it! I trying to get Descent 3 running. So far so good. It installs, and runs. But mouse does not work. It's not like it doesn't work at all. It does, but it moves erratically and mostly left-right. Could it be that it can't switch to full screen mode and fails because of it? Dome could be downloaded from here: http://www.descent3.com/4_downloads.html#d3_demos P.S. I know there is Linux version of it. Too bad I don't have it. It cost $$ and have to by purchased separately. Vitaliy Here is what dinput log looks like: trace:dinput:dinput_mouse_hook msg 200 pt 320 240 (W=0) trace:dinput:dinput_mouse_hook (X: 0 - Y: 0 L: 00 M: 00 R: 00) trace:dinput:dinput_mouse_hook msg 200 pt 320 240 (W=0) trace:dinput:dinput_mouse_hook (X: 0 - Y: 0 L: 00 M: 00 R: 00) trace:dinput:dinput_mouse_hook queueing -2 at offset 0 (queue head 46 / size 64) trace:dinput:dinput_mouse_hook queueing 8 at offset 4 (queue head 47 / size 64) trace:dinput:dinput_mouse_hook msg 200 pt 318 248 (W=1) trace:dinput:dinput_mouse_hook (X: -2 - Y: 8 L: 00 M: 00 R: 00) trace:dinput:dinput_mouse_hook queueing -2 at offset 0 (queue head 48 / size 64) trace:dinput:dinput_mouse_hook queueing 6 at offset 4 (queue head 49 / size 64) trace:dinput:dinput_mouse_hook msg 200 pt 316 254 (W=1) trace:dinput:dinput_mouse_hook (X: -4 - Y: 14 L: 00 M: 00 R: 00) trace:dinput:dinput_mouse_hook queueing -2 at offset 0 (queue head 50 / size 64) trace:dinput:dinput_mouse_hook queueing 6 at offset 4 (queue head 51 / size 64) trace:dinput:dinput_mouse_hook msg 200 pt 314 260 (W=1) trace:dinput:dinput_mouse_hook (X: -6 - Y: 20 L: 00 M: 00 R: 00) trace:dinput:dinput_mouse_hook queueing -2 at offset 0 (queue head 52 / size 64) trace:dinput:dinput_mouse_hook queueing 8 at offset 4 (queue head 53 / size 64) trace:dinput:dinput_mouse_hook msg 200 pt 312 268 (W=1) trace:dinput:dinput_mouse_hook (X: -8 - Y: 28 L: 00 M: 00 R: 00) trace:msg:MSG_peek_message got type 7 msg 200 (WM_MOUSEMOVE) hwnd 0x10022 wp 0 lp 0 trace:dinput:SysMouseAImpl_GetDeviceData (0x4036bd48)->(dods=16,entries=64,fl=0x00000000) trace:dinput:SysMouseAImpl_GetDeviceData Application retrieving 12 event(s). trace:dinput:SysMouseAImpl_GetDeviceData Warping mouse to 320 - 240

1 0

WSARecv not calling CompletionRoutine on socket close
by Geoff K. Hart 02 Nov '04

02 Nov '04

I've tried to search the mailing list archives (is their a searchable archive someplace?) for some reference to this problem. but found none. Forgive me if I didn't search hard enough. The Problem: we register a callback (lpCompletionRoutine) in our WSARecv call. This callback works fine for normal incoming messages. However, on socketclose, it does NOT get called. This behavior doesn't match what we see on Windows. Is there some configuration option we are missing? We see this same behavior for .exe's built on Windows and run under Wine - and with source code brought to Linux and built with WineLib. thanks, Geoff

1 0

[shellpath.c]: minor fix to Rolf's patch
by Rolf Kalbermatter 02 Nov '04

02 Nov '04

<menard.fabrice(a)wanadoo.fr> wrote: >The latest patch from Rolf Kalbermatter on shellpath.c was breaking the installation of wine.inf. > > wine rundll32 setupapi.dll,InstallHinfSection DefaultInstall 128 d:\\wine.inf > >was returning errors about being unable to create some dirs. In facts these errors was concerning >already existing directories in SHGetFolderPathW. I believe this patch is not fully correct. I noticed these errors too after the patch was applied, but did a little more investigation. SHCreateDirectoryEx should never be called if the directory already exists since this is explicitedly tested before the call to the function with PathFileExistsW(). Also inside the SHCreateDirectoryEx function I saw that the first call to CreateDirectory fails since intermediate directories are missing and then in the recursive call to CreateDirectory every single call returns ERROR_ALREAY_EXISTS on my system in spite of that it actually creates the last two or three directories in there. My investigations showed that in spite of that some of the the top level directories do not exist, the function NtCreateFile() which is ultimately called does seem to return an according NT status when called from SHGetFolderPath() but does create the directory nevertheless. Strange thing is that I can't reproduce this behaviour when calling SHCreateDirectoryEx() with many different parameters from an extended test in tests/shfileop.c So I believe the root cause really seems somewhere else, namely NTCreateFile or maybe wineserver itself, but I hadn't time to further go into details. >I think it is not necessary to care about that in this function so I added a check on the >type of error returned by SHCreateDirectoryExW. ShCreateDirectory should fail with that error if the directory really already existed. Rolf Kalbermatter

2 2

Can't debug mingw compiled program
by Vitaly Lipatov 02 Nov '04

02 Nov '04

During program debugging I have some trouble with winedbg use. Simple test program with error on write access to constant: #include <string.h> int main(int argc, char **argv) { char * str = "test"; _strupr(str); return (0); } I try debug it: $ winedbg 3.exe Can't attach process 3: error 87 WineDbg starting on pid 0xa In 32 bit mode. Wine-dbg>c First chance exception: page fault on write access to 0x00404000 in 32-bit code (0x00935d20). ... Backtrace: =>1 0x00935d20 _memccpy+0x595 in msvcrt (0x0090fec8) 2 0x00401330wine-kthread: stabs.c:246: stabs_find_ref: Assertion `filenr <= cu_include_stk_idx' failed. I see some bug in stubs handling. Versions: i386-mingw32msvc-gcc-3.3.3 wine from last CVS Any suggestions? -- Vitaly Lipatov, ALT Linux Team Russia, Saint-Petersburg, www.etersoft.ru

2 1

RFC: yield on Waits
by Jeremy White 02 Nov '04

02 Nov '04

Hi folks, Due to my new found belief that all of the flaws in Wine are timing problems, I have found what appears to be a gaping hole in Wine's timing behavior. Specifically, it appears as though any style of Waitxxx is supposed to yield the processor. This seems a bit difficult for me to believe, even though we had earlier discovered that Wine was never yielding on a Sleep(0). I've attached the test program I used to discover this. If you run sleep2 -1 0w the program will start 2 threads, one which spin loops (-1), and one which does a wait on an object for 0 seconds. You'll see in the results that the Wait(...,0) thread gets far fewer loops, and thus must be yielding. Further, changing that to a 0ws (or even 5ws), which means we're waiting on a signalled object, doesn't change the behavior. This leads me to suggest the attached patch. I would appreciate review from other folks, because this seems like a drastic change to me, and it strikes me as equally likely that I've done something stupid. Cheers, Jeremy

1 1

Re: Test Drive failure
by Dimitrie O. Paun 02 Nov '04

02 Nov '04

On Tue, Nov 02, 2004 at 06:40:57PM +0200, Dagan Shai wrote: > Thanks. > > Here they are. Winemaker is buggy, the generated Makefile has a small problem. Here's the fix: --- Makefile.orig 2004-11-02 09:52:59.000000000 -0500 +++ Makefile 2004-11-02 11:52:57.451738280 -0500 @@ -58,7 +58,7 @@ ### Generic targets -all: $(SUBDIRS) $(DLLS:%=%.so) $(EXES:%=%.so) +all: $(SUBDIRS) $(DLLS:%=%.so) $(EXES) ### Build rules @@ -106,7 +106,7 @@ $(helloworld_exe_MODULE).dbg.c: $(helloworld_exe_C_SRCS) $(helloworld_exe_CXX_SRCS) $(WINEBUILD) -o $@ --debug -C$(SRCDIR) $(helloworld_exe_C_SRCS) $(helloworld_exe_CXX_SRCS) -$(helloworld_exe_MODULE).so: $(helloworld_exe_MODULE).dbg.o $(helloworld_exe_OBJS) +$(helloworld_exe_MODULE): $(helloworld_exe_MODULE).dbg.o $(helloworld_exe_OBJS) $(CXX) $(helloworld_exe_LDFLAGS) -o $@ $(helloworld_exe_OBJS) $(helloworld_exe_MODULE).dbg.o $(helloworld_exe_LIBRARY_PATH) $(LIBRARY_PATH) $(helloworld_exe_DLLS:%=-l%) $(helloworld_exe_LIBRARIES:%=-l%) -- Dimi.

1 0

Correct time stamps on x11 events
by Jeremy White 02 Nov '04

02 Nov '04

Log message: Fix x11 event timing so that we correctly correlate x11 timing and Wine timing and dynamically adjust it as we go.

1 0

RE: Test Drive failure
by Dagan Shai 02 Nov '04

02 Nov '04

It only generated the helloworld.exe.so file, and no others. This is the only file defined in the makefile generated by winemaker. It is listed as part of the EXES macro and not the DLLS, which is why I thought it to be an executable. Could there be some reason that no executable is generated? Shai Dagan -----Original Message----- From: Dimitrie O. Paun [mailto:dpaun@rogers.com] Sent: Tuesday, November 02, 2004 6:14 PM To: Dagan Shai Cc: wine-devel(a)winehq.org Subject: Re: Test Drive failure On Tue, Nov 02, 2004 at 05:53:11PM +0200, Dagan Shai wrote: > Hi, > I'm new to WINELIB. As a test drive I tried to port the Hello World > application, just to see that the environment is functioning. > I called: > winemaker --console --lower-uppercase . > In the source directory. Then I called: > make > A helloworld.exe.so file was successfully created as a result (no errors > or warnings). It should have also generated a helloworld executable file, and you should be running it as: # ./helloworld -- Dimi. ______________________________________________________________________ This email message has been scanned by PineApp Mail-Secure and has been found clean.

3 2

Re: Fix for metafile test
by Juan Lang 02 Nov '04

02 Nov '04

Dmitry wrote: > The question is what makes the tests create invisible windows? Does > winetest run as a service on a not visible desktop? Anything else? I believe this is the reason. The shellpath tests fail on WinXP, I believe because HKCU doesn't exist because the service doesn't interact with the desktop. --Juan __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

1 0

Re: COM / InstallShield status
by Mike Hearn 02 Nov '04

02 Nov '04

> Likewise, what's the current status of Installshield support, > and how much work would it be to fully support > Installshield-based installers? I don't see any > open Installshield bug reports, maybe I should file > one against the apps I have that don't install at > the moment. (Or would that be overkill?) Rob and I did some work on InstallShield for iTunes a few months ago, since then AFAIK no work has been done. Status back then was that the InstallShield 7/MSI hybrid installers worked pretty well, the bug I chased for nearly a week was refcounting related (the backend wasn't shutting down) and since that was fixed I believe it works pretty well. The other main problems I'm aware of are: - needs stdole32.tlb, we have a program to generate this in CrossOver and it needs to be pulled upstream as previously discussed. - Painting problems. I've not investigated this deeply but I'm 99% sure I know what the problem is. I've even written a patch to fix it as part of investigating iTunes, but I never tried the patch with an InstallShield that shows the issue. Apart from those two there are mostly just generic issues - InstallShield contains its own scripting language which heavily exercises the variant APIs, so it sometimes shows up problems with them. I believe Marcus found an issue with them thanks to InstallShield recently. In other words, InstallShield *should* work though it might not be pretty. There may be installers out there which don't work, I'd like to start nailing them once I get back to Wine hacking. I don't know if I'll get time however. Also, Murphy continues to smack me down w.r.t internet connection, the ISP sent me the wrong type of modem and yesterday I discovered the phone socket I was going to connect the modem to doesn't actually work :( thanks -mike

1 0

Re: wineps: better pattern brushes
by Jakob Eriksson 02 Nov '04

02 Nov '04

Isn't 300 a bit low? Almost all lasers do 600 dpi. Huw D M Davies wrote: > Huw Davies <huw(a)codeweavers.com> > Scale the patterns so that they're rendered at 300dpi > Create the image dictionary once, rather than every time the PaintProc > is called - should speed printing up somewhat. > > >

2 1

Test Drive failure
by Dagan Shai 02 Nov '04

02 Nov '04

Hi, I'm new to WINELIB. As a test drive I tried to port the Hello World application, just to see that the environment is functioning. I called: winemaker --console --lower-uppercase . In the source directory. Then I called: make A helloworld.exe.so file was successfully created as a result (no errors or warnings). However, when I execute this file I immediately get a segmentation fault. I tried to run it using gdb, in order to figure out what happens, and I get: Program received signal SIGSEGV, Segmentation fault. 0x00000001 in ?? () I'm sure I'm missing something simple. Can someone please point me in the right direction? Thanks, Shai Dagan

2 1

The Return of IE6 Problems
by Dan McGhee 02 Nov '04

02 Nov '04

Hopefully, this time I have generated more specific and relevant information. I have done regressions to identify the patches that may be causing the symptoms. I have duplicated these results by using ./tools/wineinstall, make && make depends and wineprefixcreate. Although I was not able to get the help engine functional, I duplicated the IE6 not running symptom by installing IE6 manually. Additionally these symptoms are current as of a wine compiled from cvs the morning of October 30, 2004. Statement of symptoms: 1. Until the commit of 20040824 16:00:16 CDT, patch 13475, IE6, when installed using Mike Hearn's script ran and the help engine was functional. After the patch, the help engine was not functional. 2. With the commit of 20040927 15:39:42 CDT, patch 13938, IE6, installed using the script or manually, would not initialize. If I substitute system.reg and user.reg from a version of wine compiled before patch 13475 for the files of the same names in a version of wine compiled from cvs updated on the morning of 20041030, IE6 runs and the help engine is functional. The common denominator for this situation is that these patches modified some of the same files. Patch 13475 implemented itss.dll and modified wine/dlls/Makefile.in, wine/configure.ac and wine/configure. A partial implementation of advpack.RegInstall, Patch 13938 also modified wine/dlls/Makefile.in, wine/configure.ac and wine/configure in addition to adding /wine/dlls/advpack/reg.c. Although IE6 would still initialize, patch 13937 added advpack to the repository. I do not have the ability to read the changes and try to interpret them. I can only supply information that I think is relevant or for which someone specifically asks me. I have logs of installing and running IE6 before and after the patches. I have the system.reg and user.reg files also. In addtion I have diff files of the befores and afters. This is the difference between system.reg-before-patch-13475 and system.reg-after-patch-13938. This file was "egrepped" for itss|advpack: > -@="C:\\windows\\system\\itss.dll" > -@="C:\\windows\\system\\itss.dll" > -@="C:\\windows\\system\\itss.dll" > -@="C:\\windows\\system\\itss.dll" > -@="C:\\windows\\system\\itss.dll,0" > "StubPath"="rundll32.exe advpack.dll,LaunchINFSectionEx > c:\\windows\\inf\\icw.inf,PerUserStub,,36" > +"050"="rundll32.exe advpack.dll,DelNodeRunDLL32 > c:\\windows\\system\\dacui.dll" > +"054"="rundll32.exe advpack.dll,DelNodeRunDLL32 > c:\\windows\\Catroot\\icatalog.mdb" > "000"="rundll32.exe advpack.dll,LaunchINFSectionEx > c:\\windows\\system\\ieuinit.inf,BackupCryptoKeys.Win,,36" > "QuietUninstallString"="Rundll32 advpack.dll,LaunchINFSectionEx > c:\\windows\\inf\\iedom.inf,,,256" > "QuietUninstallString"="rundll32 advpack.dll,LaunchINFSectionEx > c:\\windows\\inf\\hhupdcab.inf,,,256" > "QuietUninstallString"="RunDll32 advpack.dll,LaunchINFSectionEx > c:\\windows\\inf\\icw.inf,,,256" > "QuietUninstallString"="rundll32 advpack.dll,LaunchINFSectionEx > c:\\windows\\inf\\unie5bak.inf,,,256" > "QuietUninstallString"="rundll32 advpack.dll,LaunchINFSectionEx > c:\\windows\\inf\\iereadme.inf,,,256" This is an excerpt from the difference between user.reg before and after. The whole file is 21k and I will be more than happy to supply it if someone wants the whole thing. > --- user.reg.before-13475 2004-10-25 15:56:16.000000000 -0500 > +++ user.reg.after-13938 2004-10-26 20:29:16.000000000 -0500 ................... > -[Environment] 1098735476 > +[Environment] 1098839302 > +"PATH"="c:\\windows;c:\\windows\\system;e:\\;e:\\test;f:\\" > +"Systemroot"="c:\\windows" > +"TEMP"="e:\\" > +"TMP"="e:\\" > +"USERPROFILE"="c:\\windows\\Profiles\\Administrator" > +"windir"="c:\\windows" > +"winsysdir"="c:\\windows\\system" ........................ I didn't use this section from any stance of relevance, but only to demonstrate the difference in the number strings in the [Environment] lines. 10987xxxxx changed to 10988yyyyy is typical both in the system.reg and user.reg files. This section is typical of numbers of lines either present with patch 13938 or absent with it. There are very mand "dword=.............." that are present before patch 13475 and gone after 13938. I have also attached the output of winedbg when running IE6 after patch 13938 and with the system.reg and user.reg files created from the recent version of wine. I thought that this situation could be the results of the changes in wine between now and the time that Mike Hearn wrote his script. However, I was able to duplicate the systems by installing IE6 using Method 2 from Frank's Corner. If anyone has any "hacking" they want me to try, I will be more than happy to do it. Also, if someone wants more information, I will be happy to send what I already have or generate more. Thanks, Dan

1 0

Re: Add time zone to TZ_Info
by Duane Clark 02 Nov '04

02 Nov '04

Roger Olson wrote: > RCS file: /home/wine/wine/dlls/ntdll/time.c,v > retrieving revision 1.51 > diff -u -u -r1.51 time.c > --- dlls/ntdll/time.c 22 Oct 2004 19:54:17 -0000 1.51 > +++ dlls/ntdll/time.c 31 Oct 2004 21:18:46 -0000 > @@ -105,6 +105,9 @@ > {"AKDT", > {'A','l','a','s','k','a','n',' ','S','t','a','n','d','a','r','d',' ','T', > 'i','m','e','\0'}, 480, 1}, > + {"PST", > + {'P','a','c','i','f','i','c',' ','S','t','a','n','d','a','r','d',' ','T', > + 'i','m','e','\0'}, 480, 0}, > {"PDT", > {'P','a','c','i','f','i','c',' ','S','t','a','n','d','a','r','d',' ','T', > 'i','m','e','\0'}, 420, 1}, Hmm... I don't know if anything actually uses the names, but I doubt these are right. PDT would normally be referred to as Pacific Daylight Time. Any chance of getting you to add some tests for these?

4 4

Re: Ok, trying again
by Markus Amsler 02 Nov '04

02 Nov '04

Hi, This patch doesn't aplly smoothly, because you did the cvs diff not from the wine-root directory. do: at ~/src/wine$ cvs diff -u dlls/msvrt/tests/file.c You can test if your patch apllies with $ patch -p0 < file.diff from the wine root. If there are no error messages the format is fine. To remove the patch do $ patch -p0 -R <file.diff I hope this helps Markus Jakob Eriksson wrote: > *src/wine/dlls/msvcrt/tests > > > * > jakov@toto:~/src/wine/dlls/msvcrt/tests$ cvs diff -u file.c > Index: file.c > =================================================================== > RCS file: /home/wine/wine/dlls/msvcrt/tests/file.c,v > retrieving revision 1.10 > diff -u -r1.10 file.c > --- file.c 3 Sep 2004 01:05:30 -0000 1.10 > +++ file.c 1 Nov 2004 16:24:06 -0000 > @@ -306,7 +306,25 @@ > ok(res[strlen(res)-1] != '.', "second call - last character is a > dot\n"); > } > > +static void test_access( void ) > +{ > + FILE *fp; > + > + const char filename[] = "tmpfile.tst"; > + ok(-1 == _access(filename, 0), "This file should not exist yet.\n"); > + ok(ENOENT == errno, "and errno should be ENOENT but it is %d.\n", > errno); > + > + fp = fopen(filename, "w"); > + if (NULL == fp) return; > + fclose(fp); > > + ok(0 == _access(filename, 0), "Now the file should exist.\n"); > + ok(0 == _access(filename, 2), "We should have write permission, > after all I created it. errno=%d\n", errno); > + ok(0 == _access(filename, 4), "We should have read permission. > errno=%d\n", errno); > + ok(0 == _access(filename, 6), "We should also be able to check > for read and write permission. errno=%d\n", errno); > + > + _unlink(filename); > +} > > START_TEST(file) > { > @@ -321,6 +339,7 @@ > return; > } > > + test_access(); > test_fdopen(); > test_fileops(); > test_fgetwc(); > > >

1 0

Re: Edit - wants all keys when multiline
by Dmitry Timoshkov 01 Nov '04

01 Nov '04

"Vitaliy Margolen" <wine-patch(a)kievinfo.com> wrote: > @@ -761,6 +761,12 @@ > > case WM_GETDLGCODE: > result = DLGC_HASSETSEL | DLGC_WANTCHARS | DLGC_WANTARROWS; > + > + if (GetWindowLongW( hwnd, GWL_STYLE ) & ES_MULTILINE) > + { > + result |= DLGC_WANTALLKEYS; EDITSTATE structure already has the 'style' member for the optimization sake, so please use it instead of GetWindowLong(GWL_STYLE). > + r = SendMessage(hwEdit, WM_GETDLGCODE, 0, (LPARAM) &msMessage); > + ok(r==0x89, "Expected DLGC_WANTCHARS | DLGC_HASSETSEL | DLGC_WANTARROWS got %x\n", r); Do not use 0x89 and similar cryptic values in the test, use appropriate symbolic constants instead. And please merge your test into existing win.c tests. -- Dmitry.

3 2

Listview notify_dispinfoT Messageformat
by Thorsten Kani 01 Nov '04

01 Nov '04

Hello, Testing showed that the current implementation of notify_dispinfoT doesnt work with W2K. (or at least not with SP4 (: ) The attached patch corrects that our Listview doesnt display anything on native. Following assumption proved to be wrong for the Message LVN_GETDISPINFOW: /* With testing on Windows 2000 it looks like the notify format has nothing to do with this message. It ALWAYS seems to be in ansi format. */ This time, only LVN_*ETDISPINFOW is patched, anything else is untouched. -Anybody please tell me if you see problems with this Fix since i dont want to break things.- Tho

3 8

Re: COM / Installshield status?
by Tony Lambregts 01 Nov '04

01 Nov '04

Dan Kegel wrote: >Likewise, what's the current status of Installshield support, >and how much work would it be to fully support >Installshield-based installers? I don't see any >open Installshield bug reports, maybe I should file >one against the apps I have that don't install at >the moment. (Or would that be overkill?) > There are lots of bugs against installshield. http://appdb.winehq.org/bugs.php?appId=995. There are 7 that are open and 1 that is marked as later. -- Tony Lambregts

1 0

COM / Installshield status?
by Dan Kegel 01 Nov '04

01 Nov '04

What's the current status on bug 423 (http://bugs.winehq.com/show_bug.cgi?id=423), "Out-of-process COM support"? There hasn't been anything added to that bugzilla entry for two years, and presumably there has been some progress. Perhaps someone in the know could update that bug report. Likewise, what's the current status of Installshield support, and how much work would it be to fully support Installshield-based installers? I don't see any open Installshield bug reports, maybe I should file one against the apps I have that don't install at the moment. (Or would that be overkill?) Thanks, Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

1 0

Default System Colors
by William Poetra Yoga H 31 Oct '04

31 Oct '04

The last time I submitted a patch to change the default system colors from win95 to winxp (classic), it wasn't merged. I think this was because I didn't discuss it here. So now, should we change the default system colors for WINE, from win95 to winxp (classic)? I really think it looks a lot better with the new colors, as the win95 colors are too dull (MS certainly must have done a lot of research into this). Opinions, please. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

2 2

Interesting Installshield failure running Keyhole installer
by Dan Kegel 31 Oct '04

31 Oct '04

If you haven't tried the Keyhole demo on Windows yet, give it a shot. It's kind of fun to look at an aerial view of every place you've ever lived, say. You can download it from http://www.keyhole.com Unfortunately, the installer is a no-go under Wine (cvs as of a couple days ago). It puts up a dialog or two ("Starting InstallShield Wizard", "Preparing Setup"), and then stops with an Installshield dialog box "An error (-5006: 0x80004005) has occurred while running the setup..." There's a Report / Detail / OK choice, which is pretty cool. Choosing Detail shows: Error Code: -5006 : 0x80004005 Error Information: >Kernel\ServiceProvider.cpp (77) >Kernel\ObjectHolder.cpp (441) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >Kernel\FileGroup.cpp (398) >Kernel\ServiceProvider.cpp (77) >SetupDLL\SetupDLL.cpp (1375) pAPP:Keyhole 2 LT PVENDOR:Keyhole Corporation PGUID:036ABCF1-A419-4074-B35C-2C70592A0EBB $7.1.100.1248PAK @Windows 95 (67109814) IE 6.0.2800.1106 For what it's worth, here are the Wine console messages that were shown up to this point: Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file fixme:crypt:CRYPT_VerifyImage (rsabase.dll, 0x4024ce48): not verifying image fixme:crypt:RSA_CPCreateHash 4024ce48 32772 00000000 00000000 0x4024cd84 fixme:crypt:CRYPT_VerifyImage (rsabase.dll, 0x4024c790): not verifying image fixme:crypt:CRYPT_VerifyImage (rsabase.dll, 0x4024ef38): not verifying image fixme:crypt:RSA_CPCreateHash 4023d9c0 32772 00000000 00000000 0x4024eea4 fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects fixme:ole:ITypeInfo_fnRelease destroy child objects ... I'm not really trying to get it to run, just figured I'd post a note about its status while I had a free minute. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

1 0

Re: Wine on FreeBSD current
by Gerald Pfeifer 30 Oct '04

30 Oct '04

>> I'm just wondering if it is supposed to work as well as FreeBSD stable. Right now, Wine doesn't work at all on FreeBSD -STABLE: wine: failed to initialize: /swtest/wine/dlls/ntdll.dll.so: mmap of entire address space failed: Cannot allocate memory and before that I used to see deadlocks upon startup of non-trivial applications (such as Forte Agent, both 16bit and 32bit flavors). I believe there are also signficant threadings issues on -CURRENT, so overall Wine is hardly, if at all, usable on any version of FreeBSD I have access to, even though I'm still working to keep it at least compilable on FreeBSD 4.9 and 5.2/5.3. Gerald -- Gerald Pfeifer (Jerry) gerald(a)pfeifer.com http://www.pfeifer.com/gerald/

6 13

Re: Gradient Color for Caption Bar
by William Poetra Yoga H 30 Oct '04

30 Oct '04

My patch didn't get merged... :( Anything wrong with it? Maybe I should make NC_DrawCaption() call DrawCaption() instead? Otherwise I think it's good enough. Any ideas why my patch wasn't merged? Lack of testsuite? Thanks. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

1 0

Re: Listview: Fix notify_dispinfoT for Unicode Parent
by Dimitrie O. Paun 30 Oct '04

30 Oct '04

On Sat, Oct 30, 2004 at 02:16:09PM +0100, Robert Shearman wrote: > + /* > + only need to convert to string from Unicode to Ansi if we expect a > + valid pointer > + */ > + if ((infoPtr->notifyFormat == NFR_ANSI) && (pdi->item.mask & LVIF_TEXT) && is_textT(pdi->item.pszText, FALSE)) > + convertToAnsi = TRUE; This can't be right -- what if the data is already in ASCII format? I think we need to take isW into account. -- Dimi.

1 0

CurrentVersion missing
by James Hawkins 30 Oct '04

30 Oct '04

The string HKLM\Software\Microsoft\Windows NT\CurrentVersion\CurrentVersion is missing from a normal wine install. When installing gmail notifier, the installer checks to make sure the OS version is NT or greater, but the installer calls GetVersion(), and after that succeeds, it then queries the CurrentVersion string above from the registry, but doesnt find it. After I added the key manually and set it to an arbitrary "1", the install proceeds (it only checks the length of the string not the actual data). Shouldn't this string always be a part of the registry anyway? And if so, how would I go about making sure that it is a part of the standard registry that ships with wine? -- James Hawkins

1 0

Adminrights...
by Devils Cry 30 Oct '04

30 Oct '04

Hey there! I just had an app which i wanted to install, but when i started the setup it gave me an error about the uninstallshield being active and that it has to be turned off. I googled a bit around and found out that this error only occurs if the setup is started by a user without administration rights. I tried it out, after suing i had no problems anymore. I guess there are several risks connected to so my question simply is: how can this be ommited? Regards Nikolas

1 0

Re: Success Stories?
by Scott Ritchie 30 Oct '04

30 Oct '04

>Are there any plans to spotlight Wine-use success >stories on the WineHQ home page? I always think of >how Disney used Wine to run Photoshop 7 so they could >move to a Linux platform. I'm sure it could draw >additional attention/ support and provide additional >credibility to non-Wine users. This exact story is on the CodeWeavers page somewhere, as an advertisement for Crossover. At the least, read it first :) Regardless, good luck!

1 0

Re: question about modal messageboxes.
by Ivan Leo Puoti 30 Oct '04

30 Oct '04

>WS_EX_TOPMOST does nothing on Wine anyway, so I wouldn't worry too >much about it. We certainly don't want 2 different resources, but it >would probably be cleaner to remove DS_SYSMODAL on the existing >resource, since the default is MB_APPLMODAL. So if I get WS_EX_TOPMOST to work should I use 2 resources? The only other solution I can think of is using an atom, that sounds quite ridiculous for such a trivial thing. AFAIK apart from this detail sysmodal boxes have no reason for being a fixme. Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

2 1

Re: SHDOCVW: download the Mozilla Active X control on demand (take 2)
by Alexandre Julliard 30 Oct '04

30 Oct '04

Mike McCormack <mike(a)codeweavers.com> writes: > This patch downloads the mozilla active control on demand. It needs > the following registry key to be present to function correctly: > > [Software\\Wine\\Mozilla Control] 1089668326 > "Url"="http://www.iol.ie/~locka/mozilla/MozillaControl16.exe" > "Prog"="%TEMP%\\MozillaControl16.exe" The user shouldn't have to specify the temp file name, we can clearly figure this out by ourselves. Also the registry entry should be under Software\Wine\shdocvw, config parameters specific to a dll should use the dll name as key to avoid namespace conflicts. -- Alexandre Julliard julliard(a)winehq.org

1 0

question about modal messageboxes.
by Ivan Leo Puoti 30 Oct '04

30 Oct '04

I looked at MSDN docs for MessageBox http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winu… and found that MB_SYSTEMMODAL is identical to MB_APPLMODAL, the only difference is that the dialogue box is created with WS_EX_TOPMOST. In Wine the window style is loaded from user32_En.rc, and STYLE contains, amongst other things, DS_SYSMODAL. MSDN http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winu… says that if this value is used the window will be created using the WS_EX_TOPMOST style. But what this means is that in Wine a messagebox is *always* created with this style, while, if MSDN is correct, this should only happen when MB_SYSTEMMODAL is passed to MessageBox. Am I getting something wrong or is this a bug? If yes, would creating 2 resources, one for MB_APPLMODAL and one for MB_SYSTEMMODAL be a good solution? Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

2 1

Re: rsaenh
by Juan Lang 29 Oct '04

29 Oct '04

Michael wrote: > If I use /dev/random in my patch the unit tests take more than three > minutes without any user interaction. As to be expected, it runs faster > if I move the mouse around wildly to generate entropy => You're right, this seems unreasonable for 32 bytes of random data, especially in this context. Alexandre has the final word anyway, so submitting to wine-patches was a good idea. Again, sorry I didn't see all this up front, but I'd like to suggest the following improvement: If OpenSSL is available, go ahead and use RAND_bytes, but call RAND_add first with the input buffer. I don't have a good estimate for the number of bits of entropy to expect, since we don't know whether the caller will actually have provided a seed. Assuming it's unlikely, maybe RAND_add(pbBuffer, dwLen, dwLen / 16.0f)? And go ahead and fall back to /dev/urandom if OpenSSL isn't available. Thanks, --Juan __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

1 0

We hit 5mb for 3 months running!
by Mike Hearn 29 Oct '04

29 Oct '04

Hey guys, Here's a great excuse for a party: wine-patches has had 5mb of traffic per month for the last three months now. Apart from a short dip over the summer, it looks like we've been consistently generating 5mb/month for most of the year! 2003 was mostly hovering around the 4mb level, and 2002 was mostly 1-2mb (apart from when Dimi had his listview hackfest and we got 6mb!) so we seem to be doing something right :) Let's see if we can keep it up and who knows, maybe 2005 will be averaging at 6mb/month! Expect me to be doing my bit in a few days (ADSL on Nov 1st now :) thanks -mike

1 0

Wine, openssl, kerberos, and "fixme:crypt:RSA_CPAcquireContext You have to install libcrypto.so..."
by Dan Kegel 29 Oct '04

29 Oct '04

Maybe this is old hat, but: I ran into the message fixme:crypt:RSA_CPAcquireContext You have to install libcrypto.so and development headers in order to use crypto API while running an app. Looking at the code, it's only issued if wine's configure can't find /usr/include/openssl/ssl.h. But I have that file! Digging deeper, I saw that ssl.h includes krb5.h, which isn't on the standard include path. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82369 explains the issue. It looks like configure.ac needs to be modified as described in that bug report to check for pkgconfig-openssl, and use it if present to guess the cflags needed to use openssl: $ pkg-config openssl --cflags -I/usr/kerberos/include A workaround seems to be to configure like this: ./configure CFLAGS="-I /usr/kerberos/include " This happily sets HAVE_OPENSSL_SSL_H in include/config.h. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

2 1

Re: SHDOCVW: download the Mozilla Active X control on demand (take 2)
by Andreas Mohr 29 Oct '04

29 Oct '04

Hi, On Fri, Oct 29, 2004 at 01:52:27PM +0900, Mike McCormack wrote: > I think we should not put Adam's page in our registry by default, but > perhaps host the control on WineHQ somewhere and use the URL for that > instead, so as not to direct too much traffic to Adam's page... Well, the least we should do is have the URL point to WineHQ and then use a forward page to his URL IMHO. Hosting it on WineHQ would probably be the best way indeed. Andreas Mohr

2 1

Re: USER32: add a short test for child windows (take 2)
by Dmitry Timoshkov 29 Oct '04

29 Oct '04

"Mike McCormack" <mike(a)codeweavers.com> wrote: > ChangeLog: > * add a short test for child windows > START_TEST(win) > { > + test_child_window(); > + > pGetAncestor = (void *)GetProcAddress( GetModuleHandleA("user32.dll"), "GetAncestor" ); > pGetWindowInfo = (void *)GetProcAddress( GetModuleHandleA("user32.dll"), "GetWindowInfo" ); Please add your test at the end of existing tests. By placing the test before everything else you are at least skipping the tests performed in the hook procedure. -- Dmitry.

1 0

Re: USER32: add a short test for child windows
by Dmitry Timoshkov 29 Oct '04

29 Oct '04

"Mike McCormack" <mike(a)codeweavers.com> wrote: > ChangeLog: > * add a short test for child windows Could you please merge it with existing win.c tests? -- Dmitry.

1 0

Re: Success Stories?
by Brian Vincent 29 Oct '04

29 Oct '04

On Thu, 28 Oct 2004 16:06:56 -0700 (PDT), M-Halo <masochisthalo(a)yahoo.com> wrote: > Are there any plans to spotlight Wine-use success > stories on the WineHQ home page? I always think of Nope, there's no plans. Are you volunteering? It would be great if you could do it. Rather than just provide links, I think it would be nice to put together short summaries and short interviews about it. In other words, create original content rather than regurgitate an article. -Brian Vincent

2 2

signaling unix threads
by Markus Amsler 29 Oct '04

29 Oct '04

Hi, There's a fundamental bug in winedos/dosvm. c[1]. SIGUSR2 is sent to the current process, but it should be sent to the dosvm thread. This causes various ugly bugs. I found no way signaling a unix thread, without modifing the wineserver. I have implemented a thread_kill command in the wineserver, this solves my problem, but i'm quite sure it won't get applied. I'm really not a wineserver/threading expert. Have I missed something? Markus

2 1

Re: [Wine]How to help improving Wine?
by Walt Ogburn 29 Oct '04

29 Oct '04

Hi Emanuele, After poking around a bit, there seems to be a logical problem in Wine's GDI code. From the backtrace, SelectObject on this object calls BRUSH_SelectObject, which uses a bitmap and eventually GetDIBits, which tries to CreateCompatibleDC (or sometimes DeleteDC instead). However, SelectObject always calls GDI_GetObjPtr, which calls _EnterSysLevel and not _LeaveSysLevel. But the CreateCompatibleDC complains and dies if you have had an _EnterSysLevel and not a _LeaveSysLevel. It might be that BRUSH_SelectObject really should use a different set of "internal" functions that won't complain about locking. Or maybe DeleteDC and CreateCompatibleDC should just increment the recursion level instead of erroring out. I don't know, so I'm forwarding to wine-devel for greater insight. - Walter Here's a summary of the relevant part of my backtrace again: 1 _CheckNotSysLevel (complains!) 2 GDI_CheckNotLock 3 DeleteDC 4 GetDIBits 5 MFDRV_CreateBrushIndirect 6 MFDRV_SelectBrush 7 BRUSH_SelectObject 8 SelectObject - calls GDI_GetObjPtr, which does _EnterSysLevel. On Thu, 28 Oct 2004, Emanuele Gissi wrote: > Hi, > I really did my best to understand how I can help improving Wine, but I did > not succed. > > Well, everything started when I installed a win application on my Debian 3.1, > Wine 2004.07.16 deb (clean install, no dlls). > > The application is ALOHA (http://www.epa.gov/ceppo/cameo/aloha.htm) > It's a free application from US-Environment Protection Agency used for > chemical emergency planning (I am an officer firefighter). > > On Wine it has a problem that prevents its wide use. > After having entered all the needed data (or loading the included prova.alo > example in "planning mode"), Wine crashes when tring to show the chemical > footprint result. > > The application works perfectly on Codeweavers Crossover Office 3.0.1 (trial). > And I am ready to buy it (as they support the free Wine, I think.) > > But I would like to understand why it does not work on Wine! > > The included log finishes with this: > [...] > warn:heap:HEAP_ValidateInUseArena Heap 40360000: invalid in-use arena magic > for 403bd120 > warn:heap:HEAP_ValidateInUseArena Heap 40360000: invalid in-use arena magic > for 403b46f0 > warn:heap:HEAP_ValidateInUseArena Heap 40360000: invalid in-use arena magic > for 403b6948 > warn:heap:HEAP_ValidateInUseArena Heap 40360000: invalid in-use arena magic > for 403b1570 > warn:heap:HEAP_ValidateInUseArena Heap 40360000: invalid in-use arena magic > for 403b11c0 > warn:gdi:GDI_GetObjPtr Invalid handle (nil) > warn:gdi:GDI_GetObjPtr Invalid handle (nil) > warn:gdi:GDI_GetObjPtr Invalid handle (nil) > err:syslevel:_CheckNotSysLevel Holding lock 0x408f15e0 level 3 > wine: Unhandled exception (thread 0009), starting debugger... > > 1) What should I do next time I encounter a similar problem with an app? That > is: how to use winedbg? > 2) Why does ALOHA work on Crossover and not on Wine? > 3) Which are the main differences between Crossover and Wine? > 4) Does Codewaver really contribute back to Wine? > > I thank you in advance. > > (Please, CC: me as I am not on the list for now) > -- > Ing. Emanuele Gissi - Ispettore Antincendio > Comando Provinciale dei Vigili del Fuoco di Ravenna > viale Randi, 25 - 48100 Ravenna - Italia > tel: 0544 281.501 - fax: 0544 281.531 >

1 0

Success Stories?
by M-Halo 28 Oct '04

28 Oct '04

Hi all, Are there any plans to spotlight Wine-use success stories on the WineHQ home page? I always think of how Disney used Wine to run Photoshop 7 so they could move to a Linux platform. I'm sure it could draw additional attention/ support and provide additional credibility to non-Wine users. I know this article is a year old, but I think it's the type of thing that should be shown to the world: :) http://www.eweek.com/article2/0,3959,1210083,00.asp Hiji __________________________________ Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. http://messenger.yahoo.com

1 0

Re: Windows XP Setup
by Ivan Leo Puoti 28 Oct '04

28 Oct '04

> How much effort would it take to get setup.exe on windows XP CD to run > from begining to end. I guess the setup wants direct hardware access. Also, it probably reboots, and after reboot you'll be running on the windows kernel anyway. I don't think this is really possible. Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

2 1

rsaenh
by Michael Jung 28 Oct '04

28 Oct '04

Hello, this is an updated version of my rsaenh.dll patch from yesterday with Juan's suggestions implemented: 1.) Changed destruct_... function names to destroy_... . 2.) Removed the multiple-of-four behaviour for handles. 3.) Got rid of the splitting of handle management functions into one table locking function and one function, which actually does the real work. 4.) MD4, MD5 and SHA hashes as well as random number generation will work now even if rsaenh was compiled with libssl-dev headers available, but no libcrypto.so at run-time. 5.) Compilation fixes for the case that OpenSSL was configured to support only a subset of the functions imported by rsaenh.dll. 6.) Uses /dev/urandom instead of OpenSSL's RAND_bytes function. (Do we have to check for the availability of /dev/urandom in the configure script?) If you want to try the patch note the following: - After you have applied the patch you have to run autoheader and autoconf. Then cd dlls ; make_dlls ; cd .. ; configure. - After you have compiled and installed wine, you have to unregister rsabase and register rsaenh (regsvr32 /U rsabase ; regsvr32 rsaenh). rsaenh.dll is meant to replace rsabase.dll sometime (Windows XP also has rsaenh.dll only). Greetings, Michael

4 8

_wrapped_ java application with wine
by Mario Ohnewald 28 Oct '04

28 Oct '04

Hello Devel List! I am sorry to bother you. But i cant seem to solve my wine/java issue in the users mailing list. I have already asked in the users list, but nobody seems to know an answer. http://www.winehq.org/hypermail/wine-users/2004/10/0344.html I have already tried to install JRE with the latest wine snapshot, and with a debian package. This is the error i get, where wine cant seem to be able to handle the memory request: Invoking /usr/lib/wine/wine.bin jre-1_5_0-windows-i586.exe ... fixme:msi:MsiGetProductInfoA "{3248F0A8-6813-11D6-A77B-00B0D0150000}" "PackageCode" 0x4067dbbc 0x4067dc2c fixme:msi:MsiGetProductInfoW L"{3248F0A8-6813-11D6-A77B-00B0D0150000}" L"PackageCode" 0x4037f728 0x4067dc2c err:msi:MsiGetSummaryInformationW IStorage -> IPropertySetStorage failed Wine failed with return code 133 Any idea how i could solve this? Maybe one of you would like to give it a try. Here is the JRE Download page: http://java.sun.com/j2se/1.5.0/download.jsp Thanks a lot! Mario -- NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl GMX DSL-Netzanschluss + Tarif zum superg�nstigen Komplett-Preis!

2 1

Writing tests
by Walt Ogburn 28 Oct '04

28 Oct '04

Hi folks, I have a question about dependencies when writing tests. Some tests use LoadLibraryA and GetProcessAddress to get access to Windows / Wine APIs, and other tests just include the appropriate header files and link to the DLLs. One example of the first type is dlls/oleaut32/olefont.c: ================ <snip> ============================================== static HMODULE hOleaut32; static HRESULT (WINAPI *pOleCreateFontIndirect)(LPFONTDESC,REFIID,LPVOID*); START_TEST(olefont) { LPVOID pvObj = NULL; HRESULT hres; IFont* font = NULL; hOleaut32 = LoadLibraryA("oleaut32.dll"); pOleCreateFontIndirect = (void*)GetProcAddress(hOleaut32, "OleCreateFontIndirect"); if (!pOleCreateFontIndirect) return; ===================================================================== What is the reason for this difference? Which example should new tests follow? My guess is that LoadLibraryA and GetProcAddress are used if the headers, DLLs, and APIs might not be present on some Windows machines, so that the tests don't fail. If that's correct, is there a list somewhere of which ones are safe and which ones should be handled like in the olefont test? Thanks, Walter

2 1

Re: change default colors to winxp colors; add COLOR_MENUHILIGHT and COLOR_MENUBAR
by William Poetra Yoga H 28 Oct '04

28 Oct '04

--- William Poetra Yoga H <williampoetra(a)yahoo.com> wrote: > Use default colors for Windows XP's Windows Classic style, Windows Standard > color scheme. > > Added new indexes for DefSysColors: COLOR_MENUHILIGHT and COLOR_MENUBAR > My patch was not merged... :( Um... any problems with the patch? Please comment. Thanks :) __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

1 0

Re: Gradient Color for Caption Bar
by Mike McCormack 28 Oct '04

28 Oct '04

William Poetra Yoga H wrote: > Use GdiGradientFill (not GradientFill) to implement gradient caption bar (for now). GradientFill is pretty slow, as it files the rectangle line by line. I'm not sure how much this is going to slow down a normal application. It used to draw pixel by pixel, and that was a very noticable slowdown... line by line is much faster than that, but it still may cause a slowdown in some circumstances. Anybody have any ideas about how to speed up GradientFill? Mike

3 2

rsaenh and /dev/urandom
by Michael Jung 28 Oct '04

28 Oct '04

Hello, some more thoughts on the security of using /dev/urandom. This is from MSDN (CryptGenRandom): > With Microsoft CSPs, CryptGenRandom uses the same random number generator > used by other security components. This allows numerous processes to > contribute to a system-wide seed. CryptoAPI stores an intermediate random > seed with every user. To form the seed for the random number generator, a > calling application supplies bits it might have—for instance, mouse or > keyboard timing input—that are then added to both the stored seed and > various system data and user data such as the process ID and thread ID, the > system clock, the system time, the system counter, memory status, free disk > clusters, the hashed user environment block. This result is SHA-1 hashed, > and the output is used to seed an RC4 stream, which is then used as the > random stream and used to update the stored seed. This is from the linux kernel sources (2.6.8.1 drivers/char/random.c): > When random bytes are desired, they are obtained by taking the SHA > hash of the contents of the "entropy pool". The SHA hash avoids > exposing the internal state of the entropy pool. It is believed to > be computationally infeasible to derive any useful information > about the input of SHA from its output. Even if it is possible to > analyze SHA in some clever way, as long as the amount of data > returned from the generator is less than the inherent entropy in > the pool, the output data is totally unpredictable. For this > reason, the routine decreases its internal estimate of how many > bits of "true randomness" are contained in the entropy pool as it > outputs random numbers. > > If this estimate goes to zero, the routine can still generate > random numbers; however, an attacker may (at least in theory) be > able to infer the future output of the generator from prior > outputs. This requires successful cryptanalysis of SHA, which is > not believed to be feasible, but there is a remote possibility. > Nonetheless, these numbers should be useful for the vast majority > of purposes. Condensed, I read this as follows: - Microsoft uses an entropy source to seed a pseudo-random generator. If the seed is known, then the pseudo-random numbers are predictable. - /dev/urandom is also seeded with an entropy source. However, whenever the kernel collects new entropy, this also affects /dev/urandom. As I understand it, this basically means the following: In the worst case (kernel doesn't collect new entropy), we are as good as Microsoft. In all other cases /dev/urandom is better. Given this and the fact that OpenSSL also seems to apply /dev/urandom, I think rsaenh should also do it this way. Greetings, Michael

1 0

Re: Re-implement MSVCRT *printf
by Mike McCormack 28 Oct '04

28 Oct '04

Aneurin Price wrote: > Comments, anyone? Looks like you've put quite a bit of effort into that. I think it's a worthwhile effort, however, please consider: * using a style more consistent with the rest of the Wine codebase * not abusing the preprocessor in printf.h, * not writing C code in the header in printf.h * preventing code duplication by implementing the A functions using the W functions * writing some regression tests to show your code is correct thanks, Mike

4 3

Windows XP Setup
by Jacobus Erasmus 28 Oct '04

28 Oct '04

Just a quick question, How much effort would it take to get setup.exe on windows XP CD to run from begining to end. (And in the process install the DLL's fonts etc.) The second question is if somebody is willing to take on this task and how much would it cost me. Regards jacobus(a)kewlconcepts.co.za

1 0

Re: shell32: SHFileOperation improvements
by Mike McCormack 28 Oct '04

28 Oct '04

Rolf, Thanks for cleaning up SHFileOperation. Can you please try restructuring your code further to get rid of the excessive number of branching points in that function? Last time I counted, SHFileOperation had more than 60 if/while/for/case statements in the one +500 line function... that makes it hard to read. If you were to make use of helper functions more often, you'd improve your code's readability, eliminate the need for 2-space indent, the pointless /* end-if */ comments, reduce the excessive number of local variables and reduce side effects, thus making it easier for other people to understand and fix the code. Try make small functions that fit in ~50 lines. If a function gets over 50 lines, cut it up into two new functions. Mike Rolf Kalbermatter wrote: > + if (b_Multi || IsAttribFile(FromAttr)) > + continue; > + if (IsAttribDir(FromAttr)) > + { > + /* in w98/w2k/wXp endless recursive move until it aborts due to filename getting to > + long, we don't do this stupidity but return the according error anyhow here */ > + retCode = ERROR_FILENAME_EXCED_RANGE; > + break; > + } > } > - } > + if (( b_SameRoot_MOVE && (b_Multi) && !(b_MultiFrom) && IsAttribFile(FromAttr) && IsAttribDir(ToAttr)) > + || (!(b_MultiFrom) && IsAttribFile(FromAttr) && IsAttribFile(ToAttr)) > + || ( (b_Multi) && IsAttribDir(FromAttr) && IsAttribDir(ToAttr)) > + || (!b_SameRoot_MOVE && IsAttribDir(FromAttr) && IsAttribFile(ToAttr)) > + ) > + { > + ToAttr = SHRenameOnCollision(&nFileOp, pToFile + 1, pFromFile + 1); > + } /* endif */ > + } /* endif */ > + if (!(b_MultiFrom) && (!FlagRenameOnCollision(&nFileOp) || b_SameRoot_MOVE) && > + ((SFSC_IDENTIICAL | SFSC_SOURCE_CONTAINS_TARGET) & f_SameDrive)) > + { > + if (!FlagRenameOnCollision(&nFileOp) && (IsAttribFile(FromAttr))) > + { > + /* target is the same as source */ > + retCode = 0x71; > + } > + break; > + } /* endif */ > + > + /* Analyzing for moving SourceName to TargetName */ > + if ((b_MultiFrom || !b_Multi) && ((IsAttribFile(FromAttr) && IsAttribDir(ToAttr)) || > + (!b_MultiTo && IsAttribDir(ToAttr)) || > + (!b_MultiTo && IsAttribDir(FromAttr) && b_MultiFrom && !b_SameRoot_MOVE))) > + { > + SHFileStrCpyCatW(pTempTo, NULL, pFromFile); > + /* without FOF_MULTIDESTFILES shlfileop would create dir's recursively */ > + nFileOp.fFlags |= FOF_MULTIDESTFILES; > + retCode = SHFileOperationW(&nFileOp); > + continue; > + } > + /* What can we do with one pair and FO_MOVE/FO_COPY ? */ > + /* w98se, nt40 does create recursive dirs, W2K not! wMe ist not tested */ > + if (IsAttribDir(ToPathAttr) || !b_SameRoot_MOVE) > + { > + if (!b_MultiFrom) > + { > + if (IsAttribFile(FromAttr)) > + { > + if (b_SameRoot_MOVE && > + /* windows-bug, MOVE for File also with pToTailSlash, COPY not for this */ > + (!(IsAttribFile(ToAttr)) || (!(FlagAskOverwrite(&nFileOp)) && FlagNotOverwrite(&nFileOp))) && > + (IsAttribDir(ToPathAttr) || b_ToMask)) > + { > + /* With the same drive, we can move for FO_MOVE, dir to dir is solved later */ > + retCode = SHNotifyMoveFileW(nFileOp.pFrom, nFileOp.pTo); > + continue; > + } /* endif */ > + if (IsAttribDir(ToPathAttr) && !pToTailSlash && !IsAttribDir(ToAttr)) > + { > + if (!(FOI_NeverOverwrite & nFileOp.fAnyOperationsAborted)) > + { > + if (!FlagNotOverwrite(&nFileOp)) > + { > + ToAttr = INVALID_FILE_ATTRIBUTES; > + } > + if (IsAttribFile(ToAttr) && FlagNotOverwrite(&nFileOp)) > + { > + if (FlagAskOverwrite(&nFileOp)) > + { > + /* FIXME: we must change the dialog in the future to allow 3-4 cases, > + * 'Yes','No','Yes for all','Never ?' */ > + if ((INVALID_FILE_ATTRIBUTES != ToAttr) && !SHELL_ConfirmDialogW(ASK_OVERWRITE_FILE, pTempTo)) > + { > + retCode = 0x10008; > + nFileOp.fAnyOperationsAborted |= TRUE; > + break; > + } > + ToAttr = INVALID_FILE_ATTRIBUTES; > + } /* endif */ > + } /* endif */ > + } /* endif */ > + if (INVALID_FILE_ATTRIBUTES == ToAttr) > + { > + if (SHNotifyCopyFileW(pTempFrom, pTempTo, FlagRenameOnCollision(&nFileOp))) > + { > + /* the retcode for this case is unknown */ > + retCode = 0x10009; > + } > + if ((FO_COPY != FuncSwitch) && !retCode) > + { > + nFileOp.wFunc = ((level + 1) << FO_LevelShift) + FO_DELETE; > + retCode = SHFileOperationW(&nFileOp); > + } > + continue; > + } > + } > + } > + if (IsAttribDir(FromAttr)) > + { > + if (INVALID_FILE_ATTRIBUTES == ToAttr) > + { > + SetIfPointer(pToTailSlash, '\0'); > + ToAttr = SHRenameOnCollision(&nFileOp, pToFile + 1, pFromFile + 1); > + if (INVALID_FILE_ATTRIBUTES != ToAttr) > + { > + /* w2k returns ERROR_ALREADY_EXISTS, if it found the target with mask */ > +#if 1 > + retCode = ERROR_ALREADY_EXISTS; > +#else > + retCode = ERROR_INVALID_NAME; > +#endif > + nFileOp.fAnyOperationsAborted |= TRUE; > + break; > + } > + lpFileName = &pToFile[lstrlenW(pToFile)]; > + if (pToTailSlash) > + { > + pToTailSlash = lpFileName; > + lpFileName++; > + } > + ((DWORD*)lpFileName)[0] = '\0'; > + retCode = SHNotifyCreateDirectoryW(pTempTo, NULL); > + > + if (retCode) > + { > + retCode = (ERROR_PATH_NOT_FOUND | 0x10000); /* nt40,w98se,w2k,wxp */ > + break; > + } > + ToAttr = GetFileAttributesW(pTempTo); > + SetIfPointer(pToTailSlash,'\\'); > + nFileOp.fFlags &= ~FOF_RENAMEONCOLLISION; > + } > + if (IsAttribDir(ToAttr)) > + { > + /* both are existing dirs, we (FO_)MOVE/COPY the content */ > + pToFile = SHFileStrCpyCatW(pTempFrom, NULL, wWildcardFile); > + nFileOp.fFlags &= ~FOF_MULTIDESTFILES; > + retCode = SHFileOperationW(&nFileOp); > + if ((FO_COPY != FuncSwitch) && !retCode) > + { > + ((DWORD*)pToFile)[0] = '\0'; > + nFileOp.wFunc = ((level + 1) << FO_LevelShift) + FO_DELETE; > + retCode = SHFileOperationW(&nFileOp); > + } > + continue; > + } > + } /* endif IsAttribDir(from) */ > + } /* endif !b_MultiFrom */ > + } > + if (!b_SameRoot_MOVE) > + { > + nFileOp.fAnyOperationsAborted |= TRUE; > + } /* endif */ > + retCode = ERROR_CANCELLED; > + } /* end-while */

1 0

Re: rsaenh
by Juan Lang 27 Oct '04

27 Oct '04

Hi Michael, that was quick! Okay, more feedback: 1. English note: destruct_handle_table really should be destroy_handle_table. I know, "destructor" came into common use, but the verb is to destroy. Same with destruct_key, destruct_hash, etc. 2. A CSP isn't allocating a "real" handle, it's sort of a pseudohandle, so the multiple-of-four business isn't necessary. When I was testing SSPs, I found some of them return 0 as a valid handle value. So I think using the index directly would be fine. 3. Do you really need to separate all the functions into an impl version and a non-impl version? It looks as though the non-impl version does the locking, while the impl assumes the table is locked. It seems you could at least document this, and it also doesn't seem necessary in every case, if at all--EnterCriticalSection won't deadlock if a thread that's already entered it calls it again. 4. Some of the OpenSSL checks don't seem valid. In init_hash_impl, for example, you fail if libcrypto isn't available, even if it isn't necessary for the hash. Please fail only if you really need an OpenSSL func. E.g., if (!pMD2_Init) { SetLastError()... } seems better to me. 5. This may be open to debate, but as far as a "more elegant way": perhaps you should protect each typedef with the header file that defines it, e.g. in HASH_CONTEXT, rather than: #ifdef HAVE_OPENSSL MD2_CTX md2; #endif you could use: #ifdef HAVE_OPENSSL_MD2_H MD2_CTX md2; #endif This way you could support the algorithms you were compiled with, even if they aren't the entire set. Sorry I didn't mention these last time.. --Juan __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

2 2

Re: Re-implement MSVCRT *printf
by Mike Hearn 27 Oct '04

27 Oct '04

I'm not sure if this is just Mozilla acting up but the patch doesn't seem to be fully indented. Is this just UA wierdness? Aneurin Price wrote: > Comments, anyone? >

1 0

Re: Gradient Color for Caption Bar
by Dmitry Timoshkov 27 Oct '04

27 Oct '04

"William Poetra Yoga H" <williampoetra(a)yahoo.com> wrote: > This patch is for filling the caption bar (a.k.a. title bar) with gradient > colors, like in Win98/WinME/Win2K/WinXP. > > I've modified nonclient.c too heavily (work on other parts of it), so this > patch may generate offsets or things like that. Please comment on wine-devel. > Thanks. > -IMPORTS = gdi32 advapi32 kernel32 ntdll > +IMPORTS = msimg32 gdi32 advapi32 kernel32 ntdll Use gdi32.GdiGradientFill instead of msimg32.GradientFill, the latter one is forwarded to gdi32 anyway. -- Dmitry.

3 3

Re: GetTimeZoneInformation return value fix
by Alexandre Julliard 27 Oct '04

27 Oct '04

Rein Klazes <rklazes(a)xs4all.nl> writes: > - reordered some code from the existing helper _GetTimeZoneBias > to make it more general useful (and changed the helper names to > TIME_xyz). > - Make GetTimeZoneInformation return the correct zone id > constants. > - changed some "const LPX_Y_Z" declarations to "const X_Y_Z *" This breaks the msvcrt tests: ../../../tools/runtest -q -P wine -M msvcrt.dll -T ../../.. -p msvcrt_test.exe.so time.c && touch time.ok time.c:101: Test failed: Wrong date:Year 70 mon 0 yday 1 mday 2 wday 5 hour 0 min 0 sec 0 dst -1 time.c:112: Test failed: Wrong date:Year 70 mon 0 yday 1 mday 2 wday 5 hour 0 min 0 sec 0 dst -1 -- Alexandre Julliard julliard(a)winehq.org

2 1

RE: Wine User Guide Improvements
by Scott Ritchie 27 Oct '04

27 Oct '04

Brian, I agree with your plan to condense the guide down. I would still keep some parts of the Getting Wine chapter and put it at the end of the introduction, or possibly at the beginning of configuring wine. I agree about changing it to be mostly a reference to the relevant parts of WineHQ. Would it be duplicitous of me to just go ahead and redo the Getting Wine chapter and leave it as it is now, and perhaps merge it into configuring/introduction once you're done? That way we'll have 4 chapters: Introduction Configuring Wine Running Wine Troubleshooting The running wine chapter eventually needs to be rewritten too (outdated switches, etc.) It could probably be reorganized a bit to read nicer as well (for example, directions for uninstalling programs are given before running them.) I'd like to have the documentation revamped by the next release. Combined with the coming winecfg patches, the major red marks at http://www.winehq.org/site/todo_lists can be replaced with happy green bars. I think we can easily have the yellow bit for the User Guide finished by then too. After that, the only major things in the way of 0.9 seem to be the developer and winelib guide, which are a bit beyond my abilities. (note: forwarded to wine-devel for further feedback) Thanks, Scott Ritchie

2 1

rsaenh
by Michael Jung 26 Oct '04

26 Oct '04

Hello, this is an updated version of the rsaenh implementation from yesterday. Updates: 1.) Broke long lines to not exceed a length of 100 characters. 2.) Substituted tabs with spaces. 3.) Removed magic constants. 4.) Rsaenh now uses MD4, MD5 and SHA from advapi32. 5.) Regression tests should work now without failures even if OpenSSL is not available. 6.) Fixed filenames in comments. If you want to try the patch note the following: - After you have applied the patch you have to run autoheader and autoconf. Then cd dlls ; make_dlls ; cd .. ; configure. - After you have compiled and installed wine, you have to unregister rsabase and register rsaenh (regsvr32 /U rsabase ; regsvr32 rsaenh). rsaenh.dll is meant to replace rsabase.dll sometime (Windows XP also has rsaenh.dll only). Greetings, Michael

1 0

Re: WSCEnumProtocols
by Alexandre Julliard 26 Oct '04

26 Oct '04

Hans Leidekker <hans(a)it.vu.nl> writes: > +INT WINAPI WSAEnumProtocolsA( LPINT lpiProtocols, LPWSAPROTOCOL_INFOA lpBuffer, LPDWORD lpdwLength ) > +{ > + return WINSOCK_EnumProtocols( lpiProtocols, (WSAPROTOCOL_INFOW *)lpBuffer, lpdwLength, FALSE ); > +} You cannot cast a WSAPROTOCOL_INFOA* to a WSAPROTOCOL_INFOW*, the structures don't have the same size. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: rsaenh
by Michael Jung 26 Oct '04

26 Oct '04

On Tuesday 26 October 2004 16:56, Juan Lang wrote: > Michael wrote: > > > 1. MD4, MD5, and SHA1 are now implemented in wine's > > > advapi32. Please use these instead of OpenSSL's. > > > > Yes, that makes sense. Would it be possible to move > > the SHA1, MD4 and MD5 related code to some other > > directory in the wine tree and link to it > > statically from both advapi32 and rsaenh? Is the > > misc directory meant for this purpose? > > No. Generally, creating static libs is something we > avoid in wine. More specifically, these functions are > already exported by advapi32, and you already link > advapi32 (to get access to the registry) so there's no > advantage to having a copy in both places. There is also a DES implementation in dlls/advapi32/crypt_des.c. However, this one is not exported by advapi32.dll. I could copy the code over to dlls/rsaenh, but this would mean unnecessary code duplication. How are such cases handled in wine typically? Although it is of no concern at the moment, another problem will arise in the future: advapi32 and cryptographic service provider dll's check each other against tempering by the use of digital signatures in windows (Probably because of US export restrictions on cryptographic software). Although I don't know for sure, I could imagine that this is actually the reason, why there are MD4, MD5 and SHA implementations in advapi32. Having rsaenh.dll call advapi32.dll for these algorithms would bypass these checks. I don't know if this will be an issue for wine though. Greetings, Michael

2 1

Re: shell32: shellpath tests failing greatly
by Juan Lang 26 Oct '04

26 Oct '04

Hi Rolf, try reregistering shell32; those entries are supposed to be created by wine.inf when it registers it. --Juan __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

1 0

shell32: shellpath tests failing greatly
by Rolf Kalbermatter 26 Oct '04

26 Oct '04

The recently added tests for shellpath are failing almost completely on my system as it is missing the according registry entries. Not sure how one is supposed to get those registry entries properly. Maybe there is an install script? Although the current documentation talks about an utility wineinstall this seems to have gone completely and I doubt it would take care of those settings. Rolf Kalbermatter

1 0

FW: GetEnvironmentVariableW regression?
by Rolf Kalbermatter 26 Oct '04

26 Oct '04

I suddenly happen to get an error when starting up any application in Wine after having upgraded to current CVS yesterday night from a version a few days ago. The error message is about: "Warning: The specified Windows directory L"c:\\windows" is not accessible" and the same applies for the system directory with the message: "Warning: The specified System directory L"c:\\windows\\system" is not accessible". Looking in the sources I can find the according message in dlls/kernel/process.c and the paths seem to get extracted with GetEnvironmentVariableW(). It seems to me that there is a problem with bad variable expanding or something as the double backslashes in the path in the warning text definitely look wrong. I'm using SUSE Linux 9.0 with XFree 4.3.99. Has this to do with some changes where the .wine/config is supposed to be moved to the registry? If so how do we get the right settings into the registry for common users? Rolf Kalbermatter

1 0

Re: WineHQ: Assorted spelling fixes
by Filip Navara 26 Oct '04

26 Oct '04

Francois Gouget wrote: >Index: wwn/wn20041015_244.xml >=================================================================== >RCS file: /var/cvs/lostwages/wwn/wn20041015_244.xml,v >retrieving revision 1.1 >diff -u -r1.1 wn20041015_244.xml >--- wwn/wn20041015_244.xml 15 Oct 2004 03:59:52 -0000 1.1 >+++ wwn/wn20041015_244.xml 25 Oct 2004 23:10:22 -0000 >@@ -185,7 +185,7 @@ > We discussed Jason Edmeades plans to work on > Direct3D 9 a few weeks ago (see WWN issue > <a href="http://www.winehq.com/?issue=240#DirectX%209%20Roadmap">#240</a>). >-The concensus seemed to be created a shared library between >+The concensus seemed to be ro create a shared library between > s/to be ro/to be to/

2 1

Re: rsaenh
by Juan Lang 26 Oct '04

26 Oct '04

Michael wrote: > There is also a DES implementation in dlls/advapi32/crypt_des.c. > However, this one is not exported by advapi32.dll. I could copy the > code over to dlls/rsaenh, but this would mean unnecessary code > duplication. How are such cases handled in wine typically? They are typically handled by copying the code. If linking between the two requires a private export, then our DLLs can't work with native ones, and that's something we try to avoid. If we use a static library, the number of static libraries can potentially get very large, and the makefiles unmanageable. It's really best to accept code duplication, especially for something like DES that is quite stable. > Although it is of no concern at the moment, another problem will arise > in the future: advapi32 and cryptographic service provider dll's check > each other against tempering by the use of digital signatures in > windows Yes, I know. The functions in advapi32 for verifying a provider always return success at the moment, unfortunately. Maybe with more crypto support we can tackle this, but not yet. > (Probably because of US export restrictions on cryptographic software). I'd be surprised if this were the motivation. US export restriction is on key length, not on algorithm, and the signatures don't say anything about these, just that the files have not been modified and their source can be verified. I expect the motivation is more along the lines of, I'm trusting these DLLs to encrypt my credit card number and whatnot, so how can I trust the DLLs? --Juan __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo

2 1

Re: Re: Problems downloading the RedHat Packages.
by gslink 26 Oct '04

26 Oct '04

I downloaded the Oct. Package from Heanet and got garbage. This isn't surprising if it is not there.

1 0

Wine for Solaris 2.8 assembler problems
by Doug 26 Oct '04

26 Oct '04

I am trying to compile Wine for Solaris to get MCS working for mono. However there are problems getting Wine to work on Solaris 2.8. When first compiling wine, I was thought the errors were caused by using the assembler for Solaris so I changed the as (assembler) to the GNU version. Now I get the following errors. Any ideas of how to fix this? I have heard people getting mono to work on Solaris 2.8 so from what I know it is possible to get Wine working. gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -DBINDIR="\"/usr/l ocal/bin\"" -DDLLDIR="\"/usr/local/lib/wine\"" -D_REENTRANT -fPIC -Wall -pipe -f no-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o port.o port.c {standard input}: Assembler messages: {standard input}:1162: Error: ignoring unrecognized symbol type "" {standard input}:1162: Error: Rest of line ignored. First ignored character is ` 2'.

1 0

Re: rsaenh [beware: 27kB attachment]
by Juan Lang 26 Oct '04

26 Oct '04

Hi Michael, some very brief feedback: 1. MD4, MD5, and SHA1 are now implemented in wine's advapi32. Please use these instead of OpenSSL's. 2. The regression tests should be written so they don't fail if OpenSSL isn't available. 3. Get rid of magic numbers: What do the values 0x36 and 0x5c mean in copy_hmac_info? What is the length 64? Finally, some stylistic nits: 4. Please break long lines. 5. In some of the files you have the incorrect filename in the comments, e.g. dlls/rsabase/handle.c, dlls/rsabse/handle.h 6. Your indentation in some places is inconsistent; you mix spaces and tabs, and that makes it hard for me to guess the appropriate tab size. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

3 2

Functions For Helping FillRect
by William Poetra Yoga H 26 Oct '04

26 Oct '04

FillRect is used in many places for drawing the GUI. But one thing I think many developers miss is that it doesn't fill the right and bottom borders of the rectangle, very much like LineTo doesn't draw the destination point (as per the MSDN docs). But when handling RECT structures we usually think about the objects, not how the objects are going to be painted on-screen. For example, if we wanted to draw a red rectangle at (10,10) with width of 50 pixels and height of 75 pixels, we do (assuming hdc and hbr is already set correctly): RECT r; r.left = 10; r.top = 10; r.right = r.left + 50; r.bottom = r.top + 75; FillRect(hdc, &r, hbr); This _will_ draw it all right, but there are conceptual errors: 1. The rectangle that we have here is not 50x75, but actually 51x76. But FillRect doesn't fill the right and bottom borders, so it appears correctly. 2. If we thought that FillRect fills the whole rectangle, then actually the above code doesn't do what we want; it should actually draw a 51x76 rectangle. So I think we have to make helper functions: RECT ToFill(RECT r) { ++r.right; ++r.bottom; return r; } RECT ToFillLP(LPRECT lpr) { RECT r = *lpr; return ToFill(r); } LPRECT LPToFill(RECT r) { ++r.right; ++r.bottom; return &r; } LPRECT LPToFillLP(LPRECT lpr) { RECT r = *lpr; return LPToFill(r); } So that: 1. Drawing with FillRect will be correct. 2. We can forget about FillRect's peculiar way of doing things. 3. We can concentrate on the actual rectangles. So instead of the above code, we do: RECT r; r.left = 10; r.top = 10; r.right = r.left + 50 - 1; r.bottom = r.top + 75 - 1; FillRect(hdc, LPToFill(r), hbr); What do you all think? Anyway, for LineTo we can just add "+ 1" at the arguments, no need for a helper function. __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo

4 9

Re: wine/dlls/user button.c
by Dimitrie O. Paun 26 Oct '04

26 Oct '04

> The thing is that the old code wasn't entirely correct too. > Here is a test case + fix. Thanks a lot Dmitry, I got carried away with some other stuff. -- Dimi.

1 0

Problems downloading the RedHat packages
by Bill Medland 26 Oct '04

26 Oct '04

I am unable to download the RedHat 20041019 packages; any idea why? (Did they get built?) I can download a SuSE one (well, it at least asks me if I want to save it) but for all the Red Hat ones I've tried the mirror page keeps repeatedly coming up and it never actually tries to download. -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

3 2

Re: unaligned access bug in winspool on sparc
by Juan Lang 26 Oct '04

26 Oct '04

> I just ran across an evil little bug in the > WINSPOOL_GetPrinter_2 function. It looks like this > type of bug could be hiding in other API functions > too. It causes a segmentation fault because of an > unaligned access on Solaris (sparc). Yikes. That's a bad one. The trouble is MS loves this sort of return value. Even if the dll itself doesn't dereference an unaligned pointer, the caller might depending on how things are layed out. The trouble is i386 allows unaligned memory access, so we don't see this sort of thing. If you happen to know how MS handles alignment on platforms that require it, we might be able to fix it. Otherwise it'll have to be case-by-case I'm afraid. --Juan _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

4 4

Re: wine/dlls/user button.c
by Mike McCormack 25 Oct '04

25 Oct '04

Hi Dimi, The following hunk of the patch below breaks the IE install. You should be able to press Alt-A to accept the license in the first dialog, but with this hunk applied it no longer works. Mike Index: wine/dlls/user/button.c diff -u wine/dlls/user/button.c:1.2 wine/dlls/user/button.c:1.3 --- wine/dlls/user/button.c:1.2 Thu Oct 21 11:18:35 2004 +++ wine/dlls/user/button.c Thu Oct 21 11:18:35 2004 @@ -179,10 +224,13 @@ case WM_GETDLGCODE: switch(btn_type) { - case BS_PUSHBUTTON: return DLGC_BUTTON | DLGC_UNDEFPUSHBUTTON; - case BS_DEFPUSHBUTTON: return DLGC_BUTTON | DLGC_DEFPUSHBUTTON; - case BS_RADIOBUTTON: - case BS_AUTORADIOBUTTON: return DLGC_BUTTON | DLGC_RADIOBUTTON; + case BS_AUTOCHECKBOX: return DLGC_BUTTON | DLGC_WANTCHARS; + case BS_AUTORADIOBUTTON: return DLGC_RADIOBUTTON; + case BS_CHECKBOX: return DLGC_BUTTON | DLGC_WANTCHARS; + case BS_DEFPUSHBUTTON: return DLGC_DEFPUSHBUTTON; + case BS_GROUPBOX: return DLGC_STATIC; + case BS_PUSHBUTTON: return DLGC_UNDEFPUSHBUTTON; + case BS_RADIOBUTTON: return DLGC_RADIOBUTTON; default: return DLGC_BUTTON; } Alexandre Julliard wrote: > ChangeSet ID: 14031 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2004/10/04 23:11:13 > > Modified files: > dlls/user : button.c > > Log message: > Dimitrie O. Paun <dpaun(a)rogers.com> > Audit and document button code. > Change [GS]etWindowLong{,Ptr}A to [GS]etWindowLong{,Ptr}W. > Change WM_GETDLGCODE as per the MSDN documentation. > > Patch: http://cvs.winehq.org/patch.py?id=14031 > > Old revision New revision Changes Path > 1.2 1.3 +74 -26 wine/dlls/user/button.c > >

2 1

rsaenh [beware: 27kB attachment]
by Michael Jung 25 Oct '04

25 Oct '04

Hello, I've worked on an OpenSSL based implementation of rsaenh.dll in my spare time over the last three months. Although it is by no means complete, I feel that the coarse structure should be stable by now. The patch is appended to this mail as a gzipped tape archive. I'm aware that small patches are preferable, but I hope someone helps me to get this beast in: Please give me feedback on what remains to be done. If you want to try the patch note the following: - After you have applied the patch you have to run autoheader and autoconf. Then cd dlls ; make_dlls ; cd .. ; configure. - After you have compiled and installed wine, you have to unregister rsabase and register rsaenh (regsvr32 /U rsabase ; regsvr32 rsaenh). rsaenh.dll is meant to replace rsabase.dll sometime (Windows XP also has rsaenh.dll only). - This patch was tested with the attached regression tests and with some MSDN example code. No real application was tested until now. - This code is not secure! The user's persistent private RSA signature and key exchange key pairs are stored in the registry in _plaintext_. Do not use this with your homebanking application ;) - The code depends on CUR_BLOB_VERSION being defined in wincrypt.h. This is implemented in a distinct trivial patch, which I've submitted this morning and which will probably go into CVS tonight (that is if you live in germany ;) - You ain't see a whole lot, if you don't have the openssl headers installed (libssl-dev on debian). The code will compile without, but you'll get a lot of FIXME's and some of the regression tests will fail. Please excuse me for posting a 30kB message. Greetings, Michael

1 0

Problems With MSI
by Joaquín Fernández 25 Oct '04

25 Oct '04

Hello... i am having problems installing program with MSI Installer. When i launch setup.exe, the installer begin the process and when finish of copy files (progress bar is 100%), stay in endless loop. I ran serveral programs using MSI installer but nothing, all hangs at end of copy files. I tested it with WINEDLLOVERRIDES="msi,msiexec.exe=n" too but is equal. Some dll override or other thing? Regards Joaquín P.D.: Wine 20040914 & Mandrake Linux 10.1 Community -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.4 (GNU/Linux) mQFCBEFI/gARAwDd2+ojasT3rCyRktSw+Ix3m+yoxSD0NkpMLlunmJxwvn6wKZVl mDw76/Zu9mqDWWeSGdSl+60T7fDLrJZSEB45O9T5jdujj01GFeer7xuiuHBTFw8o CXqD/hzhqYc46ecAoIQQjZ2qZtOWLPRBbegK/nyOIguNAv9QGiKPLBS8o0ksxEUp EfLAExVmu6Zp693uKGf6XrBWNcLriuwRPr1mjy3N/bhMlqc3vcTeUBwxiUuX5h2P NQgB3d2AbJS6oEvhmZL0Bn/8Ij/MSvVrartmCXuw9eSx0aMC/R7Kw9TtUfxFVUGx fQKwoA9BXNElPLcNohbBS/fH87IMMxCJyn+rmTeNCEcUEQ7UgvVCdlzZ8+L4PdlH qGR81nhZVEwPRnSSesLpSHRC1QQVoceBeb7PICr/b2eZiKMX+bQ+Sm9hcXXDrW4g TWFudWVsIEZlcm7DoW5kZXogUXVpbGVzIDxqb2FxdWluQGNhc2FkZWFsYWJhbnph Lm9yZz6IXgQTEQIAHgUCQUj+AAIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBH 677/q7xL4e15AJwNfSpeaXXMH2EjuKblfeBe51MrUgCcCP5jEnpXrDXLWULIW5yD t6VdHlU= =a8BM -----END PGP PUBLIC KEY BLOCK-----

1 0

Re: WSCEnumProtocols, was _SHExpandEnvironmentStrings() should return input string if no % found to expand?
by Rolf Kalbermatter 25 Oct '04

25 Oct '04

James Hawkins wrote: >> No, it will work. The cast probably there because the original author >> didn't want to write two functions. Instead he added a bool to the >> internal function that specifies whether the buffer is unicode or >> not. The cast is then needed to keep the compiler happy. > >The fact that the structures have a string in them is one issue that >you're ignoring. You can't make a cast from a unicode to an ansi >string just by casting. You have to call RtlMultiByteToWideChar to >convert it. This isn't a problem here since the helper function which is called has as last parameter a boolean telling it if the structure should be interpreted as the ANSI or Unicode version. While this may look asthetically wrong it is technically correct as long as the strings are embedded as pointers instead of inlined. There is a string inlined in the structure but it is at the end of the structure only so even there it is not necessarily a problem although the internal helper function needs to take extra care to get it right and in that it might be a better idea to just implement the Unicode version and convert for the ANSI one. >The major problem that you're ignoring is that you're >casting from one kind of struct to another, and they aren't the same. >The cast wont work. You would have to individually pull out the >relevant fields into a new PROTOCOL_INFO struct like I said in the >last post. If by original author I'm assuming you're talking about >the author of the spec file. In which case, there was only one >function in the spec file to begin with, because all functions only >have one in the spec file originally until someone stubs out that >function and finds out that it needs and A and a W...which is why I >didn't want my patch committed. This would be indeed the real problem if it was the case, but (from my SDK headers): int WSPAPI WSCEnumProtocols(IN LPINT lpiProtocols, OUT LPWSAPROTOCOL_INFOW lpProtocolBuffer, IN OUT LPDWORD lpdwBufferLength, OUT LPINT lpErrno); int WSAAPI WSAEnumProtocolsA(IN LPINT lpiProtocols, OUT LPWSAPROTOCOL_INFOA lpProtocolBuffer, IN OUT LPDWORD lpdwBufferLength); There is no ANSI version defined for the WSC function. This means either of two things: It is on all versions of Windows Unicode or it is very much like many Shell functions really ANSI on non NT systems while NT systems implement it as Unicode. Seeing that MSDN claims this to be supported on even Win95 I tend to believe the second one but only tests will show. The fact that modern SDK headers don't contain any indication of ANSI support means nothing as Microsoft has removed support for developing Win9x application from many SDK headers and MSDN. The problem seems to me rather that even the WSAEnumProtocols function casts the WSAPROTOCOL_INFOA/W structure pointer into PROTOCOL_INFOA and since they have indeed a completely different layout we are basically causing big trouble. I doubt that WSAEnumProtocols ever did work properly unless MS has at some point changed the second parameter of the function. Once this has been fixed, the implementation as suggested by Hans should actually work fine. Rolf Kalbermatter

1 0

Re: Fully Revised Wine User Guide Introduction
by Francois Gouget 25 Oct '04

25 Oct '04

On Mon, 25 Oct 2004, Francois Gouget wrote: > On Fri, 22 Oct 2004, Scott Ritchie wrote: > [...] >> Unlike my previous patch, this one should be properly formatted, > > It still had very long lines. So here's a line-wrapped version of the patch: > > Changelog: > > * documentation/introduction.sgml > > Scott Ritchie <scott(a)open-vote.org> > Revised Wine User Guide Introduction Sorry for this. I was without Internet access for a while and our emails crossed. Hmmm, I wonder... does this double the chances of the patch getting accepted?<g> -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy

1 0

d3drs_multisampleantialias: check for it?
by Devils Cry 24 Oct '04

24 Oct '04

Hi again... :/ ^^ So im now moving for the multisampleantialias call... ive found the gl_multisample_arb function to be matching, so far, so good. Now while googling for it i only found code examples which check whether multisampling is supported before it is activated. My question: do i need this? I found no other call in the d3d8lib which asks for its extension the way i found it (http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=46). Theres also another problem: the multisampling has to be turned off after its done, turned on again if something is drawn and after this turned off again (at least i understood it that way...). Is it enough to simply turn it on? And if not, how should i do this??? Thx in advance Nikolas

2 1

Re: _SHExpandEnvironmentStrings() should return input string if no % found to expand?
by Hans Leidekker 24 Oct '04

24 Oct '04

On Sunday 24 October 2004 01:35, James Hawkins wrote: > The reason why I said to ignore this patch is because there has to be > both an A and a W version of it. I'm pretty sure that this cast: No, I believe this is an exception. I assume that the spec file is correct in that there are no A and W versions of this function in shell32, it's just WSCEnumProtocols(). > (PROTOCOL_INFOA *)buffer > from a LPWSAPROTOCOL_INFOW structure isn't going to work. No, it will work. The cast probably there because the original author didn't want to write two functions. Instead he added a bool to the internal function that specifies whether the buffer is unicode or not. The cast is then needed to keep the compiler happy. > WSAPROTOCOL_INFO and PROTOCOL_INFO don't even have the same fields: No, but WSCEnumProtocols() wants WSAPROTOCOL_INFOW structures, just like WSAEnumProtocolsW(). Quote from MSDN: int WSCEnumProtocols( LPINT lpiProtocols, LPWSAPROTOCOL_INFOW lpProtocolBuffer, LPDWORD lpdwBufferLength, LPINT lpErrno ); -Hans

2 1

Re: Patch : dlls/ntdll, dlls/kernel, dlls/user
by Dmitry Timoshkov 24 Oct '04

24 Oct '04

"Peter Quiring" <pquiring(a)hotmail.com> wrote: > I've added some stub's for 39 functions that I've come accross > while using Wine. I often try to use native DLLs as much as > possible but can't always unless these 39 stubs are added. > I've also attached a txt file listing the functions I've added. That's usually considered a bad idea to add stubs to .spec files if there is no real need for that. And that's really the case, since: 1. there is no real difference between a missing API and a stubbed in the .spec file one 2. using native dlls "as much as possible" is not encouraged in Wine at all, and especially for Wine *development* 3. you can't use native versions of ntdll, kernel32 and user32 in any case 4. Adding stubs for NT/win2k/win2k3 only APIs will make the things much worse for some apps, because they could start think that they are running under those platforms by checking presence of that APIs -- Dmitry.

1 0

OpenGL Extension Viewer
by Devils Cry 24 Oct '04

24 Oct '04

Hi there everybody! While browsing the web i found a little tool which i expect to be quite helpfull: the opengl extension viewer. Though its written for windows, it runs perfectly on wine and allows people working on d3d and so on to have a quick overview of the functions. With kind regards Nikolas

2 2

DLL search order
by Kenneth Porter 24 Oct '04

24 Oct '04

I know this has to be a FAQ, but I'm not finding it. I want to test a custom version of kernel32.dll without bothering other wine users on the box. What do I need to do to make an app search the local directory for it instead of using the one in /usr/lib/wine?

2 1

Re: Bug in recent shellpath.c change, with fix?
by Juan Lang 24 Oct '04

24 Oct '04

This certainly is a bug. Your patch fixes it, but I think it might be better (there's an unnecessary copy left, and I wonder whether _SHExpandEnvironmentStrings should be called at all). I'll submit what I think is a better patch shortly. Thanks, --Juan --- Dan Kegel <dank(a)kegel.com> wrote: > Hey, I think I found a bug in your recent patch. > Could you have a look and maybe approve my > patch or submit the real fix? > The app I was tryiing to install was Google Desktop > Search, > which is a free download from > http://desktop.google.com > > Thanks, > Dan > > -------- Original Message -------- > Subject: _SHExpandEnvironmentStrings() should return > input string if no % found to expand? __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

1 0

bug 2170: can't install Office '97
by Dan Kegel 24 Oct '04

24 Oct '04

http://bugs.winehq.org/show_bug.cgi?id=2170 This bug is marked 'closed', but it's still happening for me with today's CVS. Anyone know what's up with this? Thanks, Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

2 2

RE: The wine user guide: an idea
by Scott Ritchie 24 Oct '04

24 Oct '04

Thanks for you comment. I've taken up the task of rewriting alot of the User Guide at the moment, and revising the Using Wine section may be the most important next step after the rewrite of the Intro. > What I would like is a section with common use cases of wine and > step-by-step instructions for each of them. It shouldn't be long - it > should be mostly links to other parts of the user guide. I think of > something like that... Not a bad idea, I'll certainly keep it in mind as I go through the other chapters. -Scott Ritchie

2 1

Re: Fix regression in CreateProcess
by Mike McCormack 24 Oct '04

24 Oct '04

Eric Pouech wrote: > As Mike reported, there was a bug in CreateProcess introduced with the > runtime info handling. > This patch should take care of it. > A+ Hi Eric, This patch fixes the problem! thanks for your help! Mike

1 0

The wine user guide: an idea
by Noam Raphael 23 Oct '04

23 Oct '04

Hello, First, let me apologize: I am not familiar with wine, and I didn't make a decent research before I posted this message. I just read through the wine user guide, and though of something that could be nice for a user as lazy as I am. Since the introduction asked for comments, I comment. What I would like is a section with common use cases of wine and step-by-step instructions for each of them. It shouldn't be long - it should be mostly links to other parts of the user guide. I think of something like that: CASE: I have a working windows machine, and I would like to use the installed programs from linux. (which happens to be my situation...) WHAT TO DO: 1. Install wine (see ...) 2. Copy all files into your home dir, for example, ~/wine/C 3. Run winecfg (see ...) ... This would give the users (or at least me) a nice warm feeling that what I want to do was already done and isn't so complicated (I hope - I haven't tried it yet). Have a good week, Noam Raphael P.S. if you reply, can you please CC me? I'm not a member of wine-devel.

1 0

Re: wine devel documentation reorganization
by Mike Hearn 23 Oct '04

23 Oct '04

Spiffy. As part of my ongoing quest to make Wine hacking less scary, I've written some docs on SEH. I'll submit them to the kernel modules section when I get net access back. Just a heads up in case anybody else was thinking of covering that topic. Eric Pouech wrote: > As posted on wine-devel, here's a patch to reorganize the Wine > Developer's Guide. > It's gzip:ed because of the size (160KB). > Here's the changelog for those who don't want to open the gzip: > > A+ > Reorganizing wine-devel: > - killing the advanced part > (and moving its chapters in both developing Wine and Wine > archi parts) > - creating a new book on coding practices > from i18n.sgml, patches.sgml and porting.sgml (developing > Wine) > - creating a new book on some debugging strategies > from the old advanced book and cvs-regression.sgml > (developing Wine) > - creating a new book on the kernel modules (NTDLL & KERNEL32) > from architure.sgml / related DLLs and > address-space.sgml, console.sgml, threading.sgml > - creating a new book on the windowing > from architure.sgml / USER32 and related > - creating a new book on the graphical parts > from architure.sgml / GDI32 and related > Other changes: > - removed list of DLLs and their role (from the > modules overview) > - removed in X11 keyboard mapping section the part related > to submit a patch

2 1

Re: Fully Revised Wine User Guide Introduction
by Francois Gouget 23 Oct '04

23 Oct '04

On Fri, 22 Oct 2004, Scott Ritchie wrote: > The version 0.9 todo list (bug 85) specifies the need for a rewritten > intro to the Wine User Guide. > > This patch is that rewritten intro. It rewords things to make Wine > easier to understand for the new user, gives it a more professional > look, and removes some outdated information. Unlike my previous patch, > this one should be properly formatted, It still has awfully long lines. Are you sure you sent the right patch? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly.

1 0

Program To Check System Metrics
by William Poetra Yoga H 23 Oct '04

23 Oct '04

Hi guys (& gals), if you remember I was working on the caption buttons. I haven't submitted the patch yet (it's still in progress) and I wish to know the relations between system metrics, because I think they are very closely related to drawing on the screen, like borders, sizes, etc. I'm writing an app here, called metrics, but since this is my first Win32 program, I've encountered many problems (and solved only a few :-P). I've read bits of theForge's Win32 tutorial at www.winprog.org (I got the link from Wine), but I just can't figure out how to handle the "Refresh" and "Save" buttons properly. "Refresh" is for refreshing (regetting) the metric values, and save is for saving the values to a file. Please help me with this, and be informed that this is my first Win32 app, so bear with me... File is attached. _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

1 0

IE6 install Regression
by Mike McCormack 23 Oct '04

23 Oct '04

Hi Eric, The following patch causes the IE6 installer to crash. Thanks to Rob for figuring out which patch caused the problem very quickly :) Mike Log message: Eric Pouech <pouech-eric(a)wanadoo.fr> - msvcrt: the file descriptors are now inherited between parent/child processes - kernel32.CreateProcess: make use of the *reserved2 fields for C-RunTime data inheritance http://www.winehq.org/hypermail/wine-cvs/2004/09/0039.html ... 001f:Call kernel32.GetStartupInfoA(77adfca4) ret=500b34f6 001f:Ret kernel32.GetStartupInfoA() retval=77adfca4 ret=500b34f6 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x500b354f trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=780704e4 trace:seh:EXC_RtlRaiseException eax=00570000 ebx=77efd6e8 ecx=00000040 edx=77b004e0 esi=780704e4 edi=500c7ab8 trace:seh:EXC_RtlRaiseException ebp=77adfcec esp=77adfc98 cs=0073 ds=007b es=007b fs=0033 gs=0000 flags=00210 202 trace:seh:EXC_CallHandler calling handler at 0x77c0e240 code=c0000005 flags=0

2 3

Re: Fix for bug 824 - proper handling of REG_MULTI_SZ
by Alexandre Julliard 23 Oct '04

23 Oct '04

Randy Galbraith <randy.galbraith(a)cox.net> writes: > This proposed patch addresses the concern raised by bug 824. This > patch changes the handling of REG_MULTI_SZ from REG_SZ to REG_BINARY. Do you actually have an app that depends on this? I agree that in theory we should preserve the data exactly, but this means giving up on an easily editable registry format, so it should be done only if something really needs it. -- Alexandre Julliard julliard(a)winehq.org

3 5

Re: winapi_check and 16 bit -register functions
by Alexandre Julliard 22 Oct '04

22 Oct '04

Francois Gouget <fgouget(a)free.fr> writes: > Yesterday's winapi_check path warns about 32 bit -register functions > that are implemented by stdcall functions, but not about 16 bit > -register functions implemented by stdcall functions. The reason is > that for the latter the calling convention is set to 'pascal' or > 'pascal16' in winapi_check. However I suspect these too should be > implemented as cdecl. They could, but that will require some changes to the .spec.c code, right now the calling convention is based on the type specified in the spec file, so pascal register functions have to be WINAPI. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: [dx9-12] Major change to desgin
by Alexandre Julliard 22 Oct '04

22 Oct '04

"Ann and Jason Edmeades" <us(a)the-edmeades.demon.co.uk> writes: > I have changed the design so only the Direct3D<interface><8/9> ones extend > IUnknown, and so there is no reference counting of the IWineD3D > objects. I don't think that's a good idea. If you are using COM interfaces then you need to use them the COM way, this means IWineD3D should derive from IUnknown and freeing it should be done through the Release method. If you don't want to use standard COM then don't declare COM interfaces at all, create your own mechanism. > Instead, when any Direct3D<interface><8/9> is Released to zero, then it > calls a Free method in its WineD3D equivalent interface. I also changed the > IWineD3D interface to contain, as a void *, a pointer to its 'parent' (by > which I mean the Direct3D8/9 interface) plus a function (GetParent) which > returns that pointer. This is bad too, you shouldn't use void*, you should use proper types, at the very least IUnknown*, but preferably define an IWineD3DUser interface or something like that. -- Alexandre Julliard julliard(a)winehq.org

2 4

Wine on OpenBSD
by Sascha Hanse 22 Oct '04

22 Oct '04

> >> I just tried to install the recent Wine-tarball (20041019) on my >> OpenBSD 3.6. First I had to remove kthread.c:275: the RFTHREAD flag. >> Then the'make depend && make' worked properly but the make install >> first fails with: >> >> /usr/bin/install -c serialui.dll.so >> /usr/local/lib/wine/serialui.dll.so cd `dirname setupapi/__install__` >> && make install gcc -g -O2 -o install install.c > >Your make tries to build the 'make install' target from install.c, >that won't work of course. I guess we'll have to rename that file, >unless OpenBSD make has an equivalent of the .PHONY target. > >-- >Alexandre Julliard >julliard_at_winehq.org Hi Julliard, thank you for your response. Could you tell me when or how this can be done? -- Anyone who considers arithmetical methods of producing random digits is, of course, in a state of sin. --John von Neumann (1951)

2 2

Re: Add list for monitoring Appdb
by Jeremy Newman 22 Oct '04

22 Oct '04

I'm holding off on this patch until I get more comments on why we should or shouldn't create yet another mailing list. My personal opinion is that we don't need a mailing list for this. The change emails can go straight to the app owners themselves, and possibly to the appdb admins. I know I wouldn't care seeing update emails for apps I don't maintain. Just my opinion. I will create this list if there is enough interest in it. On Wed, 2004-10-13 at 10:38 -0700, Tony Lambregts wrote: > I am working on a series of changes that will let changes to the appdb > be emailed to administrators, application owners and other users. > > This will be similar to how bugzilla does it. > > When someone changes an application an email listing the changes gets > sent to the following > > - Appdb administrators. > - Application owners. > - Aplication monitors. > > One of the things that I think is a repository the way wine-bugs(a)winehq.org > does for bugzilla > > I need Jeremy to set up the email account and the mailman account. > > Change log: Add link for monitoring changes to application database > > files changed: lostwages/templates/en/forums.template > > > Tony Lambregts > > Index: forums.template > =================================================================== > RCS file: /home/wine/lostwages/templates/en/forums.template,v > retrieving revision 1.16 > diff -u -r1.16 forums.template > --- forums.template 15 Sep 2004 20:05:31 -0000 1.16 > +++ forums.template 13 Oct 2004 15:46:24 -0000 > @@ -97,6 +97,13 @@ > <a href="http://bugs.winehq.org/">Bug Tracking Database</a>. > > <li> > + [<a href="http://www.winehq.org/mailman/listinfo/wine-appdb">(Un-)Subscribe</a>] > + [<a href="http://www.winehq.org/hypermail/wine-appdb/">Archive </a>] > + <a href="mailto:wine-appdb@winehq.org">wine-appdb(a)winehq.org</a> > + A low traffic (2/day) read-only list for monitoring submissions to the > + <a href="http://appdb.winehq.org/">Application Database</a>. > + > + <li> > [<a href="http://www.winehq.org/mailman/listinfo/wine-tests-results">(Un-)Subscribe</a>] > [<a href="http://www.winehq.org/hypermail/wine-tests-results/">Archive</a>] > <a href="mailto:wine-tests-results@winehq.org">wine-tests-results(a)winehq.org</a> > > >

3 2

Re: shellpath.c: Avoid copying invalid data on error
by Alexandre Julliard 22 Oct '04

22 Oct '04

Juan Lang <juan_lang(a)yahoo.com> writes: > The following is a better patch, I think, in that > - it doesn't add a break statement to the default case > (some compilers warn on this) I seriously doubt that, what compiler does this for you? It's much better practice to always add break to all cases, otherwise when someone adds some code at the end of the switch they will forget to add a break to the previous case. > - WCHAR szBuildPath[MAX_PATH], szTemp[MAX_PATH]; > + WCHAR szBuildPath[MAX_PATH], szTemp[MAX_PATH] = { 0 }; This fills the whole buffer with zeroes, that's not really needed. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: dlls/shlwapi PathIsValidChar
by Alexandre Julliard 22 Oct '04

22 Oct '04

Ge van Geldorp <gvg(a)reactos.com> writes: > Did this patch: http://www.winehq.org/hypermail/wine-patches/2004/09/0446.html > fall through the cracks or is it not acceptable? I think a lookup table would be more elegant (and faster...) -- Alexandre Julliard julliard(a)winehq.org

1 0

unaligned access bug in winspool on sparc
by Eric Frias 22 Oct '04

22 Oct '04

I just ran across an evil little bug in the WINSPOOL_GetPrinter_2 function. It looks like this type of bug could be hiding in other API functions too. It causes a segmentation fault because of an unaligned access on Solaris (sparc). This function packs a PRINTER_INFO_2 structure and all of its variable-length fields into one contiguous block of memory. The structure is first, then several strings, and then a DEVMODE structure. The problem is that because the strings can be any length, the DEVMODE structure itself could be placed at an unaligned (odd) address. So on our system, wine runs correctly if we only have printers with an even number of letters in their name in the printcap file, but it crashes if any have an odd number of letters in their name. I put in a quick hack that aligns it to a 4-byte boundary. I think a two-byte boundary would suffice, but I decided to err on the safe side since I wasn't sure. I inserted the following block near line 1822 in info.c: ------ { int bytesOfPadding = (4 - (*pcbNeeded % 4)) % 4; if (space && bytesOfPadding <= left) { ptr += bytesOfPadding; left -= bytesOfPadding; } else space = FALSE; *pcbNeeded += bytesOfPadding; } ------ right before the line: ------ if(WINSPOOL_GetDevModeFromReg(hkeyPrinter, Default_DevModeW, ptr, left, &size, unicode)) { ----- What is the correct way to align this structure? Are there any macros that specify the necessary alignment for each architecture? I'm also wondering if there are any other functions that are likely to contain the same bug. Thanks, Eric

1 0

Re: msdn: d3drs_wrapn[0-7] ???
by Devils Cry 22 Oct '04

22 Oct '04

Well, i aplied the changes raphael suggested and although i dont understand what they do they work :D @David Welch Yeah, already found that out, but thx anyway, i think i understand it a bit better now :) /Me moving on for validateshaders... lets see what that gets :D Cheers Nikolas

1 0

Re: Add function prototypes to wineconf
by Chris Morgan 22 Oct '04

22 Oct '04

I think the idea is that we should move the functionality of wineconf into winecfg so winecfg should be able to autodetect and import the configurations from existing windows installs. Wineconf hasn't been well maintained lately so maybe now is a good time to encourage people to implement that functionality in winecfg by removing it ;-) Chris > > From: Francois Gouget <fgouget(a)free.fr> > Date: 2004/10/22 Fri PM 12:21:32 EDT > To: wine-patches(a)winehq.org > Subject: Add function prototypes to wineconf > > > This tool generates a Wine configuration containing [Drive] sections! > In other words it's pretty outdated. It was last updated almost 18 > months ago! > > Is it even worth keeping? Maybe the best thing to do is to do a cvs > delete on it? > > In case we want to keep it I added function prototypes. However I did > not change its behavior any further. On my machine it runs but perl > issues a couple of warnings... the same one it was issuing before I ever > touched it. > > > Changelog: > > * tools/wineconf > > Add function prototypes. > Change the way functions are called and their declaration order so > perl can check the prototypes. > > > -- > Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ > "Lotto: A tax on people who are bad at math." -- unknown > "Windows: Microsoft's tax on computer illiterates." -- WE7U >

1 0

modal message box fixme
by Ivan Leo Puoti 22 Oct '04

22 Oct '04

I've written an app that calls a modal message box, if the uType parameter passed to MessageBox is MB_TASKMODAL or MB_SYSTEMMODAL a fixme is printed, but if it's MB_APPLMODA wine doesn't print a fixme. Is the attached fix correct (It works for me)? Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

2 1

Using Microsoft C++ Toolkit with Wine
by Dan Kegel 22 Oct '04

22 Oct '04

I've posted about this before, but never really tied things up in a neat package, so: Here's a document that describes how to use Microsoft C++ Toolkit on Linux to build Windows programs: http://www.kegel.com/wine/cl-howto.html I hope that helps a few people. I certainly find it convenient when writing Wine conformance tests. To build a Wine conformance test standalone, I start the test off with the lines #include <stdarg.h> #include <windef.h> #include <winbase.h> #ifndef STANDALONE #include "wine/test.h" #define ok2 ok #else #include <assert.h> #include <stdio.h> #define START_TEST(name) main(int argc, char **argv) #define ok(condition, msg) \ do { \ if(!(condition)) \ { \ fprintf(stderr,"failed at %d, msg:" msg "\n",__LINE__); \ exit(0); \ } \ } while(0) #define ok2(condition, msg, arg) \ do { \ if(!(condition)) \ { \ fprintf(stderr,"failed at %d, msg:" msg "\n",__LINE__, arg); \ exit(0); \ } \ } while(0) #define todo_wine #endif #include <winerror.h> and use ok2 for those calls to ok that have one argument after the format string. That .c file should be fine for either normal or standalone use. (I haven't tested ok2 yet under the normal wine build, but I think #define ok2 ok should work.) Then I can compile with cl -DSTANDALONE -D_X86_ myfile.c and get a quickie Windows executable for just that test file. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

1 0

Re: Cleanup config
by Alexandre Julliard 22 Oct '04

22 Oct '04

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > [wine] > -"Windows" = "c:\\windows" > -"System" = "c:\\windows\\system" > -"Temp" = "e:\\" > -"Path" = "c:\\windows;c:\\windows\\system;e:\\;e:\\test;f:\\" > -"Profile" = "c:\\windows\\Profiles\\Administrator" This is OK except for the windows dir, that one is still being used by the registry code. -- Alexandre Julliard julliard(a)winehq.org

2 2

wine 1019 build fails at wine_marlett.sfd
by sean 22 Oct '04

22 Oct '04

I'm trying to buid wine-10192004. I've installed fontforge-10142004. The wine build fails here: fontforge -script ../fonts/genttf.ff wine_marlett.sfd Copyright (c) 2000-2004 by George Williams. Executable based on sources from 10:52 14-Oct-2004. FontForge used to be named PfaEdit. make[1]: *** [wine_marlett.ttf] Segmentation fault This not a machine error. The sigsegv happens if I execute this command in the build directory. Before that i get: fontforge -script ../fonts/genttf.ff wine_courier.sfd Copyright (c) 2000-2004 by George Williams. Executable based on sources from 10:52 14-Oct-2004. FontForge used to be named PfaEdit. LD_LIBRARY_PATH="../libs/unicode:$LD_LIBRARY_PATH" ../tools/sfnt2fnt wine_courier.ttf 13 1252 96 128 ../tools/fnt2fon wine_courier-1252-96-13.fnt wine_coure.fon Wine Courier 10 pts 96x96 dpi LD_LIBRARY_PATH="../libs/unicode:$LD_LIBRARY_PATH" ../tools/sfnt2fnt wine_courier.ttf 13 1250 96 128 ../tools/fnt2fon wine_courier-1250-96-13.fnt wine_couree.fon Wine Courier 10 pts 96x96 dpi LD_LIBRARY_PATH="../libs/unicode:$LD_LIBRARY_PATH" ../tools/sfnt2fnt wine_courier.ttf 13 1251 96 128 Missing glyph for char 0402 Missing glyph for char 0403 Missing glyph for char 0453 Missing glyph for char 0409 Missing glyph for char 040a Thanks for any help. sean

1 0

Re: Add list for monitoring Appdb
by Tony Lambregts 22 Oct '04

22 Oct '04

Quoting Chris Morgan I was intending to submitt a patch to allow each user to turn on emails. By default no one would recieve emails. If administrators turn on the switch then they would recieve emails from any app that changed. For application Owners/ Maintainers, they would recieve emails when something changed for thier app. The idea for a mailing list archive is so we have a record of what was changed the same way that we have for bugzilla. Mostly it is a safegaurd for when we open up the DB to individual app Owners/maintainers. > > Maybe there should be an option for an admin to add themselves to both a > global and a app specific list so when things change for an app an email is > sent to all people on the global list and then all people on the app specific > list. This lets people opt-in if they want to get the emails. > > Chris > > > On Thursday 21 October 2004 3:58 pm, Jeremy Newman wrote: > > I'm holding off on this patch until I get more comments on why we should > > or shouldn't create yet another mailing list. > > > > My personal opinion is that we don't need a mailing list for this. The > > change emails can go straight to the app owners themselves, and possibly > > to the appdb admins. I know I wouldn't care seeing update emails for > > apps I don't maintain. Just my opinion. > > > > I will create this list if there is enough interest in it. > > > > On Wed, 2004-10-13 at 10:38 -0700, Tony Lambregts wrote: > > > I am working on a series of changes that will let changes to the appdb > > > be emailed to administrators, application owners and other users. > > > > > > This will be similar to how bugzilla does it. > > > > > > When someone changes an application an email listing the changes gets > > > sent to the following > > > > > > - Appdb administrators. > > > - Application owners. > > > - Aplication monitors. > > > > > > One of the things that I think is a repository the way > > > wine-bugs_at_winehq.org does for bugzilla > > > > > > I need Jeremy to set up the email account and the mailman account. > > > > > > Change log: Add link for monitoring changes to application database > > > > > > files changed: lostwages/templates/en/forums.template > > > > > > > > > Tony Lambregts > > > > > > Index: forums.template > > > =================================================================== > > > RCS file: /home/wine/lostwages/templates/en/forums.template,v > > > retrieving revision 1.16 > > > diff -u -r1.16 forums.template > > > --- forums.template 15 Sep 2004 20:05:31 -0000 1.16 > > > +++ forums.template 13 Oct 2004 15:46:24 -0000 > > > @@ -97,6 +97,13 @@ > > > Bug Tracking Database. > > > > > > <li> > > > + [<a > > > href="http://www.winehq.org/mailman/listinfo/wine-appdb">(Un-)Subscribe</ > > >a>] + [<a href="http://www.winehq.org/hypermail/wine-appdb/">Archive > > > </a>] + <a > > > href="mailto:wine-appdb_at_winehq.org">wine-appdb_at_winehq.org</a> + A > > > low traffic (2/day) read-only list for monitoring submissions to the + > > > Application Database. + > > > + <li> > > > [<a > > > href="http://www.winehq.org/mailman/listinfo/wine-tests-results">(Un-)Sub > > >scribe</a>] [<a > > > href="http://www.winehq.org/hypermail/wine-tests-results/">Archive</a>] > > > <a > > > href="mailto:wine-tests-results_at_winehq.org">wine-tests-results_at_winehq.org > > ></a> > > -- > Tony Lambregts > > -- Tony Lambregts

2 1

Re: d3drs_wrap[0-7] ???
by N. Dahn 21 Oct '04

21 Oct '04

Hopefully this isnt the case, and according to this http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dx8_c/dire… i have luck for this time i think. :) Comments? Okay, i think i got one step further: on gamedev.net i found the suggestion to use glTexParameteri(GL_TEXTURE_2D, TEXTURE_WRAP_U/V/W, wrapParm). Besides, could this also be an 3D Texture? I think I worked it out and im going to try it out now, but theres one thing bothering me: as mentioned earlier in d3d there exists the d3dwrapcoord_3 flag which wraps textures through the 4th dimension (that should be time). However, i was unable to find _anything_ going into that direction in opengl so i stubbed it out for now. Does anybody know how to proceed with this? BTW, is there a way to figure out what an undocumented function does? (namely d3drs 172 and 173) Cheers Nikolas

3 3

Winedbg: watchpoints broken?
by Walt Ogburn 21 Oct '04

21 Oct '04

Hi, Winedbg's watchpoints don't seem to work for me: when I try to watch a memory location, winedbg responds that a watchpoint has been set at a different, always constant location (I suspect this is actually in winedbg's memory space). Nothing happens when the location I was trying to watch changes. Here is a cut-and-paste from my winedbg session. I try to watch memory location 0x0041a5ec, but I can set other breakpoints and see that the value has changed without the watchpoint taking effect. ----------------------------------------------------------------------- Wine-dbg>run In 32 bit mode. 0x4049a81f start_process+0xcf [/home/reuben/project/wine/wine/dlls/kernel/../../include/winternl.h:1249] in kernel32: jmp 0x4049a815 start_process+0xc5 [/home/reuben/project/wine/wine/dlls/kernel/process.c:1022] in kernel32 1249 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } 1249 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } Wine-dbg>watch *0x0041a5ec Watchpoint 1 at 0x405ae8c4 Wine-dbg>x 0x0041a5ec 00000000 Wine-dbg>break *0x004130ec Breakpoint 2 at 0x004130ec Wine-dbg>cont fixme:ole:CoRegisterMessageFilter stub Stopped on breakpoint 2 at 0x004130ec Wine-dbg>x 0x0041a5ec 403e9d40 Wine-dbg>cond 2 $ecx==0x10 Wine-dbg>cont Stopped on breakpoint 2 at 0x004130ec Wine-dbg>x 0x0041a5ec 00000000 Wine-dbg>info break Breakpoints: 2: y 0x004130ec (1) stop when ($ecx == 16) Watchpoints: 1: y 0x405ae8c4 on 4 bytes (W) -------------------------------------------------------------------------- The fact that winedbg thinks the watchpoint is 0x405ae8c4 is especially puzzling, but it's entirely possible that the confusion lies with me rather than winedbg. Thanks, Walter

2 5

Re: wine/ programs/winhelp/hlp2sgml.c dlls/winsock ...
by Vincent Béron 21 Oct '04

21 Oct '04

Le mar 19/10/2004 à 19:55, Alexandre Julliard a écrit : [snip] > 1.161 1.162 +2 -2 wine/dlls/winsock/socket.c This change removed LONG to put long instead, which is not the same size on Alpha between Windows and Unix. LONG can be made the same size on both. > 1.32 1.33 +2 -2 wine/dlls/rpcrt4/rpc_server.c Same thing here. Shouldn't we use LONG in both places? Vincent

2 1

Re: winedos: per drive current directory
by Eric Pouech 21 Oct '04

21 Oct '04

Markus Amsler a écrit : > Microsoft's Segmented-Executable Linker Version 5.10 shipped with QBasic > 7.1 needs per drive current directory. > > Changelog > * Implement per drive current directory. IMO, you should keep the part of the note dealing with where to store the list of current drives (as it's not done yet in DOS style) A+

1 0

Graphic problems with wxtide32
by Uwe Bonnes 21 Oct '04

21 Oct '04

Hallo, wxtide (http://www.wxtide32.com/download.html) is an opne source program that shows graphic problems. For example, when started, a left click in the tide window brings up a gray window, where some text should appear. This window is managed by following code: static void open_popup(DWORD mouseXY, char *text) { int mouseX, mouseY, cxscreen, cyscreen, startX, startY, side; PAINTSTRUCT ps; RECT purc = {0,0,0,0}; HFONT oldfont; #define POPUP_BORDER 1 close_popup(); // Open window with dummy position and size to get device context popup = CreateWindow("STATIC", "", WS_POPUP|WS_VISIBLE,//|WS_BORDER, 10,10,250,50, window, NULL, t_hinst, NULL); BeginPaint(popup,&ps); oldfont = SelectFont(ps.hdc,gfont); // Get extents for this text DrawText(ps.hdc, text, strlen(text), &purc, DT_CALCRECT); purc.right += POPUP_BORDER*2; purc.bottom += POPUP_BORDER*2; mouseX = LOWORD(mouseXY); mouseY = HIWORD(mouseXY); cxscreen = GetSystemMetrics(SM_CXSCREEN); // cyscreen = GetSystemMetrics(SM_CYFULLSCREEN); if (side=(cxscreen > (mouseX + winX + purc.right))) startX = mouseX + winX; else startX = mouseX + winX - purc.right; if (0 < (mouseY + winY - purc.bottom)) startY = mouseY + winY - purc.bottom; else startY = mouseY + winY; // Now make window the right size and in the right place MoveWindow(popup,startX,startY,purc.right,purc.bottom,FALSE); // SetTextColor(ps.hdc,fgtext_color); // SetBkColor(ps.hdc,RGB(255,255,255)); FillRect( ps.hdc, &purc, GetStockObject(WHITE_BRUSH)); FrameRect(ps.hdc, &purc, GetStockObject(BLACK_BRUSH)); purc.left += POPUP_BORDER; purc.top += POPUP_BORDER; purc.right -= POPUP_BORDER; purc.bottom -= POPUP_BORDER; DrawText(ps.hdc,text,strlen(text),&purc, DT_WORDBREAK|(side? DT_LEFT : DT_RIGHT)); SelectFont(ps.hdc,oldfont); EndPaint(popup,&ps); } Any idea what wine is doing wron? Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Re: msdn: d3drs_wrap[0-7] ???
by Devils Cry 21 Oct '04

21 Oct '04

> yes, its strange. having a real demo of use should help a lot Okay, i tested what i did with a game but the game doesnt call it directly so i guess its right what you said, its done be the d3dtss_address thing. Ill have a _very_ close look at it as my understanding of c isnt that deep atm... > Hmm, i don't think it match exactly OpenGL WRAP specs > but i haven't understand d3d wrapping specs, and i havent seen any > game using it to test :( Try Chaos Legion, its really fun and it uses the wrap calls ;D BTW, for ommiting redundances, ive currently done the d3drs_lineantialias and the ive stubbed out the d3drs_debugmonitortoken call, i think we dont need it. Regards, Nikolas

1 0

Toolbar control Messages causing WM_PAINT
by Thorsten Kani 21 Oct '04

21 Oct '04

I did a quick check of ToolbarMessages that cause WM_PAINT instantly: TB_CHANGEBITMAP TB_CHECKBUTTON TB_DELETEBUTTON TB_ENABLEBUTTON TB_INDERTERMINATE TB_MARKBUTTON TB_PRESSBUTTON TB_SETBITMAPSIZE TB_SETBUTTONSIZE TB_SETBUTTONWIDTH TB_SETCOLOSCHEME TB_SETIMAGELIST TB_SETINDENT TB_SETINSERTMARK TB_SETMAXTEXTROWS TB_SETSTATE I left some the remaining ToolbarMessages untestet because i did not know how to send them correcty with controlspy. other Messages showing up and caused Paint: WM_UNKNOWN(128) WM_CHILDACTIVATE WM_ERASEBKGND WM_MOUSELEAVE(borders) probably this is not everything you need. (: Tho

1 0

Winecfg resources
by David Kredba 21 Oct '04

21 Oct '04

Hello all. There are disabled other than English resources in the wincfg.rc file. I finished tranlating resources to the Czech language and want to enable it. Why are non English resources commented out ? Thanks, David -- David Kredba <kredba at ibot.cas.cz> GPG: ID 1024D/5B6B02DE Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE

2 1

Re: [wineD3D] HW Vertex Buffer
by Ann and Jason Edmeades 21 Oct '04

21 Oct '04

Hiya, Re your new patch... -#define IWineD3DDevice_CreateVertexBuffer(p,a,b,c,d,e,f) (p)->lpVtbl->CreateVertexBuffer(p,a,b,c,d,e,f) +#define IWineD3DDevice_SetFVF(p,a) (p)->lpVtbl->SetFVF(p,a) +#define IWineD3DDevice_GetFVF(p,a) (p)->lpVtbl->GetFVF(p,a) +#define IWineD3DDevice_CreateVertexDeclaration(p,a,r) (p)->lpVtbl->CreateVertexDeclaration(p,a,r) +#define IWineD3DDevice_SetVertexDeclaration(p,a) (p)->lpVtbl->SetVertexDeclaration(p,a) +#define IWineD3DDevice_GetVertexDeclaration(p,a) (p)->lpVtbl->GetVertexDeclaration(p,a) +#define IWineD3DDevice_CreateVertexShader(p,a,r) (p)->lpVtbl->CreateVertexShader(p,a,r) +#define IWineD3DDevice_SetVertexShader(p,a) (p)->lpVtbl->SetVertexShader(p,a) +#define IWineD3DDevice_GetVertexShader(p,a) (p)->lpVtbl->GetVertexShader(p,a) +#define IWineD3DDevice_CreatePixelShader(p,a,r) (p)->lpVtbl->CreatePixelShader(p,a,r) +#define IWineD3DDevice_SetPixelShader(p,a) (p)->lpVtbl->SetPixelShader(p,a) +#define IWineD3DDevice_GetPixelShader(p,a) (p)->lpVtbl->GetPixelShader(p,a) +#define IWineD3DDevice_CreateVertexBuffer(p,a,b,c,d,e,f) (p)->lpVtbl->CreateVertexBuffer(p,a,b,c,d,e,f) +#define IWineD3DDevice_BindVertexBuffer(p,a) (p)->lpVtbl->BindVertexBuffer(p,a) +#define IWineD3DDevice_UnbindVertexBuffer(p,a) (p)->lpVtbl->UnbindVertexBuffer(p,a) Some of these are defining functions which dont exist yet in wined3d, which will get confusing. Additionally, the functionality for the wined3d vertex buffer is almost untested, because its just copying code and ensuring it gets driven. The d3d9 -> wined3d support isnt enough to prove your changes actually work, and I would rather we didnt put in untested code during the migration phase. I'm finding it hard to keep track of where I am on the migration from d3d8 -> wined3d, so could I ask that you hold off this patch for a month or so, until I can get enought support into the wined3d library so you can prove the new code works. I could do with the d3d8, d3d9 and wined3d code staying fixed as I try to shuffle it all around. Once I get enough in wined3d to be able to prove parts of it work, and we are using it from both d3d8 and d3d9 then by all means put in this change. I'd also comment that this change is desperately needed as hardware buffer support should speed up the d3d support too. It seems odd to turn away new code, especially when hardly anyone else helps on the d3d side! Jason

2 2

msdn: d3drs_wrap[0-7] ???
by Ann and Jason Edmeades 21 Oct '04

21 Oct '04

As I understand it, there is texture states (D3DTSS_ADDRESSU/V/W) which map to the GL_WRAP_* states, and there is no direct mapping for the d3drs_* versions. I am not sure I understand the differences, but you would need to understand it before implementing it. BTW Any help on the d3d8/9 interfaces is very welcome - there's not enough people working on it (Nor the ddraw stuff either, come to that). I'm working on moving all the code from d3d8 into wined3d and calling from both d3d8/d3d9. It will probably take another month or so, but if patches could be held until it is complete I would appreciate it - I'm afraid of dropping or missing something as I go! Regards, Jason

2 1

msdn: d3drs_wrap[0-7] ???
by Devils Cry 21 Oct '04

21 Oct '04

Hi folks! Dunno why, but this list regrets my subscriptionrequests. Anyway, lets see if this gets through... Im currently working a bit on the d3d8 dll (i know there are currently heavy changes made, just creating some new interfaces) and am now focusing on the d3drs_wrap[0-7] function. I have some problems understanding what it should do, from msdn: [quote] D3DRS_WRAP0 [ie, its the same for wrap0 to 7] Texture-wrapping behavior for multiple sets of texture coordinates. Valid values for this render state can be any combination of the D3DWRAPCOORD_0 (or D3DWRAP_U), D3DWRAPCOORD_1 (or D3DWRAP_V), D3DWRAPCOORD_2 (or D3DWRAP_W), and D3DWRAPCOORD_3 flags. These cause the system to wrap in the direction of the first, second, third, and fourth dimensions, sometimes referred to as the s, t, r, and q directions, for a given texture. The default value for this render state is 0 (wrapping disabled in all directions). [/quote] My current thoughts are to enable the GL_TEXTURE_WRAP_S, T and R functions by the value passed to it (ie for 2 enable the S and T wrappers), but i guess this isnt exactly what it should do. Any thoughts, ideas, guesses? BTW, i havent found anything matching the D3DWRAPCOORD_3 flag (should be the 4th dimension). Is there something i can use for this? Thx in advance Nikolas

2 1

msdn: d3drs_wrap[0-7] ???
by Devils Cry 21 Oct '04

21 Oct '04

Hi folks! Im currently working a bit on the d3d8 dll (i know there are currently heavy changes made, just creating some new interfaces) and am now focusing on the d3drs_wrap[0-7] function. I have some problems understanding what it should do, from msdn: [quote] D3DRS_WRAP0 [ie, its the same for wrap0 to 7] Texture-wrapping behavior for multiple sets of texture coordinates. Valid values for this render state can be any combination of the D3DWRAPCOORD_0 (or D3DWRAP_U), D3DWRAPCOORD_1 (or D3DWRAP_V), D3DWRAPCOORD_2 (or D3DWRAP_W), and D3DWRAPCOORD_3 flags. These cause the system to wrap in the direction of the first, second, third, and fourth dimensions, sometimes referred to as the s, t, r, and q directions, for a given texture. The default value for this render state is 0 (wrapping disabled in all directions). [/quote] My current thoughts are to enable the GL_TEXTURE_WRAP_S, T and R functions by the value passed to it (ie for 2 enable the S and T wrappers), but i guess this isnt what it should do. Any thoughts, ideas, guesses? BTW, i havent found anything matching the D3DWRAPCOORD_3 flag (should be the 4th dimension). Is there something i can use for this? Thx in advance Nikolas

1 0

Re: shell32: shlfileop; Add resource for renaming files on collision (patch 2)
by Tobias Burnus 21 Oct '04

21 Oct '04

Hello, Rolf Kalbermatter wrote: > + IDS_COPY_X_OF_TEXT "Kopie%svon %s" > + IDS_COPY_X_OF_TEXT "Copy%sof %s" I may miss something, but I think there is are space missing around the first '%s'. Tobias

1 0

RE: Treeview +/-
by Ge van Geldorp 21 Oct '04

21 Oct '04

> From: Jon Griffiths > > Hi, > > Fixing my own FIXME. > > Cheers, > Jon > > +wine/dlls/comctl32/treeview.c > Draw +/- correctly for large icon sizes (patch applied here: http://www.winehq.org/hypermail/wine-cvs/2004/10/0115.html) I can see that this would be an improvement for large icon sizes, but I don't think it's good for small icon sizes. See attached screenshot of regedit. Maybe the height/width at which to switch to the Rectangle drawing algorithm needs a bit of tuning? Ge van Geldorp.

1 0

scroll bars not shown
by Nicolai Kuntze 21 Oct '04

21 Oct '04

Hi, in the application given in Bug 2302 are in some menus the scroll bars missing. I think the programm gets wrong dimensions from the size of the window. I do not have enough experience to track the bug by myself. Can someone please have a look on it? I have tried with the latest CVS checkout and comctrl32 as an native library. Yours, Nicolai ---- Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.

1 0

Wine on OpenBSD
by Sascha Hanse 21 Oct '04

21 Oct '04

Hi people, I just tried to install the recent Wine-tarball (20041019) on my OpenBSD 3.6. First I had to remove kthread.c:275: the RFTHREAD flag. Then the 'make depend && make' worked properly but the make install first fails with: /usr/bin/install -c serialui.dll.so /usr/local/lib/wine/serialui.dll.so cd `dirname setupapi/__install__` && make install gcc -g -O2 -o install install.c install.c:23: windef.h: No such file or directory install.c:24: winbase.h: No such file or directory install.c:25: winreg.h: No such file or directory install.c:26: winternl.h: No such file or directory install.c:27: winerror.h: No such file or directory install.c:28: wingdi.h: No such file or directory install.c:29: winuser.h: No such file or directory install.c:30: winnls.h: No such file or directory install.c:31: setupapi.h: No such file or directory install.c:33: wine/unicode.h: No such file or directory install.c:34: wine/debug.h: No such file or directory *** Error code 1 Stop in /home/sensei/wine-20041019/dlls/setupapi. *** Error code 1 Stop in /home/sensei/wine-20041019/dlls (line 416 of Makefile). *** Error code 1 Stop in /home/sensei/wine-20041019 (line 301 of Makefile). After that I copied all needed headerfiles into dlls/setupapi/ and finally I got these errors: [SNIP] /tmp//ccU25700.o(.text+0x18d1): In function `InstallHinfSectionW': /home/sensei/wine-20041019/dlls/setupapi/install.c:927: undefined reference to `SetupOpenInfFileW'/tmp//ccU25700.o(.text+0x18e1):/home/sensei/wine-200 41019/dlls/setupapi/install.c:930: undefined reference to `SetupInitDefaultQueueCallback'/tmp//ccU25700.o(.text+0x18f0):/home/sen sei/wine-20041019/dlls/setupapi/install.c:931: undefined reference to `SetupDefaultQueueCallbackW'/tmp//ccU25700.o(.text+0x1912):/home/sensei /wine-20041019/dlls/setupapi/install.c:934: undefined reference to `SetupTermDefaultQueueCallback'/tmp//ccU25700.o(.text+0x1918):/home/sen sei/wine-20041019/dlls/setupapi/install.c:935: undefined reference to `SetupCloseInfFile'/tmp//ccU25700.o(.text+0x193e): In function `InstallHinfSectionA':/home/sensei/wine-20041019/dlls/setupapi/install. c:950: undefined reference to `RtlCreateUnicodeStringFromAsciiz'/tmp//ccU25700.o(.text+0x195f):/home/ sensei/wine-20041019/dlls/setupapi/install.c:953: undefined reference to `RtlFreeUnicodeString'/tmp//ccU25700.o(.rodata+0x80): In function `get_field_string':/home/sensei/wine-20041019/dlls/setupapi/install.c:9 8: undefined reference to `__wine_dbch_setupapi' collect2: ld returned 1 exit status*** Error code 1 Stop in /home/sensei/wine-20041019/dlls/setupapi. *** Error code 1 Stop in /home/sensei/wine-20041019/dlls/setupapi. *** Error code 1 Stop in /home/sensei/wine-20041019/dlls (line 416 of Makefile). *** Error code 1 Stop in /home/sensei/wine-20041019 (line 301 of Makefile). Please CC me because I'm not subscribed to the list. -Sascha -- Anyone who considers arithmetical methods of producing random digits is, of course, in a state of sin. --John von Neumann (1951)

2 1

Re: Tiny optimizations of bit testing operations
by Rein Klazes 21 Oct '04

21 Oct '04

On Wed, 20 Oct 2004 19:48:05 +0900, you wrote: > Hello, > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Tiny optimizations of bit testing operations. Testing with gcc 3.3.5: > - BOOL min_or_max_box = (wndPtr->dwStyle & WS_MAXIMIZEBOX) || > - (wndPtr->dwStyle & WS_MINIMIZEBOX); > + BOOL min_or_max_box = wndPtr->dwStyle & (WS_MAXIMIZEBOX | WS_MINIMIZEBOX); At moderate optimization levels (-O1) gcc compiles this to identical code. > - if((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) != 0) > + if (wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) At any optimization level, gcc compiles this to identical code. > if ((wndPtr->dwStyle & WS_VSCROLL) && > - ((((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) != 0) && (ptClient.x <= rcClient.left + GetSystemMetrics(SM_CXVSCROLL))) || > - (((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) == 0) && (ptClient.x >= rcClient.right - GetSystemMetrics(SM_CXVSCROLL))))) > + (((wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) && (ptClient.x <= rcClient.left + GetSystemMetrics(SM_CXVSCROLL))) || > + (!(wndPtr->dwExStyle & WS_EX_LEFTSCROLLBAR) && (ptClient.x >= rcClient.right - GetSystemMetrics(SM_CXVSCROLL))))) Not different then the previous example. >From the C point of view these bit logics are identical. The compiler finds that out easy. Rein. -- Rein Klazes rklazes(a)xs4all.nl

4 4

IE6: Help Engine Sputtering, Main Engine Doesn't Start, Segmentation Fault
by Dan McGhee 21 Oct '04

21 Oct '04

At the outset I must apologize for the length of this post. This situation is intricately convoluted and, currently, I cannot interpret the information that I have collected. Right now I can only relay information that I think is relevant. I would be more than happy to generate more info, but I will need some specific direction for commands and so forth. Right now I have reached the limit of my current troubleshooting skills. My overall goal is to get Edit Studio 4, a video editing application, running in wine. It depends on the IE6 Help Engine. There are other situations with this app and that's why I don't depend on an older version of wine to run it. Right now, if I can't get IE6 to run its help engine, I can't get my app to work. Here goes on my problems with IE6. Conventions: 1013 implies wine compiled from the cvs update on October 13 and a .wine, created from that update aug implies wine version compiled from the cvs update on October 13 and a .wine from a wine version, compiled from my repository, before the 20040824 16:00:16 CDT commit Symptoms: 1. with wine from 1013 and .wine from 1013, IE6 exits with no window--this started sometime after the September snapshot 2. with wine from 1013, any version of wine that I compile, and .wine from aug, IE6 runs and Help works 3. with wine from September snapshot and .wine from 1013, IE6 creates a segmentation fault My original symptom was that I couldn't get IE6 Help to work after the September snapshot. I did a regression and identified the commit of 20040824 16:00:16 CDT as causing the problem. The commit edits this patch: http://cvs.winehq.org/patch.py?id=13475 Among other things this patch changes wine/dlls/Makefile.in wine/configure.ac wine/configure it also changes itss.dll. However, my symptoms still persist whether I use a native or builtin version of itss. I include this information because I don't know if the symptoms are separate problems or are related. I am not able to pin point the cause of Symptom 1 because I do not yet know how to update my repository to do a regression. I must wait for the archive after the October snapshot. I have reasoned, since I can get IE6 to work completely using a ~/.wine created before that August commit, that the problem lies somewhere in the "fake windows" directory. There are differences in the registry, win.ini and system.ini files, but I do not know how to diagnose them. The following excerpt, from one of the logs I created, shows that there is a completely different sequence, between the working and non-working situations, when shell32 loads for the first time: trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\shell32.dll" : builtin -trace:loaddll:MODULE_FlushModrefs Unloaded module L"c:\\windows\\system\\shell32.dll" : builtin -trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\shell32.dll" : builtin trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\ole32.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\BROWSEUI.dll" : native err:shell:ReadCabinetState Initializing shell cabinet settings trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\browselc.dll" : native -trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\RPCRT4.DLL" : native +trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\shdoclc.dll" : native +err:rebar:REBAR_WindowProc unknown msg 200b wp=00000000 lp=71180f00 +trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\uxtheme.dll" : builtin +trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\RPCRT4.dll" : native +trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\lz32.dll" : builtin +trace:loaddll:load_dll Loaded module L"c:\\windows\\system\\version.dll" : builtin +trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\urlmon.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\MSOSS.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\CRYPT32.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\OLEAUT32.dll" : native trace:loaddll:load_dll Loaded module L"C:\\windows\\system\\WININET.dll" : native I stopped the excerpt here because this is the point at which the non-working situation exits. I have generated a log from +relay "grepped" for shell32 but do not know how to interpret it to see if I can glean any more information. This log and all the others are contained in the tarball that I have attached. It creates a directory called "wine-trouble" and contains all the information that I have generated. The README contains specifics of what I have done. As I was composing the README for inclusion here, I realized that I had not done two things. I forgot to copy shell and shell32 to my fake windows directory so that all of my tests were conducted with builtin shell and shell32. Additionally, I have not run wine compiled before the August commit with a fake windows created on October 13. I will do both of these and see if I get differenet results. I'm really interested in resolving this and would rather that I had been able to supply better information. However, my knowlege of winedbg, windows and cvs does not currently allow me to proceed further. If anyone wants me to do more, I would appreciate being pointed in the right direction, but I will need some specifics. I have found no documentation on any of the wine mailing lists or other forums to indicate that anyone else is having this problem. It could be something that I am doing. This is why I haven't yet submitted a bug report. If a bug report would be more appropriate, I will do that. Thanks, Dan

1 1

Re: [wineD3D] HW Vertex Buffer
by Raphael 21 Oct '04

21 Oct '04

Hi again, A better patch than previous Changelog: - beta implementation of HW Vertex Buffer support (using ARB_vertex_buffer_object): locking/unlocking, creation, destruction - some wined3d headers/interface extension Todo - Bind/Unbind on rendering (use exported APIs, see IWineD3DDevice_BindVertexBuffer/IWineD3DDevice_UnbindVertexBuffer) Regards, Raphael

1 0

wine developer guide
by Eric Pouech 20 Oct '04

20 Oct '04

While looking at the WDG (and please don't count me in about arguing whether it's WDG or WD'sG or WD'G), I came onto the Advanced Topics book after the two big ones ("Developing Wine" and "Wine Architecture") I does seem very odd to me as it right now: - it just contains "random" bits of information on some parts of wine - we don't have (yet) a uniform way to qualify something of advanced So my proposal would be to: - get rid of "Advanced Topics" book altogether, and keep only "Developing Wine" (the way we'd like development going on) and "Wine architecture" (the way it works - or it's supposed to) - move the various items from "Advanced Topics" to where they belong (see below) - maybe tag in both the "developing" and "architecture" books which parts are really advanced (change of font, specific paragraph type... pick up the visual effect you like most) The mapping that could be done would be: 14.1 Keyboard => Architecture/X11DRV DLL 14.2 Undocumented API => somewhere in the "developing" chapter 14.3 accelerators => Architecture/USER32.DLL 14.4 HW trace => somewhere in the "developing" chapter (likely in debugging) 15 Porting to new OS => somewhere in the "developing" chapter (likely in writing patches, to be renamed as "coding practice" or so) 16 Consoles => Architecture/KERNEL32.DLL 17 Address space => Architecture/6.3.4 (as advanced material) 18 Regression testing => somewhere in the "developing" chapter (in conformance tests) Likewise, the 5.1 about adding new languages could be moved into the "coding practice" part. If noone objects, I'll submit the changes. A+

1 0

Stack overflows
by Robert Lunnon 20 Oct '04

20 Oct '04

I have been trying to make wine work properly with Solaris xlib and have been experiencing a few stack overflow exceptions eg 0009:Ret kernel32._LeaveSysLevel() retval=00000000 ret=7f86a7ba 0009:Ret user32.USER_Unlock() retval=00000000 ret=7f53f837 0009:Call ntdll.RtlEnterCriticalSection(7f579840) ret=7f549249 0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=7f549249 0009:Call ntdll.RtlLeaveCriticalSection(7f579840) ret=7f54926a 0009:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=7f54926a 0009:Call ntdll.RtlEnterCriticalSection(7f579840) ret=7f549249 0009:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=7f549249 err:seh:setup_exception stack overflow 0 bytes in thread 0009 eip ca096003 esp 7fc11000 stack 7fc10000-7fd10000 As I recall PE executables specify the stack size in the PE header so in the past I have used a little windows utility under wine to increase the stack allocation to the program, sometimes with mixed results. I Thought I'd post here to find out if this is known problem and what the cause is. I had presumed it was probably due to the extra call layering through xlib adding too much overhead to the stack for the app. Assuming this is the issue there were two actions I was looking at taking 1. A Wine utility to adjust the stack allocation for the executable 2. Adjust the stack allocation in wine to allow a little extra for wine over and above that requested by the app. Opinions ? Bob

1 0

Reimplementing SHGetFolder functions
by Juan Lang 20 Oct '04

20 Oct '04

Any reason this patch wasn't applied? http://www.winehq.org/hypermail/wine-patches/2004/10/0167.html I know it's big, but I hope the test cases help demonstrate its correctness. Let me know if there's anything else I can do to help a review. Thanks, --Juan __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

2 1

Re: Startmenu
by Robert Shearman 20 Oct '04

20 Oct '04

Thorsten Kani wrote: > Nice Patch - looks good now! > i have changed the offsets and used SM_CXBORDER instead of SM_CXEDGE. > (According to MSDN, cxedge is used for 3D while cxborder is used for > Flat ) > This seems to fix the"draw below" issue. Visual Experience comes now > really near native. > > I noticed that SM_CXEDGE is used everywhere, regardless of Style > TBSTYLE_FLAT. > Please review my attached Patch. It seems to me that this Stylechecks > shoud be used everywhere. I don't think this is correct. If you change the return value for GetSystemMetrics(SM_CXEDGE) in wine/windows/sysmetrics.c then you can see that it does affect the spacing between border and icon (but our toolbar control doesn't exactly match the native for this). > As for String position issue, maybe i can help out with the controlspy > check. > Im interested in understanding the controls and wanted to play around > with CSpy anyway. > Suggestions ? You can download controlspy here: http://www.microsoft.com/msj/0798/controlspy.aspx It is very useful for throwing messages at the common controls, but it cannot test custom draw functionality and it is becoming dated (it is missing new functionality from comctl32 v5.80 and new controls). Rob

2 2

Re: dlls/x11drv/winpos.c::SWP_DoOwnedPopups()
by Dmitry Timoshkov 20 Oct '04

20 Oct '04

"Peter Riocreux" <par+wine_patches(a)silistix.com> wrote: > The comment above SWP_DoOwnedPopups in dlls/x11drv/winpos.c suggests > that the only thing missing is what I *might* have fixed here, > therefore the patch also removes the FIXME and the WARN. It compiles > and doesn't break any behaviour I can test, but I am only guessing > whether I have done the right thing. You have to write a test case and add it to existing ones in dlls/user/tests/win.c to confirm that the patch is correct. -- Dmitry.

2 3

DrawTextA: regarding the nCount variable
by William Poetra Yoga H 20 Oct '04

20 Oct '04

In the MSDN, it is stated that if nCount is 1, then it is assumed that lpString is a null-terminated string. But in the DrawTextExA function, it is -1, as in the code: if (count == -1) count = strlen(str); Shouldn't this be 1 instead of -1? CMIIW. (But theForger's tutorial also uses -1) _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

3 3

Re: ADVAPI32: implement ChangeServiceConfigA using ChangeServiceConfigW (take 2)
by Robert Shearman 20 Oct '04

20 Oct '04

Mike McCormack wrote: > > oops. The macro functions for duplicating strings already exist, so > use them instead. > > Mike > > > ChangeLog: > * implement ChangeServiceConfigA using ChangeServiceConfigW > >------------------------------------------------------------------------ > >Index: dlls/advapi32/service.c >=================================================================== >RCS file: /home/wine/wine/dlls/advapi32/service.c,v >retrieving revision 1.60 >diff -u -r1.60 service.c >--- dlls/advapi32/service.c 27 Sep 2004 20:35:27 -0000 1.60 >+++ dlls/advapi32/service.c 20 Oct 2004 07:28:54 -0000 >@@ -810,7 +810,8 @@ > > static inline VOID SERV_free( LPWSTR wstr ) > { >- HeapFree( GetProcessHeap(), 0, wstr ); >+ if (wstr) >+ HeapFree( GetProcessHeap(), 0, wstr ); > } > > There is no need for this check. Freeing NULL pointers is not an error and is handled by the RtlFreeHeap code. Rob

1 0

Re: fix tbn_deletingbutton
by Dmitry Timoshkov 19 Oct '04

19 Oct '04

"Thorsten Kani" <beebix(a)gmx.net> wrote: > I'm a bit unsure about my solution, but actually everything works. > -complaints appreciated- > --- toolbar.c 23 Sep 2004 22:51:14 -0000 1.194 > +++ toolbar.c 10 Oct 2004 17:29:01 -0000 > @@ -3191,12 +3191,20 @@ > TOOLBAR_INFO *infoPtr = TOOLBAR_GetInfoPtr (hwnd); > INT nIndex = (INT)wParam; > NMTOOLBARW nmtb; > + WCHAR Buffer[256]; > > if ((nIndex < 0) || (nIndex >= infoPtr->nNumButtons)) > return FALSE; > > memset(&nmtb, 0, sizeof(nmtb)); > nmtb.iItem = nIndex; > + memcpy(&nmtb.tbButton, &infoPtr->buttons[nIndex], sizeof(nmtb.tbButton) ); > + nmtb.cchText = 256; > + nmtb.pszText = Buffer; > +#if (_WIN32_IE >= 0x500) > + nmtb.rcButton =(RECT)infoPtr->buttons[nIndex].rect; > +#endif > + > TOOLBAR_SendNotify((NMHDR *)&nmtb, infoPtr, TBN_DELETINGBUTTON); 1. do not use _WIN32_IE version checks in Wine code, they have no sense 2. there is no point in setting a pointer to a not initialized buffer 3. there is no need to cast RECT to a RECT -- Dmitry.

3 8

Re: add epoll implementation to libwine_port (take 3)
by Chris Dodd 19 Oct '04

19 Oct '04

Mike McCormack <mike(a)codeweavers.com> wrote in news:4174D681.9050503@codeweavers.com: > A few more changes after consulting with Alexandre. > > ChangeLog: > * add epoll implementation to libwine_port : > + __asm__ __volatile__( "pushl %%ebx; movl %2,%%ebx; int $0x80; popl > %%ebx" + : "=a" (ret) : "0" : A random question here from someone who is not too familiar with wine internals -- why are you using inline asm code instead of syscall(2)? It seems like syscall would be both simpler and more portable. Chris Dodd cdodd(a)acm.org

1 0

Re: add epoll implementation to libwine_port (take 3)
by Boaz Harrosh 19 Oct '04

19 Oct '04

Mike McCormack wrote: > > > ChangeLog: > * add epoll implementation to libwine_port > >.... > > >+ __asm__ __volatile__( "pushl %%ebx; movl %2,%%ebx; int $0x80; popl %%ebx" > > Grate ! [Q] Does that mean that we directly check if it is supported in kernel, bypassing glibc all together? how do we avoid conflicts with glibc?

4 5

dlls/x11drv/winpos.c::SWP_DoOwnedPopups
by Peter Riocreux 19 Oct '04

19 Oct '04

I have a lot of WARNs from this function so I thought I would have a shufty at it to see if it was easy to fix. The FIXME above it is written so as to suggest that it is a matter of mere keystrokes to fix it up, or weeks of work, depending on your frame of mind when you read it. Still being a beginner (first patch now committed be Aj - yay!) and not knowing about Windows programming, I don't know where to look to decide which is the case. The comment above it says: /*********************************************************************** * SWP_DoOwnedPopups * * fix Z order taking into account owned popups - * basically we need to maintain them above the window that owns them * * FIXME: hide/show owned popups when owner visibility changes. */ It looks like, depending on some property of 'owner' it should or shouldn't use the property SWP_HIDEWINDOW in the call to SetWindowPos <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winu…> If this is the case I could fix it, if I knew how to determine when 'owner' is visible. Do I also need a callback of some kind so that the popup is rendered invisible when the parent is, even if SWP_DoOwnedPopups is not called (or is that not (supposed to be) possible?)? Is the WARN there only because of the FIXME and if I fix the FIXME I should remove the WARN? Peter

1 1

Re: wine/dlls/ntdll time.c
by Dimitrie O. Paun 19 Oct '04

19 Oct '04

On Mon, Oct 18, 2004 at 04:19:29PM -0500, Alexandre Julliard wrote: > Log message: > Rein Klazes <rklazes(a)xs4all.nl> > In RtlQueryTimezoneInformation use information from the registry if it > is available. > > Patch: http://cvs.winehq.org/patch.py?id=14188 Hmm, shouldn't we synch up with the Unix env instead? I assume this info is available in the Unix env... This would be preferable even in the case of a shared Windows install, me thinks. -- Dimi.

2 1

CreateFile GENERIC_WRITE on a directory
by ScratchMonkey 19 Oct '04

19 Oct '04

Not sure if this should be in -users, but I'm trying to get the Tribes: Vengeance dedicated server going (1st person shooter) and it stops with a messagebox that it can't write to its own directory. Tracing the program with +relay reveals this: 000b:Call kernel32.CreateFileW(10415fc0 L"Z:\\home\\vengeance\\Server \\Program\\Bin\\",40000000,00000007,00000000,00000003,02000000,00000000) ret=1015b46d 000b:Call ntdll.RtlIsDosDeviceName_U(10415fc0 L"Z:\\home\\vengeance\\Server \\Program\\Bin\\") ret=554b4506 000b:Ret ntdll.RtlIsDosDeviceName_U() retval=00000000 ret=554b4506 000b:Call ntdll.RtlDosPathNameToNtPathName_U(10415fc0 L"Z:\\home\\vengeance \\Server\\Program\\Bin\\",559bebb0,00000000,00000000) ret=554b42c7 000b:Ret ntdll.RtlDosPathNameToNtPathName_U() retval=00000001 ret=554b42c7 000b:Call ntdll.NtCreateFile (559beba4,40000000,559bebb8,559beba8,00000000,00000000,00000007,00000001,00 004010,00000000,00000000) ret=554b438f 000b:Ret ntdll.NtCreateFile() retval=c00000ba ret=554b438f 000b:Call ntdll.RtlNtStatusToDosError(c00000ba) ret=554b43bd 000b:Ret ntdll.RtlNtStatusToDosError() retval=00000005 ret=554b43bd 000b:Call ntdll.RtlFreeUnicodeString(559bebb0) ret=554b43cc 000b:Ret ntdll.RtlFreeUnicodeString() retval=00000001 ret=554b43cc 000b:Ret kernel32.CreateFileW() retval=ffffffff ret=1015b46d Decoding the parameters to CreateFile show it trying to open the directory for GENERIC_WRITE. I'm about to dig into the wine sources but am hoping someone can spot the problem more quickly than me. I'm using the 20040914 source RPM from NewRPMs.

2 3

Re: Turn off Antialiasing for Rendering with Palette
by Alexandre Julliard 19 Oct '04

19 Oct '04

Glenn Wurster <gwurster(a)scs.carleton.ca> writes: > Description: > * When we are working with a palette, we need to disable antialiasing. > Antialiasing results in a lot of extra colour values which are not > mapped in the palette, causing bad display artifacts. > > Changelog: > * Disable antialiasing when working with the palette You shouldn't change the global antialias flag, this is ugly and it will most likely break the font caching. You have to add checks for a palette directly at the places that handle the anti-aliasing (and your palette check is wrong too, you shouldn't peek into the internals of the DC bitmap). -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: Server: Create and Use New mem_free Function
by Alexandre Julliard 19 Oct '04

19 Oct '04

Robert Shearman <rob(a)codeweavers.com> writes: > We have our own mem_alloc memory allocator, so this patch adds the a > new free function, mem_free, and replaces instances of free with > mem_free. At the moment, the implementation completely defers to the > libc free function, but it makes sense to have this new function so > that we can easily change memory allocators. The patch also changes a > few instances of malloc to mem_alloc. You cannot do that, mem_alloc sets the error code but malloc doesn't, they are not the same thing. The purpose of mem_alloc is to simplify handling of allocation failures in common cases, it's not a general replacement for malloc. If you really want to change the memory allocator you can redefine malloc and free, but I'm not sure why you'd want to do that. -- Alexandre Julliard julliard(a)winehq.org

1 0

oleaut32: SafeArrayDestroyData
by Walt Ogburn 18 Oct '04

18 Oct '04

Hi, I am working on getting a scientific / engineering application called SRIM (www.srim.org), specifically the batch-mode component SRModule of SRIM 2003. This is a Visual Basic program, so there's lots of reliance on oleaut32.dll. In addition to freeing the data memory of the SafeArray, Wine's implementation of SafeArrayDestroyData sets the pointer pvData to NULL. The native Windows version apparently does not do this, and SRIM depends on pvData still pointing to the same place afterwards. Wine's code also uses this nulling to keep track of the memory, so that it won't get freed again. I can't say why a program would still want pvData after a call to SafeArrayDestroyData, but there it is. Could the flag FADF_DATADELETED be used to keep track of this instead? That seems to be the case only for vector SafeArrays now. The following patch seems to make SRIM work: =================================================================== Index: dlls/oleaut32/safearray.c =================================================================== RCS file: /home/wine/wine/dlls/oleaut32/safearray.c,v retrieving revision 1.40 diff -u -r1.40 safearray.c --- dlls/oleaut32/safearray.c 20 Sep 2004 19:11:48 -0000 1.40 +++ dlls/oleaut32/safearray.c 18 Oct 2004 17:03:51 -0000 @@ -1254,7 +1254,7 @@ if (psa->cLocks) return DISP_E_ARRAYISLOCKED; /* Can't delete a locked array */ - if (psa->pvData) + if (psa->pvData && !(psa->fFeatures & FADF_DATADELETED)) { /* Delete the actual item data */ if (FAILED(SAFEARRAY_DestroyData(psa, 0))) @@ -1265,7 +1265,8 @@ { if (!SAFEARRAY_Free(psa->pvData)) return E_UNEXPECTED; - psa->pvData = NULL; + /* psa->pvData = NULL; */ + psa->fFeatures |= FADF_DATADELETED; } else psa->fFeatures |= FADF_DATADELETED; /* Mark the data deleted */ =================================================================== Also, is there a way to make the tests in oleaut32/tests/ run on the native dlls? If so, I could more clearly show that the Windows version doesn't null pvData. Thanks, Walter

2 2

Re: x11drv: Add stretching support to AlphaBlend
by Huw D M Davies 18 Oct '04

18 Oct '04

On Sun, Oct 17, 2004 at 10:34:28PM -0400, Kevin Koltzau wrote: > Changelog: > Add stretching support to AlphaBlend XRenderSetPictureTransform is a relatively new addition to libxrender, arriving just before XFree 4.3. I don't think we want the whole xrender stuff to fail if this specific function isn't available in the library. Could you make the presence of this function optional and simply skip the stretched AlphaBlend if it's not there? Huw.

1 0

-fPIC on link line in winegcc for HPUX
by Warren_Baird/CSI＠cimmetry.com 18 Oct '04

18 Oct '04

Hi all, Another change I had to make for HPUX that I'm not 100% sure about: The HPUX linker gets quite unhappy unless the gcc link line inside of winegcc is fed -fPIC. The problem is that the collect2 phase builds it's own temporary object file that gets included in the final link, and if that temp .o file isn't compiled with -fPIC, the HP linker complains. In order to get this to work, I had to add -fPIC to the list of link flags that winegcc recognizes: diff -ur patched/wine-20040914/tools/winegcc/winegcc.c wine-20040914/tools/winegcc/winegcc.c --- patched/wine-20040914/tools/winegcc/winegcc.c 2004-10-12 10:28:37.000000000 -0400 +++ wine-20040914/tools/winegcc/winegcc.c 2004-10-12 10:10:07.000000000 -0400 @@ -616,7 +616,7 @@ { "-nostartfiles", "-nodefaultlibs", "-nostdlib", "-s", "-static", "-static-libgcc", "-shared", "-shared-libgcc", "-symbolic", - "-framework" + "-framework", "-fPIC" }; int j; The question: is this going to be harmful on other platforms? I'm not sure whether I should protect it with ifdefs, or just leave it as is. Any suggestions? Thanks, Warren

3 6

Re: Resend: Honor --disable-debug or --disable-trace completely
by Alexandre Julliard 18 Oct '04

18 Oct '04

Vincent Béron <vberon(a)mecano.gme.usherb.ca> writes: > wine/debug.h has some tests based on NO_{DEBUG,TRACE}_MSGS, which is set > (or not) in config.h. Quite a few files didn't #include config.h before > wine/debug.h, so some debugmsgs were always compiled in, even with > ./configure --disable-debug. > > Now maybe we want to install config.h as well, as debug.h is already > installed. I'll leave that one to Alexandre. No, the right fix is to put these defines in the Makefile and get rid of them in config.h. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: MinGW portability fix
by Hans Leidekker 18 Oct '04

18 Oct '04

On Sunday 17 October 2004 16:16, Hans Leidekker wrote: > Changelog: > Add configure check for getpagesize() declaration, needed by MinGW. Hmm, I just found that the AC_CHECK_DECL macro doesn't work as expected. You can skip this patch. -Hans

1 0

Re: [wine] Re: window caption buttons
by William Poetra Yoga H 18 Oct '04

18 Oct '04

--- David Lee Lambert <lamber45(a)cse.msu.edu> wrote: > On Wed, Oct 13, 2004 at 08:31:37AM -0700, William Poetra Yoga Hadisoesen > wrote: > > --- Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> wrote: > > > > If it really makes a functional difference, then I guess it should be > fixed, > > > otherwise why not leave it as is? > > > 1. Developers coming from Windows can have the same "look and feel". This > > increases their productivity, although indirectly. When people see > something > > different but similar to the one they see everyday, their attention will be > > divided to the new object and the work they are doing. And their motivation > to > > work will decrease, too, if the GUI doesn't get fixed. > > Once in a while on Windows, I tweak the desktop fonts and colors a little > bit just so it doesn't get boring. I've made document backgrounds > off-white; changed the menu font; even done a little bit with Active > Desktop on some boxes. An off-by-one error in a terminal emulator that > lets it only display 79 columns needs to be fixed, but I'd rather we kept > little oddities like this. Yeah, you've got a point there. But then wouldn't it be better if we start off emulating the "standard" win9x style, and then create themes and stuff? Just like reactos: they start by trying to be nt4.0-compatible, but have plans to do win2k. Or xpde: they start with the win2k shell and add the winxp features later ;) > > 2. Windows users looking at WINE will reject it straight away, because it > > doesn't look like a "professionaly-made" software, and maybe mocking it as > a > > carelessly written software, with sloppy GUI. Remember, some users become > > developers. > > I don't aggree with this either. "Professional" apps on Windows these > days go out of their way to look fancy, do their own drawing, be a > little bit different than Windows. (I know these have better alternatives > on Linux but) look at MusicMatch Jukebox, WinAmp, RealPlayer, Windows > Media Player, AOL, Kodak Photo Editor... these apps have all their own > icons anyway. The Win3.1->Win95 or WinNT->WinXP UI jump is already bigger > than that from Wine to the average of all versions it matches, in terms > of things like this. Yes, there are inconsistencies between Windows versions, and between some programs and programs which use the "standard" ui. It's true that there are many professional programs which draw their own windows. But have you looked more closely at WINE's window decorations? They're like Windows 95's, but they're somewhat different. I think it's better (and more appealing to the eye) if we were to define a theme (WINE theme) that looks at least obviously different from the Windows shell. It's because when we draw things so similar -- yet different -- to things found in Windows, people won't like it. It's like, doing a (sorry, just a comparison) fake thing that's similar to the original. If you have lived in China, you can find fake Nike's everywhere, for example. Or fake Yonex shuttlecocks. They're not so much different from the original, but they still look... odd. It's one reason people won't buy them. And one more thing, is that I've found numerous off-by-one bugs in the ui part (that draws buttons, decorations, etc), just by attacking the "caption buttons" problem. I know they're off-by one bugs because they don't look right :( I'm not a good programmer, and I don't know how the Windows UI work, so if I'm left to fix the UI bugs there would be little or no wastage of resources, it will make me learn, and also make WINE look better. So I think it should be okay for me to "fix" the buttons (and numerous bugs I find along the way). _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

1 0

Re: UCS2 vs. UTF16 question
by Shachar Shemesh 18 Oct '04

18 Oct '04

Hi Juan, I took the liberty of answering to the list. I hope you don't mind. Juan Lang wrote: >Hi Schachar, something you said earlier this year at >wineconf caught my ear, and I think I'm finally >understanding enough to ask about it. You said >Windows uses UCS2-LE (I think you did, anyway) rather >than UTF16. Is that true? > I most certainly didn't say that. I may have mentioned UCS4, but to the best of my knowledge at the time, Windows uses UTF-16. As a result of your email, I tried to check it again, however. The results are somewhat inconclusive. I generated a file (attached) containing two musical symbols in Unicode. These are from the codepoints above U10000, and are therefor unrepresentable in UCS2. Opening this file up in notepad reveals a mixed result. On the one hand, they appear as two unknown characters (which seems to suggest that at least Notepad understands this is UTF-16LE). On the other hand, I did not manage to find any font that has any characters with codepoints above U10000. I'm hoping one of our far-eastern speakers jumps in with more insight (Mike?). Are surrogates used on Windows? How common are they? > Does that then imply that >Windows really can't handle characters outside the >Basic Multilingual Plane? Does that also imply that >WCHARs are in fact fixed-width in Windows? > > As far as I know, they are not. Sorry. >I'm planning to write a tool to detect the following >problematic bit of code: >char str[] = "hi", *p = str + sizeof(str) - 1; >p--; >At least, it's problematic when str contains >double-byte characters. > I'm not sure what you are aiming at achieving. Are you trying to hit the beginning of the last character of the string? If so, then you do, indeed, have a problem here. > If the type of char and p >were WCHAR * instead, and WCHARs are fixed width, >there isn't a problem. > >If you have thoughts on similar programming bugs >relating to internationalization (use of strchr and >strrchr, for example) I'd be interested to hear them. > > In the past I have written programs that had to do MBCS (the non-unicode Japanese encoding). This is an encoding in which some characters are one byte, and some two. The best I could come up with was to build a wrapper around std::string that had two bytes per character internally. When you loaded a string, it would check character by character for whether it's a double byte, and then have each string location contain exactly one character. This allowed random access, as well as both forward AND backwards scanning. Fortunately, UTF is much better than MBCS. Given a byte in either UTF-8 or UTF-16, it's fairly easy to figure out whether it's part of a surrogate, and what part. If you have assurance that the string you are handling is a well formed one, you can do backward scans of a UTF string fairly easily. >Thanks, >--Juan > >_______________________________ >Do you Yahoo!? >Declare Yourself - Register online to vote today! >http://vote.yahoo.com > > Do you want a gmail account? Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

2 1

Wineconf 2005
by Jeremy White 18 Oct '04

18 Oct '04

Hey Folks, It's that time again, time to plan for another Wineconf. There has been some back room chatter about Wineconf this year, but no definitive plans. A small cabal of people (myself included) think that we should hold it in Southern Germany around February/March. Marcus and Michael have each expressed that they might be able to get a facility to hold it in, but those efforts have so far not yielded anything definitive (I think we're tied up in big company red tape). Also, Huw Davies has offered to help host Wineconf in Oxford; that essentially translates into an offer by CodeWeavers to host Wineconf in mid March in Oxford. However, I want to throw this open to discussion and see if others have great ideas or if someone outside our secret cabal wants to step up and make this happen in Southern Germany. Based on our experience last year, I feel pretty strongly that we need the following: 1. An inexpensive, yet easy to reach location. Connection to nice places to visit before/after is a plus, but should be a substantially secondary consideration imo. 2. Two rooms that can each hold about 30-40 people, ideally with white boards, power, and high speed internet. 3. Access to food and hotels, preferably all within walking distance of each other. Since Europe is civilized, we should be able to walk from our Hotel to the conference, to a variety of food sources, and then, of course, to the pub. Candidly, I don't know that this is all that complicated. We'll likely be bringing enough people in that we should be able to negotiate a pretty nice deal with a Hotel. (We promise them xxx heads in beds, they give us conference facilities for a weekend). If someone wanted to help host Wineconf, and was willing to facilitate a conversation between myself and a Hotel that was well situated, CodeWeavers would be happy to sponsor the conference (i.e. financially reassure the Hotel). Thoughts? Comments? Cheers, Jeremy

4 5

Re: Make TranslateAcceleratorA handle national characters
by Dmitry Timoshkov 18 Oct '04

18 Oct '04

"Dmitry Timoshkov" <dmitry(a)baikal.ru> wrote: > Make TranslateAcceleratorA handle national characters. Please ignore this patch, it apparently corrupts original msg structure but it shouldn't. I'll send a new patch tomorrow. -- Dmitry.

1 0

Re: [PATCH] setkey breaks FreeBSD
by Mike Hearn 18 Oct '04

18 Oct '04

Anish Mistry wrote: > The attached patch fixes a CVS build problem with confilicting setkey in the > stdlib.h header. It's changed to WINE_setkey. I've gone ahead and changed > getkey to match. Aesthetics wise, I'd rather it was renamed to eg setcfgkey or something - there are no WINE_ prefixes in winecfg and none are needed, I'd rather keep it that way. thanks -mike

3 3

Re: ez-cdda sleep
by Mike Hearn 18 Oct '04

18 Oct '04

>> - storing context in server while entering USR1 signal handler (to be >> done without races, which will require some more work, as the server >> doesn't synchronize with the USR1 handler) I've implemented this in my local tree, and it works fine: Easy CD-DA gets further now. It is still being nailed by the copy protection system (called "Armadillo" apparently) but the splash screen appears now :) Today the BT engineer reconnected our line. So, now I just have to wait for ADSL to be activated, then I can flush my patch queue and get back to some real work. To eliminate the race at the top of SIGUSR1 handler I made server get_thread_context/set_thread_context RPCs fail with STATUS_RETRY if the context has not yet been uploaded, and adjusted the ntdll code to spin in a loop yielding the timeslice whenever it receives STATUS_RETRY. It's not fancy but it works, and on average only 1 yield is needed (obvious in hindsight I guess). The SIGCONTEXT is reloaded when the context override is cancelled, so set_thread_context on a suspended thread works as expected. thanks -mike

1 0

Problem using winelib
by Ross Quinlan 18 Oct '04

18 Oct '04

Hello, This is my first try with winelib ... I'm running RedHat 7.3. I've downloaded the wine source (wine-20040914) and built everything using ./tools/wineinstall. I'm trying the winemine example in the winelib doc. I've copied the .c, .h, and .rc files to a new directory winemine2 and in that directory I've run winemaker as follows: E> winemaker --lower-uppercase . Winemaker 0.6.0 Copyright 2000 Francois Gouget <fgouget(a)codeweavers.com> for CodeWeavers Scanning the source directories... Fixing the source files... dialog.c main.c De.rc En.rc Es.rc Fr.rc It.rc Nl.rc Pl.rc Pt.rc Ru.rc Si.rc rsrc.rc dialog.h main.h resource.h Generating project files... . This generates one new file, "Makefile" (no Makefile.in, configure) so I can't run ./configure --with-wine etc. If I try a simple make, here's the result: E> make all winebuild -o winemine2.exe.dbg.c --debug -C. dialog.c main.c winegcc -c -mno-cygwin -I. -o winemine2.exe.dbg.o winemine2.exe.dbg.c winegcc -c -mno-cygwin -I. -o dialog.o dialog.c winegcc -c -mno-cygwin -I. -o main.o main.c wrc -I. -foDe.res De.rc De.rc:22:21: Error: parse error make: *** [De.res] Error 1 I'm therefore contacting this address as suggested in the winemaker documentation. Any help for a complete novice would be appreciated! Regards, Ross

3 2

Fwd: Re: Fwd: Re: about a book I'm thinking of writing
by Wesley Parish 18 Oct '04

18 Oct '04

This is in relation to an idea I had a few months ago. Bruce Perens stated that he didn't see any future at present for a book on ReactOS, but he would definitely be interested in a book on Win internals, from one of the Wine developers. Is there anyone on this list who'd be interested? FWIW, I'd be willing to edit, if necessary. (That's something I'm not unfamiliar with.) Wesley Parish ---------- Forwarded Message ---------- Subject: Re: Fwd: Re: about a book I'm thinking of writing Date: Mon, 18 Oct 2004 13:53 From: Alexandre Julliard <julliard(a)winehq.org> To: Wesley Parish <wes.parish(a)paradise.net.nz> Wesley Parish <wes.parish(a)paradise.net.nz> writes: > I wrote an email to Bruce Perens on doing something for the ReactOS > project, and he sent me this reply. Do you think there'd be anyone in the > Wine HQ who'd be interested and capable of writing a book on the Wine > internals a la "Inside Windows NT" or "VAX/VMS Internals and Data > Structures", or suchlike? I don't know of anyone, but you may want to ask this on the wine-devel list. -- Alexandre Julliard julliard(a)winehq.org ------------------------------------------------------- -- Wesley Parish * * * Clinersterton beademung - in all of love. RIP James Blish * * * Mau e ki, "He aha te mea nui?" You ask, "What is the most important thing?" Maku e ki, "He tangata, he tangata, he tangata." I reply, "It is people, it is people, it is people."

1 0

Appdb - Add 'Delete' button to comments when the user is an admin
by Chris Morgan 18 Oct '04

18 Oct '04

This patch adds a delete button to comments when the user is an admin. It will need to be modified slightly when application maintainers are added to appdb. The hope is that we can start to clear the stale comments out of the database to increase the signal-to-noise. After deleting the comment the parentId of the child comments are adjusted to be the parentId of the deleted comment. I'm still a php rookie, comments, questions are welcome ;-) Chris

1 0

Re: Temporary fix to trying to put a pointer in a DWORD
by Dmitry Timoshkov 17 Oct '04

17 Oct '04

"Vincent Béron" <vberon(a)mecano.gme.usherb.ca> wrote: > We try to put a pointer in a DWORD in a static initialization of > CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have > to find a better solution though. Another way to fix it is to use full 'DWORD Spare[2]' to store a pointer on Win64 and leave it as it is now for Win32. -- Dmitry.

3 4

Re: Fix various function prototypes
by Rolf Kalbermatter 17 Oct '04

17 Oct '04

Vincent Béron wrote: >MSDN says it's void >http://msdn.microsoft.com/library/default.asp?url=/library/en- >us/shellcc/platform/shell/reference/functions/shcocreateinstance.asp > >I don't have latest PSDK. > >This will need to be investigated some more (although I'm leaning >towards HRESULT). My own tests seem to indicate that the function really returns some codes which are consistent with HRESULTs. Also my SDK (from February 2003) declares the functions as SHSTDAPI which is an abbreviation for "extern HRESULT __stdcall". So MSDN seems to be wrong here and besides returning them anyhow in the implementation eventhough some clients may ignore them based on MSDN documentation seems the correct way to me! Rolf Kalbermatter

1 0

Re: Enable _WIN64
by Robert Shearman 17 Oct '04

17 Oct '04

Vincent Béron wrote: >Index: wine/dlls/oleaut32/oaidl_p.c >=================================================================== >RCS file: /home/wine/wine/dlls/oleaut32/oaidl_p.c,v >retrieving revision 1.4 >diff -u -r1.4 oaidl_p.c >--- wine/dlls/oleaut32/oaidl_p.c 7 Oct 2004 03:06:49 -0000 1.4 >+++ wine/dlls/oleaut32/oaidl_p.c 16 Oct 2004 04:50:00 -0000 >@@ -11119,7 +11119,7 @@ > }; > > >-#if !defined(__RPC_WIN32__) >+#if !defined(__RPC_WIN32__) && !defined(__RPC_WIN64__) > #error Invalid build platform for this stub. > #endif > > > oaidl.idl needs to be regenerated from a newer MIDL that knows about Win64 instead of this hack. Rob

1 0

Re: Fix various function prototypes
by Robert Shearman 17 Oct '04

17 Oct '04

Vincent Béron wrote: >SHCoCreateInstance returns void, not HRESULT. >Some functions had a different prototype than their declaration. > >Changelog: >Fix various function prototypes. > > Some of these are wrong if we want binary compatibility with Windows 64-bit because e.g.: sizeof(unsigned long) on linux != sizeof(unsigned long) on Windows If a parameter to a function is "unsigned long" then we will have to change it to "ULONG" instead. Rob

1 0

Re: Freetype portability fix for older versions - improved
by Rein Klazes 17 Oct '04

17 Oct '04

On 15 Sep 2004 11:17:10 -0400, you wrote: > Tested on both freetype 2.1.2 and freetype 2.1.4. > > Changelog: > Use the preferred FT_ENCODING values rather than ft_encoding. > > +#ifndef FT_ENCODING_NONE > +#define FT_ENCODING_NONE ft_encoding_none > +#endif > +#ifndef FT_ENCODING_MS_SYMBOL > +#define FT_ENCODING_MS_SYMBOL ft_encoding_symbol > +#endif > +#ifndef FT_ENCODING_UNICODE > +#define FT_ENCODING_UNICODE ft_encoding_unicode > +#endif > +#ifndef FT_ENCODING_APPLE_ROMAN > +#define FT_ENCODING_APPLE_ROMAN ft_encoding_apple_roman > +#endif The patch works, but is not quite correct and doing the opposite of what you claim: the FT_ENCODING's are never defined but are enums. Therefore "ifndef FT_ENCODING_XYZ" is always true and you always use the depreciated ft_encodings. On old freetype2: enum FT_Encoding { ft_encoding_xyz, ... On Newer freetype2: enum FT_Encoding { FT_ENCODING_XYZ, ... #define ft_encoding_xyz FT_ENCODING_XYZ So to use FT_ENCODING_XYZ in the code and still compile with older freetype2's, we need to test: #ifndef ft_encoding_xyz Patch attached, tested to compile with freetype 2.0.9 and 2.1.7. Changelog: dlls/gdi : freetype.c Test whether the ft_encoding's are defined, not the FT_ENCODING's. Rein. -- Rein Klazes rklazes(a)xs4all.nl

1 0

Re: winesetuptk0.72/tcltk-winesetuptk-0.72
by Ivan Leo Puoti 17 Oct '04

17 Oct '04

> /tcltk-winesetuptk-0.72/build.sh Winesetuptk isn't maintained any more, and it isn't needed to configure wine. Why do you need it? Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

1 0

Re: Honor --disable-debug or --disable-trace completely
by Vincent Béron 17 Oct '04

17 Oct '04

Le sam 16/10/2004 à 22:29, Vincent Béron a écrit : > (Yes, the patch is gzip as it's over 200k) > > wine/debug.h has some tests based on NO_{DEBUG,TRACE}_MSGS, which is set > (or not) in config.h. Quite a few files didn't #include config.h before > wine/debug.h, so some debugmsgs were always compiled in, even with > ./configure --disable-debug. > > Now maybe we want to install config.h as well, as debug.h is already > installed. I'll leave that one to Alexandre. > > Changelog: > Force inclusion of config.h before wine/debug.h. Don't commit yet, make depend fails (config.h has been added to some includes in some dirs). I'll resend. Vincent

1 0

Re: Use LLP64 compatible sized-types for LONG and DWORD
by Dmitry Timoshkov 17 Oct '04

17 Oct '04

"Vincent Béron" <vberon(a)mecano.gme.usherb.ca> wrote: > Changelog: > Change the type of LONG and DWORD to be int based instead of long based > for Win64 compatibility. It would be cleaner IMO to use that only when compiling with _WIN64 defined, that would avoid affecting the Win32 target. -- Dmitry.

2 2

Re: Fix various function prototypes
by Dmitry Timoshkov 17 Oct '04

17 Oct '04

"Vincent Béron" <vberon(a)mecano.gme.usherb.ca> wrote: > SHCoCreateInstance returns void, not HRESULT. According to Platform SDK headers SHCoCreateInstance returns HRESULT. P.S. Do you compile Wine with _WIN64 defined on Alpha? That would be really cool to see that going, clean our headers and fix all warnings caused by 32 bit pointer assumptions. -- Dmitry.

2 3

RFH: winuser.h
by Dimitrie O. Paun 16 Oct '04

16 Oct '04

Can someone please help me with the value of LBS_COMBOBOX? TIA, Dimi.

2 1

programs/winecfg/libraries.c warnings regressions
by Gerald Pfeifer 16 Oct '04

16 Oct '04

I believe the following patch of programs/winecfg/libraries.c revision 1.3 date: 2004/09/28 03:55:16; author: julliard; state: Exp; lines: +288 -501 Mike Hearn <mike(a)navi.cx> - rewrite the transaction system to be based on a settings overlay, to have a nicer API, and to actually work (always a bonus) - change the libraries page to be based on a listbox rather than a treeview, clean up and shrink the code - add accelerator keys to the libraries page, focus management - make the window title reflect what the user is currently editing - remove bogus root warning - remove some unused control IDs in resource.h - start converting the x11drv dialog to kernel_style from javaStyle - bugfixing introduced the following warnings libraries.c:261: warning: `mode' might be used uninitialized in this function libraries.c:264: warning: `str' might be used uninitialized in this function (which are the only ones of this kind for a full Wine build). Gerald

3 2

programs/winecfg/winecfg.c and setkey()
by Gerald Pfeifer 16 Oct '04

16 Oct '04

programs/winecfg/winecfg.c now defines a function called setkey(). This same function also appears in stdlib.h and unistd.h on FreeBSD 5.x systems, so the build on these platforms fails with winecfg.c:136: error: conflicting types for `setkey' /usr/include/stdlib.h:211: error: previous declaration of `setkey' (How) can we address this in Wine? Gerald -- Gerald Pfeifer (Jerry) gerald(a)pfeifer.com http://www.pfeifer.com/gerald/

2 1

winesetuptk0.72/tcltk-winesetuptk-0.72
by C. Andrews La Varre 16 Oct '04

16 Oct '04

Hello. Trying to extract / build these on RedHat RHEL 3.0. I get the attached results from /tcltk-winesetuptk-0.72/build.sh with the end result that [Error] Static tk library build failed As a result the winesetuptk installation fails. My kernel version is 2.4.21-20.EL Thanks, Andy La Varre [root@m60 root]# cd /archives/computer/linux [root@m60 linux]# ls bin etc lindesk linux.mdb vmware windesk wine [root@m60 linux]# cd wine [root@m60 wine]# ls wine-20040914-1wbel3winehq.i686.rpm winesetuptk-0.72.tar.gz wine-20040914-1wbel3winehq.src.rpm xwine winesetuptk XWine-0.3.2_en.tar.gz [root@m60 wine]# cd winesetuptk [root@m60 winesetuptk]# ls winesetuptk0.72 [root@m60 winesetuptk]# cd winesetuptk0.72 [root@m60 winesetuptk0.72]# ls tcltk-winesetuptk-0.72 winesetuptk-0.72 [root@m60 winesetuptk0.72]# cd tcltk-winesetuptk-0.72 [root@m60 tcltk-winesetuptk-0.72]# ls build.sh cwdialog itcl3.1.0 mktclapp tk8.3.2 build.txt img1.2.4 local tcl8.3.2 [root@m60 tcltk-winesetuptk-0.72]# sh build.sh [Building tcl] Installing libtcl8.3.a to /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/local/lib/ Installing tclsh as /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/local/bin/tclsh8.3 Installing tclConfig.sh to /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/local/lib/ Installing libtclstub8.3.a to /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/local/lib/ Installing header files Installing library files to /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/local/lib/tcl8.3 Installing library http2.3 directory Installing library http1.0 directory Installing library opt0.4 directory Installing library msgcat1.0 directory Installing library tcltest1.0 directory Installing library encoding directory Installing top-level (.1) docs Cross-linking top-level (.1) docs Installing C API (.3) docs Cross-linking C API (.3) docs Installing command (.n) docs Cross-linking command (.n) docs [Building tk] cc -pipe -c -O -D__NO_STRING_INLINES -D__NO_MATH_INLINES -Wall -Wconversion -Wno-implicit-int -fPIC -I/archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix -I/archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/../generic -I/archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/../bitmaps -I/archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tcl8.3.2/generic -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_PW_GECOS=1 -DSTATIC_BUILD=1 -DTCL_NO_DEPRECATED /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/../generic/tk3d.c In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:21, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:83:29: X11/Xlib.h: No such file or directory In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:21, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:581: syntax error before "Bool" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:581: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:582: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:583: syntax error before "event" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:583: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:584: syntax error before "root" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:584: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:585: syntax error before "subwindow" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:585: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:586: syntax error before "time" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:586: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:591: syntax error before "same_screen" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:591: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:592: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:597: syntax error before "Bool" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:597: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:598: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:599: syntax error before "window" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:599: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:600: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:601: syntax error before "XActivateEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:601: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:602: syntax error before "XDeactivateEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:602: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:657: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:657: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:660: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:660: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:662: syntax error before "window" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:662: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:671: syntax error before "changes" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:671: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:673: syntax error before "atts" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:673: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:692: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:692: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:787: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:887: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:890: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:985: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:985: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1015: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1015: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1049: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1049: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1061: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1061: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1062: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1062: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1063: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1063: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1064: syntax error before "stipple" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1064: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1065: syntax error before "activeStipple" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1065: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1066: syntax error before "disabledStipple" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1066: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1067: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1092: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1094: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1337: syntax error before "XErrorEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1339: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1341: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1346: syntax error before "XEvent" In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:1359, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:21, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:37: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:37: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:39: syntax error before "Tk_3DBorderGC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:40: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:45: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:50: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:58: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:72: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:73: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:77: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:80: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:90: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:95: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:115: syntax error before "XSetWindowAttributes" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:122: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:126: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:146: syntax error before "XWindowChanges" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:167: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:187: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:229: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:241: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:246: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:251: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:254: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:259: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:264: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:269: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:274: syntax error before "Tk_FontId" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:274: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:279: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:281: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:284: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:287: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:291: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:297: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:300: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:305: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:307: syntax error before "Tk_GCForColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:308: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:308: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:324: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:330: syntax error before "Tk_GetBitmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:331: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:333: syntax error before "Tk_GetBitmapFromData" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:335: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:340: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:341: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:343: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:344: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:344: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:346: syntax error before "Tk_GetColormap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:347: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:367: syntax error before "Tk_GetGC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:369: syntax error before "XGCValues" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:369: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:396: syntax error before "Tk_GetPixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:397: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:397: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:415: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:419: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:421: syntax error before "Colormap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:421: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:430: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:433: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:441: syntax error before "Tk_InternAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:442: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:479: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:483: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:486: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:504: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:541: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:544: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:549: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:583: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:592: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:595: syntax error before "Colormap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:599: syntax error before "Visual" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:603: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:621: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:626: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:640: syntax error before "Tk_AllocBitmapFromObj" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:642: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:648: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:650: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:693: syntax error before "Tk_GetBitmapFromObj" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:694: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:696: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:697: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:761: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:764: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:768: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:771: syntax error before "Tk_Outline" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:774: syntax error before "Tk_Outline" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:777: syntax error before "Tk_Outline" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:780: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:787: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:795: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:798: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:814: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:836: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:836: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:837: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:837: `GC' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:837: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:838: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:839: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:841: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:845: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:845: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:846: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:847: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:850: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:852: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:857: syntax error before "XSetWindowAttributes" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:859: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:860: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:865: syntax error before "XWindowChanges" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:870: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:876: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:888: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:892: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:893: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:894: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:895: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:896: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:897: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:898: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:900: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:900: `Font' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:900: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:902: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:903: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:904: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:905: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:907: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:909: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:910: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:912: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:913: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:913: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:913: `GC' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:913: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:918: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:920: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:920: `Pixmap' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:920: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:921: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:921: `Pixmap' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:921: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:923: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:923: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:924: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:924: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:924: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:925: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:925: `Colormap' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:925: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:931: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:931: syntax error before "XGCValues" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:931: `GC' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:931: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:940: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:940: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:940: `Pixmap' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:940: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:945: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:947: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:947: syntax error before "Colormap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:947: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:950: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:951: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:954: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:954: `Atom' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:954: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:967: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:969: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:970: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:977: syntax error before "Atom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:988: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:989: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:990: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1001: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1004: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1005: syntax error before "Colormap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1006: syntax error before "Visual" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1007: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1013: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1014: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1020: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1020: `Pixmap' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1020: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1022: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1022: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1036: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1036: `Pixmap' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1036: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1037: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1037: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1056: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1057: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1058: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1059: syntax error before "Tk_Outline" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1060: syntax error before "Tk_Outline" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1061: syntax error before "Tk_Outline" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1062: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1064: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1066: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1067: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1071: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1074: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1074: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1079: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkDecls.h:1079: warning: data definition has no type or storage class In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:64, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkPort.h:32, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:27, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /usr/include/time.h:184: `time' redeclared as different kind of symbol /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:586: previous declaration of `time' In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkPort.h:32, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:27, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:77:22: X11/Xlib.h: No such file or directory /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:78:28: X11/cursorfont.h: No such file or directory /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:79:24: X11/keysym.h: No such file or directory /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:80:23: X11/Xatom.h: No such file or directory /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:81:24: X11/Xproto.h: No such file or directory /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:82:27: X11/Xresource.h: No such file or directory /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/unix/tkUnixPort.h:83:23: X11/Xutil.h: No such file or directory In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:47: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:50: syntax error before "Window" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:50: `Window' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:50: warning: parameter names (without types) in function declaration /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:53: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:62: syntax error before "TkClassCreateProc" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:62: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:74: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:74: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:84: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:84: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:108: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:108: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:118: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:118: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:119: conflicting types for `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:104: previous declaration of `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:122: syntax error before "lastEventTime" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:122: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:162: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:162: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:221: syntax error before "cursorFont" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:221: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:388: syntax error before "multipleAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:388: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:390: syntax error before "incrAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:390: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:391: syntax error before "targetsAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:391: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:392: syntax error before "timestampAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:392: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:393: syntax error before "textAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:393: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:394: syntax error before "compoundTextAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:394: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:395: syntax error before "applicationAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:395: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:396: syntax error before "windowAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:396: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:397: syntax error before "clipboardAtom" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:397: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:421: syntax error before "commProperty" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:421: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:422: syntax error before "registryProperty" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:422: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:424: syntax error before "appNameProperty" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:424: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:435: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:435: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:435: `XID' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:435: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:502: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:502: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:511: syntax error before "TkDisplay" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:511: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:533: conflicting types for `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:119: previous declaration of `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:537: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:537: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:645: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:645: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:646: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:650: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:650: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:653: `window' redeclared as different kind of symbol /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:662: previous declaration of `window' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:663: conflicting types for `parentPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk.h:665: previous declaration of `parentPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:668: conflicting types for `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:533: previous declaration of `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:703: syntax error before "changes" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:703: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:707: syntax error before "atts" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:707: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:785: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:785: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:793: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:793: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:814: syntax error before "Pixmap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:814: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:814: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:816: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:816: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:817: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:817: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:826: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:826: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:871: syntax error before '*' token In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:878, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:38: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:39: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:39: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:46: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:48: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:51: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:58: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:61: syntax error before "TkDisplay" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:79: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:82: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:82: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:91: syntax error before "TkCurrentTime" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:91: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:91: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:95: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:99: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:101: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:106: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:116: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:119: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:121: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:122: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:122: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:128: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:130: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:141: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:142: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:147: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:147: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:147: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:153: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:153: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:153: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:168: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:170: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:178: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:182: syntax error before "keysym" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:193: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:199: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:201: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:210: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:212: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:215: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:223: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:223: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:223: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:225: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:225: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:225: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:239: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:239: `TkpMakeWindow' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:244: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:244: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:247: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:256: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:259: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:268: syntax error before "TkDisplay" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:271: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:278: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:282: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:284: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:287: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:291: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:295: syntax error before "TkClassProcs" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:301: syntax error before "TkStringToKeysym" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:301: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:308: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:310: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:312: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:312: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:312: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:314: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:316: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:319: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:322: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:325: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:327: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:329: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:355: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:355: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:364: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:505: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:508: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:511: syntax error before "KeySym" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:513: syntax error before "TkpGetKeySym" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:514: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:514: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:516: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:522: syntax error before "TkWindow" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:522: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:524: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:525: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:526: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:529: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:530: syntax error before "TkDisplay" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:534: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:534: syntax error before "XColor" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:534: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:537: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:537: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:537: `Time' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:537: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:539: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:540: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:541: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:542: syntax error before "Display" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:545: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:546: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:547: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:547: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:547: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:550: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:551: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:554: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:554: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:556: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:556: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:556: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:558: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:558: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:558: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:563: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:564: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:566: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:568: syntax error before "keysym" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:571: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:573: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:574: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:577: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:578: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:579: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:582: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:582: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:582: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:583: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:583: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:583: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:588: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:588: `tkpMakeWindow' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:590: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:590: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:591: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:594: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:595: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:598: syntax error before "TkDisplay" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:599: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:600: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:601: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:602: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:603: syntax error before "XEvent" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:605: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:606: syntax error before "TkClassProcs" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:608: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:608: `KeySym' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:608: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:610: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:611: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:612: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:612: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:612: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:613: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:614: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:615: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:616: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:617: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:618: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:619: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:628: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:628: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:631: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:817: syntax error before "GC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:818: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:819: syntax error before "KeySym" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:820: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:820: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:820: `KeySym' declared as function returning a function /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:820: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:821: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:822: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:827: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkIntDecls.h:827: warning: data definition has no type or storage class In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:18, from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:1064: syntax error before "XImage" In file included from /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:16: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:33: syntax error before "Screen" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:33: warning: no semicolon at end of struct or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:34: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:38: syntax error before "colormap" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:38: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:52: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:52: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:55: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:55: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:58: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:58: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:62: syntax error before "shadow" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:62: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:66: syntax error before "bgGC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:66: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:68: syntax error before "darkGC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:68: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:71: syntax error before "lightGC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:71: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:76: conflicting types for `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tkInt.h:668: previous declaration of `nextPtr' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:81: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:81: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:94: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:94: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:96: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.h:97: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:30: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:35: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:38: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Alloc3DBorderFromObj': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:87: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:87: (Each undeclared identifier is reported only once /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:87: for each function it appears in.) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:92: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:108: warning: implicit declaration of function `ScreenOfDisplay' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:108: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:108: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:109: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:133: `firstBorderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:134: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:138: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:138: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:139: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:152: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Get3DBorder': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:192: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:192: `existingBorderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:192: warning: left-hand operand of comma expression has no effect /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:194: `XGCValues' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:194: syntax error before "gcValues" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:195: `XColor' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:196: invalid operands to binary * /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:198: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:200: request for member `borderInit' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:204: request for member `borderTable' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:204: request for member `borderTable' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:206: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:209: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:209: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:210: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:232: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:232: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:233: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:234: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:235: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:241: `None' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:255: `gcValues' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:256: `GCForeground' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Draw3DRectangle': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:283: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_NameOf3DBorder': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:330: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:330: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: At top level: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:351: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:353: warning: return type defaults to `int' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_3DBorderColor': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:355: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: At top level: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:375: syntax error before "Tk_3DBorderGC" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:376: warning: return type defaults to `int' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_3DBorderGC': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:382: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:382: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:384: `None' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:401: syntax error before "None" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Free3DBorder': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:427: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:427: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:428: `Display' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:428: warning: implicit declaration of function `DisplayOfScreen' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:429: `prevPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:436: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:447: `None' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `FreeBorderObjProc': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:531: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:531: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `DupBorderObjProc': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:566: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:566: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_SetBackgroundFromBorder': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:598: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:600: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Draw3DPolygon': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:752: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:754: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:766: `XPoint' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:766: syntax error before "poly" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:768: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:769: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:769: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:772: `Display' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:772: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:774: `None' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:800: `p1Ptr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:800: subscripted value is neither array nor pointer /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:801: `p2Ptr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:801: subscripted value is neither array nor pointer /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:847: subscripted value is neither array nor pointer /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:847: warning: left-hand operand of comma expression has no effect /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:848: warning: left-hand operand of comma expression has no effect /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:859: `newB1' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:860: `newB2' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:862: `poly' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:865: `b1' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:865: `b2' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:897: `perp' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:900: `c' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:901: `shift1' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:902: `shift2' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:916: `gc' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:920: warning: implicit declaration of function `XFillPolygon' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:920: `Convex' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:921: `CoordModeOrigin' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:847: warning: value computed is not used /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:847: warning: value computed is not used /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Fill3DRectangle': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:960: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:968: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:994: warning: implicit declaration of function `XFillRectangle' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:994: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:994: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Fill3DPolygon': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1025: syntax error before "Drawable" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1027: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1039: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1041: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1041: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1042: `Complex' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1042: `CoordModeOrigin' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: At top level: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1067: syntax error before "TkDisplay" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1067: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1068: syntax error before '{' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1070: syntax error before '&' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1070: conflicting types for `Tcl_InitHashTable' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tcl8.3.2/generic/tclDecls.h:583: previous declaration of `Tcl_InitHashTable' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1070: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1093: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1093: `p1Ptr' used prior to declaration /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1093: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1094: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1094: `p2Ptr' used prior to declaration /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1094: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1099: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1099: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1101: syntax error before '{' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1124: syntax error before "if" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1128: syntax error before "for" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1130: conflicting types for `cosine' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1126: previous declaration of `cosine' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1130: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1131: `i' undeclared here (not in a function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1131: conflicting types for `shiftTable' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1117: previous declaration of `shiftTable' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1131: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1132: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1135: warning: initialization makes pointer from integer without a cast /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1135: initializer element is not constant /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1135: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1136: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1136: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1136: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1137: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1137: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1137: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1138: syntax error before "if" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1140: redefinition of `dy' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1137: `dy' previously defined here /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1140: initializer element is not constant /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1140: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1141: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1146: redefinition of `dx' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1136: `dx' previously defined here /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1146: initializer element is not constant /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1146: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1147: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1186: syntax error before "XPoint" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1186: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1187: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1187: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1188: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1188: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1189: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1189: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1190: syntax error before '*' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1190: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1191: syntax error before '{' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1200: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1200: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1200: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1200: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1200: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1201: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1201: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1201: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1201: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1201: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1202: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1202: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1202: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1202: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1202: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1203: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1203: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1203: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1203: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1203: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1205: syntax error before "if" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1208: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1208: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1208: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1208: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1208: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1209: initializer element is not constant /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1209: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1210: syntax error before "if" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1212: redefinition of `q' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1209: `q' previously defined here /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1212: initializer element is not constant /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1212: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1213: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1219: redefinition of `p' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1208: `p' previously defined here /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1219: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1219: request for member `y' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1219: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1219: request for member `x' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1219: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1220: redefinition of `q' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1212: `q' previously defined here /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1220: initializer element is not constant /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1220: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1221: syntax error before "if" /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1223: redefinition of `q' /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1220: `q' previously defined here /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1223: initializer element is not constant /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1223: warning: data definition has no type or storage class /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1224: syntax error before '}' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `Tk_Get3DBorderFromObj': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1259: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1261: invalid operands to binary * /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1261: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1274: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1277: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1277: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1278: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1298: request for member `borderTable' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1298: request for member `borderTable' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1302: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1304: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1304: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1305: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c: In function `TkDebugBorder': /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1385: `borderPtr' undeclared (first use in this function) /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1388: invalid operands to binary * /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1388: syntax error before ')' token /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1391: request for member `borderTable' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1391: request for member `borderTable' in something not a structure or union /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1393: syntax error before ')' token /usr/include/sys/stat.h: At top level: /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:1131: storage size of `shiftTable' isn't known /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:30: warning: `BorderInit' declared `static' but never defined /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:35: warning: `Intersect' declared `static' but never defined /archives/computer/linux/wine/winesetuptk/winesetuptk0.72/tcltk-winesetuptk-0.72/tk8.3.2/generic/tk3d.c:38: warning: `ShiftLine' declared `static' but never defined {standard input}: Assembler messages: {standard input}:661: Error: symbol `dy' is already defined {standard input}:667: Error: symbol `dx' is already defined {standard input}:714: Error: symbol `q' is already defined {standard input}:720: Error: symbol `p' is already defined {standard input}:726: Error: symbol `q' is already defined {standard input}:732: Error: symbol `q' is already defined gmake: *** [tk3d.o] Error 1 [Error] Static tk library build failed

1 0

CoCreateInstance now fails on msxml4.dll
by Bill Medland 15 Oct '04

15 Oct '04

Any ideas on this? (The problem has become apparent since 20040914 but was probably lurking before) Working with a current Wine environment (as of yesterday); fresh .wine created and the DllOverride added to call native ole32 If you run regsvr32 /s msxml4.dll it registers itself as at %SystemRoot%\system\msxml4.dll (As of 20040914 it would register itself as at c:\windows\system\msxml4.dll) If you try to CoCreateInstance (... a class in msxml4.dll e.g. SAXXMLReader40...) then it now fails. (It succeeds under the builtin ole32) I have run a +relay trace. Between the call to RegQueryKey that gets the path, complete with %SystemRoot%, and the call to LoadLibraryEx (called with %SystemRoot%) there is no apparent attempt to call a function to expand the string (and in particular it does not call ExpandEnvironmentString) I've even looked at all the calls between the start of the CoCreateInstance and the LoadLibrary and I don't see anything obviously problematic I will look at the full trace but I'm not hopefull of spotting what earlier call resulted in ole32 not trying to expand the string. Does anyone have any suggestions as to how to investigate further? -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

1 1

Problems using set in winedbg
by Bill Medland 15 Oct '04

15 Oct '04

Am I just doing this wrong or is it a bug? I am trying to figure out a problem in an application. I want to turn on reg and relay once I am into the program. (If they are turned on initially I can't get into the program because of some sort of timeout or something). I am following the instructions in the Wine Developer's Guide. I start the program itself in one terminal and get past the timeout-critical bit. In another terminal I start winedbg, use info process to find the id (there are three processes by this point), and attach to the process. I can now do things like info share info regs etc. c/Ctrl-C Each time I get the Wine-dbg> prompt If I type set + reg <return> the debugger seems to sort of hang. It doesn't give the prompt. As time passes it complains about being not able to find rhe pdb files etc. but at no point do I get the opportunity to tell it to continue. I have tried leaving it for 10 minutes after the last pdb complaint but still no success. Am I supposed to get a prompt? -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

2 3

Re: [janitor] tools -Wwrite-strings cleanup
by Alexandre Julliard 15 Oct '04

15 Oct '04

Daniel Marmier <d.marmier(a)bluewin.ch> writes: > This is one situation I would like to discuss a bit more. > Some code uses a mix of static and dynamic structures containing strings. > The static instances have constant strings, the others are xmalloc'd. These > strings must be declared char *, since we need to be able to free them. But > this prevents us from initializing the static ones with constant strings. > > Solution 1 (double casting to avoid constness removal warning) > s->name = FAKE_CHARPTR("hello"); > > Solution 2 (shows clearly that we mix constant/variable and avoids casting): > union { > const char *c; > char *v; > } name; > s->name.c = "hello"; > > Can you think of a better solution? What is preferable? I think this sort of construct should be avoided. If we mix static and allocated data in the same structure, there is a big risk that we will one day try to free static data, with random results. We should change the code so that it doesn't need that, either by storing the static data in a separate structure, or for non performance critical code by allocating a copy of the static data. -- Alexandre Julliard julliard(a)winehq.org

3 2

Microsoft Data Access Components
by Tom Hibbert 15 Oct '04

15 Oct '04

Hi All, I've been given the thankless task of getting a legacy application running under Linux. It requires the Microsoft Data Access Components (MDAC) to run, but I cant get them to install (either 2.6 or 2.8). Does anyone have a howto or can give me the skinny on what sacrifices I need to make to get this installed? I'm running Gentoo Wine 20040716. Thanks in advance Tom

2 1

winetest results refused when run by wine
by Robert Reif 15 Oct '04

15 Oct '04

Couldn't winetest fill in the proper test results fields necessary for acceptance when compiled to an exe.so and run in wine?

8 13

Re: shlexec - skip argument identifier
by Vitaliy Margolen 15 Oct '04

15 Oct '04

Oops, resend with the right patch. Vitaliy Margolen Wednesday, October 13, 2004, 5:58:22 AM, Vitaliy Margolen wrote: > Second char of argument identifier was getting into program name: > wine start http://yahoo.com > was executing: > winebrowser \"http://yahoo.com\"1 > Vitaliy Margolen > changelog: > dlls/shel32/shlexec.com > fix parameter parsing

3 2

env lookup in loading a dll
by Bill Medland 15 Oct '04

15 Oct '04

Anyone any ideas about this? With recent changes in Wine, registering msxml4.dll results in the path in the registry being %SystemRoot%\system\msxml4.dll (which is correct). Previously it was the explicit C:\windows\system\msxml4.dll. The result is that CoCreateInstance results in an attempt to LoadLibraryExW ("%SystemRoot%..., which LoadLibraryEx cannot handle (even under Windows). There does not appear to be an attempt to call GetEnvironmentVariable or GetWindowDirectory between the registry access that gets the InProcServer32 and the call to LoadLibraryExW. Does anyone have any idea where the fault is likely to be? (Until I create a small test case I can't run with +relay) -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

1 1

Stupid thing to try ...
by Ivan Leo Puoti 15 Oct '04

15 Oct '04

You can get the wine dlls build for windows from our sf.net page, look for the wine-dlls packages. Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

1 0

Re: Commctl32 Stubs
by Dmitry Timoshkov 14 Oct '04

14 Oct '04

"Thorsten Kani" <beebix(a)gmx.net> wrote: > +BOOL WINAPI > +SetPathWordBreakProc(DWORD par1, HWND hwndTo) > +{ > + LRESULT result; > + > + result=SendMessageA (hwndTo,EM_GETWORDBREAKPROC,0,0); > + TRACE("(par1: %lx, HwndTo: %p, CurrentPWBProc: %lx) Stub!\n", par1, hwndTo, result); ... > +BOOL WINAPI > +MirrorIcon(LONG par1) > +{ > + TRACE("(par1: %lx) empty stub!\n", par1); > + return FALSE; > +} You have to use FIXME not TRACE for stubs. -- Dmitry.

1 0

Re: Stupid thing to try ...
by Steven Edwards 14 Oct '04

14 Oct '04

--- Lars Segerlund <lars.segerlund(a)comsys.se> wrote: > Ok, I get it, wine must us a binary loader for the windows dll's ... > areasonable ... Under Windows you can just compile the dll using mingw and then drop the dll in to the program direct that you want to test. Lets say you have a app name foo.exe you can copy the wine comctl32.dll to that directory that contains foo.exe and the make a copy of foo.exe and name the copy foo.exe.local When you create a *.exe.local file it exposes a hidden hack in Windows that forces it to search the local directory first for dlls no matter what the registry setting is. Note this only works for comctl32, shell32, shlwapi, ole32 and a few others. Dlls from Wine like user32, gdi32, ntdll, kernel32 and friends cannot be loaded on Windows. Like the other guy suggested you should checkout ReactOS. We support building a good number of the Wine dlls for Windows. Thanks Steven _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

1 0

Re: Commctl32 Stubs
by Robert Shearman 14 Oct '04

14 Oct '04

Thorsten Kani wrote: > > Added > -SetPathWordBreakProc > -MirrorICON > -ImageList_SetColorTable > > This Patch makes MSGina and native Shlwapi happy. > With it, commctl32 can be replaced on Win2k SP4. Thanks for the patch, but I'd rather get the params correct for the stubs. Can you let me know where each function is used? > Changelog: New Stubs in Commctl32: SetPathWordBreakProc, MirrorICON > and ImageList_SetColorTable MirrorIcon is a nop on Wine at the moment. ImageList_SetColorTable is trivial with using DIBs internally now. That just leaves SetPathWordBreakProc. I believe that should set the word break proc of an edit control to one that understands paths. It shouldn't be too hard to implement if you leave it with me. > PS: FirstPatchWarning: Be warned (: Good first patch, but leave it with and I should be able to implement these functions for you. Rob

2 1

unusual debug message
by Ivan Leo Puoti 14 Oct '04

14 Oct '04

does anyone know what this means, and what could be causing it? libpng warning: Invalid cHRM white point Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

1 0

Stupid thing to try ...
by Lars Segerlund 14 Oct '04

14 Oct '04

I was thinking of a silly thing to try, namely replacing windows dll's with wines, does anybody have any thoughts about it ? I just thought about it as a debugging trick I wanted to try, but I don't know enough to evaluate if it's even worth trying. So what about it, is it worth giving a shot ? Regards, Lars Segerlund.

3 2

Rename Wine User Guide to Wine User's Guide?
by Scott Ritchie 14 Oct '04

14 Oct '04

The Winelib documentation is called the Winelib User's Guide, but the Wine documentation is called the Wine User Guide. I think for consistency's sake we should rename the Wine User Guide to Wine User's Guide - afterall, it's a guide for the user, not about the user. Thoughts?

10 12

Rename Wine User Guide to Wine User's Guide?
by Scott Ritchie 14 Oct '04

14 Oct '04

The Winelib documentation is called the Winelib User's Guide, but the Wine documentation is called the Wine User Guide. I think for consistency's sake we should rename the Wine User Guide to Wine User's Guide - afterall, it's a guide for the user, not about the user. Thoughts? Thanks, Scott Ritchie scott(a)open-vote.org

2 1

Re: Rename Wine User Guide to Wine User's Guide?
by Ivan Leo Puoti 14 Oct '04

14 Oct '04

Let's do it like Microsoft, and call it "Wine 1.0 starts here" ;-) Ivan. ____________________________________________________________ Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it

1 0

[PATCH] DrawDibDraw flag handling
by Peter Riocreux 14 Oct '04

14 Oct '04

I got a lot of messages from this function about a particular flag (DDF_BACKGROUNDPAL) not being handled, so I tried to handle it. The MSDN docs are at <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/multimed/h…> I am coming to this completely cold, so I may be completely off target here, so if anyone can comment on whether I have done this right. I suspect that there needs to be explicit support for DDF_SAME_HDC, but I didn't really understand what it was wanting .... (Patch is against CVS from this AM (GMT) Index: dlls/msvideo/drawdib.c =================================================================== RCS file: /home/wine/wine/dlls/msvideo/drawdib.c,v retrieving revision 1.21 diff -u -r1.21 drawdib.c --- dlls/msvideo/drawdib.c 3 Jun 2004 23:19:51 -0000 1.21 +++ dlls/msvideo/drawdib.c 14 Oct 2004 14:46:47 -0000 @@ -311,7 +311,7 @@ whdd = MSVIDEO_GetHddPtr(hdd); if (!whdd) return FALSE; - if (wFlags & ~(DDF_SAME_HDC | DDF_SAME_DRAW | DDF_NOTKEYFRAME | DDF_UPDATE | DDF_DONTDRAW)) + if (wFlags & ~(DDF_SAME_HDC | DDF_SAME_DRAW | DDF_NOTKEYFRAME | DDF_UPDATE | DDF_DONTDRAW | DDF_BACKGROUNDPAL)) FIXME("wFlags == 0x%08lx not handled\n", (DWORD)wFlags); if (!lpBits) @@ -362,7 +362,10 @@ } } if (!(wFlags & DDF_DONTDRAW) && whdd->hpal) - SelectPalette(hdc, whdd->hpal, FALSE); + if ((wFlags & DDF_BACKGROUNDPAL) && ! (wFlags & DDF_SAME_HDC)) + SelectPalette(hdc, whdd->hpal, TRUE); + else + SelectPalette(hdc, whdd->hpal, FALSE); if (!(StretchBlt(whdd->hdc, xDst, yDst, dxDst, dyDst, whdd->hMemDC, xSrc, ySrc, dxSrc, dySrc, SRCCOPY))) ret = FALSE;

3 4

Re: MM doc update
by Mike Hearn 14 Oct '04

14 Oct '04

The problem with ASCII art is that the website uses a proportional font so it looks all messed up. I think a good janitorial task would be for somebody to install Inkscape and convert the ASCII art diagrams we have in the docs to SVG, so they could be rendered to PNGs or something and become a part of the developer guide. What do people think of this? If anybody is reading this and wants to help the Wine projcet but doesn't want to/can't write patches, this would be a great little job to do. BTW you can install Inkscape via autopackage (plug plug), using the nightly builds from here: http://navi.cx/~mike/inkscape thanks -mike

4 5

Re: alsa 0.9 + audio.c (Joris Huizer)
by Dietrich Teickner 14 Oct '04

14 Oct '04

Message: 2 Date: Wed, 13 Oct 2004 20:19:21 +0200 From: Joris Huizer <......> Subject: Re: alsa 0.9 + audio.c To: .... Dietrich Teickner wrote: >> Hi, >> >> Have anyone a solution for this problem ? >> >> Dietrich >> What *is* your problem?? Joris I and some others can not compile wine/dlls/winmm/winealsa. Wine audio.c can not compile with alsa 0.9 (SuSE 8.1) Dietrich audio.c:3224: warning: passing arg 3 of `snd_pcm_hw_params_set_buffer_time_near' makes integer from pointer without a cast audio.c:3226: warning: passing arg 3 of `snd_pcm_hw_params_set_period_time_near' makes integer from pointer without a cast audio.c:3231: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size' from incompatible pointer type audio.c:3231: too many arguments to function `snd_pcm_hw_params_get_period_size' audio.c:3232: too many arguments to function `snd_pcm_hw_params_get_buffer_size' make[2]: *** [audio.o] Fehler 1 make[2]: Verlassen des Verzeichnisses ?/home/sao2l02/Wine/wine/dlls/winmm/winealsa½ make[1]: *** [winmm/winealsa] Fehler 2 make[1]: Verlassen des Verzeichnisses ?/home/sao2l02/Wine/wine/dlls½ make: *** [dlls] Fehler 2 sao2l02@x2l:~/Wine/wine>

1 0

nonclient.c and sysmetrics.c
by William Poetra Yoga Hadisoesen 14 Oct '04

14 Oct '04

This is my first post here. I noticed that the caption buttons wine draws are different with those drawn by windows. I found the functions in nonclient.c and this led me to modify sysmetrics.c. I haven't succeeded yet... Should I post those two files here (the diffs)? Or does anyone have a comment? __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo

2 5

alsa 0.9 + audio.c
by Dietrich Teickner 13 Oct '04

13 Oct '04

Hi, Have anyone a solution for this problem ? Dietrich

2 1

RE: .so dependancies in winegcc
by Pierre d'Herbemont 13 Oct '04

13 Oct '04

Warren, On Mac OS X/Darwin .so and .dylib extensions are both used. In fact .dylib extension is used for dynamic libraries (libwine*.dylib) whereas dll.so and exe.so extensions are used for the dlls and the exe. So your patch would break winegcc on Mac OS X. Pierre.

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel