wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

Compilation errors when compiling without optimizations
by Shachar Shemesh 10 Sep '03

10 Sep '03

Hi, When trying to compile Wine without optimizations, the compilation fails. I'm trying clean sources, with the "--with-nptl" flag. The failure (so far, I'm still trying to figure these things out) are when compiling ntdll and the wine executable itself. Both cases, the problem is that same. The linker complains that "InterlockedCompareExchange" cannot be found. Adding kernel32 to the IMPORTS Makefile at dlls/ntdll and miscemu/wine seem to solve these problems, but I'm somewhat worried, and would like to get a second opinion before I submit a patch about this. Shachar p.s. For me (P-IV 1600MHZ) complete build compile takes 25 minutes. I've now switched to ccache, hoping I can bring it down even lower. Sh. -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

4 3

newbie - question: compiling winelib's winemine
by Deji Akinyemi 10 Sep '03

10 Sep '03

Hi there! I am trying to get up to speed on developing applications using wine. The winelib-user documentation recommends getting started by taking a look at the winemine (wine-xxxxxx/programs/winemine) code packaged with the library. I seem to be having different outcomes when I compile the code with the original Makefile and when I do so with the Makefile generated with winemaker. The original winemine makefile compiles the code without a problem and the program runs, however when I run the makefile generated by winemaker I get the following error: LD_LIBRARY_PATH=":$LD_LIBRARY_PATH" /usr/bin/wrc -I. -I/usr/local/include/wine/windows -o En.res En.rc En.rc:23:22: Error: parse error The wine-lib documentation mentions editing the Makefile.in file, I have looked at it and compared it with the original winmine Makefile. The winemaker makefile includes the files En.rc and Pt.rc in it RC_SRCS which is absent from the original Makefile. I removed the two entries with the result that the code compiles, but however fails to run. I do not get any error messages. Apart from those RC_SRCS entries I haven't noticed anything semantically that would result in the different behaviors that I am getting, granted, I may be missing some things. What parameters do I need to pass to winemaker to get this program to run, or are there certain changes I need to make to the Makefile that I a missing? Thanks for any help or advice. Deji. P.S. Any recommendations on winelib primers would also be much appreciated.

3 3

Re: FAQ: Update the ports section
by John Freed 10 Sep '03

10 Sep '03

Ah, the difference between British English and American English. <lang=en-uk>ManU are crushing Arsenal.</lang> <lang=en-us>ManU is crushing Arsenal.</lang> UK English insists on plural verbs for collective nouns (family, team, list, etc.), while US English generally uses singular verbs. (An exception is "couple" referring to a romantic pair -- "The couple are going to the store" would be acceptable on both sides of the Atlantic, although many Americans would say "is" even here.) John Freed ---original message follows--- You must send me some of the stuff you're smoking! "The list are now up to date" doesn't exist in english, you must choose "The lists are now up to date" for a plural "The list is now up to date" for a singular

2 1

Segmentation fault after new wine update and install
by Juraj Hercek 10 Sep '03

10 Sep '03

Hello, I've updated today from wine and got into troubles after installing it - got Segmentation fault. I dig in it and figured the problem is my environment variable WINEDLLPATH which was set to "." (current directory). The back trace of stack during the crash was similar to this (just the frames 5,6,7,8 were repeating many times - until stack overflow): #0 __pthread_rwlock_unlock (rwlock=0x4032b600) at ../../scheduler/pthread.c:669 #1 0x40220ea7 in gettext () from /lib/i686/libc.so.6 #2 0x40220885 in dcgettext () from /lib/i686/libc.so.6 #3 0x4021f667 in __assert_fail () from /lib/i686/libc.so.6 #4 0x400903d7 in __pthread_rwlock_unlock (rwlock=0x4032b600) at ../../scheduler/pthread.c:671 #5 0x40220ea7 in gettext () from /lib/i686/libc.so.6 #6 0x40220885 in dcgettext () from /lib/i686/libc.so.6 #7 0x4021f667 in __assert_fail () from /lib/i686/libc.so.6 #8 0x400903d7 in __pthread_rwlock_unlock (rwlock=0x4032b600) at ../../scheduler/pthread.c:671 #9 0x40220ea7 in gettext () from /lib/i686/libc.so.6 #10 0x40220885 in dcgettext () from /lib/i686/libc.so.6 #11 0x40278059 in strerror_r () from /lib/i686/libc.so.6 #12 0x40277ea5 in strerror () from /lib/i686/libc.so.6 #13 0x4035513a in dlerror () from /lib/libdl.so.2 #14 0x400f7c00 in wine_dlopen (filename=0x3c001862 "./ntdll.dll.so", flag=0x2, error=0xbffff244 "", errorsize=0x400) at loader.c:452 #15 0x400f745b in dlopen_dll (name=0x400f80cb "ntdll.dll", error=0xbffff244 "", errorsize=0x400, test_only=0x0, exists=0xbffff21c) at loader.c:151 #16 0x400f7b48 in wine_init (argc=0x1, argv=0xbffff694, error=0xbffff244 "", error_size=0x400) at loader.c:424 #17 0x3c000550 in main (argc=0x1, argv=0xbffff694) at main.c:33 #18 0x402137f7 in __libc_start_main () from /lib/i686/libc.so.6 So, I guess wine pthread functions table should be initialized before any (system) library get's chance to throw error, otherwise we have SIGSEGV. I've fixed the error on my side with WINEDLLPATH="/usr/local/lib/wine:.". Anyways I think it's a workaround not a solution... Since I don't know much about initialization, I would leave the real fix for someone more skillful. Best Regards, Juraj

3 6

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

>Thats the problem! >You have your fine dictonary in hand, so you think you know how to speak >english... but when you visit a english speaking country the people >you speak to look like a deer caught in a spot light! So you want a png of my british passport? (BTW it's dictionary, not dictonary, or is that just your american english?) >Shachar don't get mad or pissed.. I had to find someone for my >eniligey.. :) so "eniligey" is american english? Never heard it from Bush, fox tv, NPR... Shachar is right, and at least he uses english on this list, while you >ba bing, bing, bing, BING! speak what for me is a unknown language >As far as slang goes.. I can speak three different versions of slang >NE slang, African American, SE Hill Billy, take your pick. So you want to add slang support to wine? updated is not slang, whatever you may say >Just come for a visit :) I have decss on my site, I don't like the idea of ending up in a US prison (Any american wanting to violate the DMCA go here http://digilander.libero.it/winehqitalia/dvd.html ) Anyway, I have no problems with US english, so I don't see why you should have problems understanding UK english, and I don't see why we shouldn't have grammar in the wine docs.

1 0

adding structures to headers
by Geoff Thorpe 10 Sep '03

10 Sep '03

Hi there, Quick licensing/copyright question before I submit something I regret: when adding missing functions and structure types to wine headers, to what extent can we copy-n-paste structure definitions from the documentation at msdn.microsoft.com web? IANAL. Cheers, Geoff -- Geoff Thorpe geoff(a)geoffthorpe.net http://www.geoffthorpe.net/

3 5

compile time
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

>p.s. >For me (P-IV 1600MHZ) complete build compile takes 25 minutes. I've now >switched to ccache, hoping I can bring it down even lower. And my 1.4GHZ AMD Athlon XP takes 18:45, and some people still think intel can compete with AMD...

2 1

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

> Purely academic, I know, but m-w doesn't know "updated" as an adjective. > To the best of my knowledge, "the list is now updated" is slang. Am I > wrong here? >From the Cambridge Advanced Learner's Dictionary update verb [T] 1 to make something more modern or suitable for use now by adding new information or changing its design: an updated version of the software http://dictionary.cambridge.org/define.asp?key=87314&dict=CALD It definitely isn't slang.

6 7

Re: compile time
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

> Without knowing the rest of the systems (RAM, HD speed, present libs, > compiler used, etc.) it's rather meaningless to compare compile times. 512MB ddr, gcc 3.3.1, all optional wine stuff compiled in, 7200rpms hd.

1 0

something I found that might help GDI hackers
by Jonathan Wilson 10 Sep '03

10 Sep '03

struct GDIHandleBitFields { unsigned long Index:0:10; unsigned long Type:10:5; unsigned long AltType:15:2; unsigned long Stock:17:1; unsigned long Unique:18:8; }; This might help people trying to understand the inner workings of GDI... Its current as of windows XP SP1.

2 1

Re: FAQ: Update the ports section
by Tom 10 Sep '03

10 Sep '03

Francois Gouget wrote: >Changelog: > > >- The following will list the x86 operating systems supported by >+ The following lists the x86 operating systems supported by > > Should be. The following list are the x86 operating systems supported by Tom

7 15

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

I happen to be from the UK, and can tell you that >The following lists the x86 operating systems supported by >the list is now updated >the list is now up to date are all correct.

2 1

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

You must send me some of the stuff you're smoking! "The list are now up to date" doesn't exist in english, you must choose "The lists are now up to date" for a plural "The list is now up to date" for a singular

1 0

Re: [Resend winegcc03] winewrap can handle the default output name
by Dimitrie O. Paun 10 Sep '03

10 Sep '03

On Tue, 9 Sep 2003, Richard Cohen wrote: > Slightly different from last time. > > > Default name that mingw uses is a.exe > > This also stops winewrap from segfaulting when passed no arguments. > > Changelog > Handle default linker output name (a.exe) in winewrap instead of > winegcc I'm still not sure I like this one, as I said, a.out is a gccism, and should be handled in winegcc. winewrap does not have to be command line compatible to the GNU tool (as it currently stands), we can require an output name for it. -- Dimi.

3 4

Re: [DSHOW-08] Implementation of IMemAllocator and IMediaSample (REVISED2)
by Dimitrie O. Paun 10 Sep '03

10 Sep '03

On September 9, 2003 07:37 pm, Robert Shearman wrote: > --- /dev/null Mon Jun 24 01:53:01 2002 > +++ wine/dlls/quartz/list.h Mon Sep 8 00:48:58 2003 The list.h stuff seems to be fairly popular, why not stick a copy in wine/list.h? -- Dimi.

2 1

Re: [winegcc08] Handle -L in a separate array
by Dimitrie O. Paun 10 Sep '03

10 Sep '03

On Tue, 9 Sep 2003, Richard Cohen wrote: > ...rather than adding -L<libpath> to both the DLLs and static libraries > No functional changes. I'm not sure this is correct, as the order of -L and -l may be significant. That is to say, if I do -LdirA -la -LdirB -lb then the system will search for a only in A, not in B, which is not the case if I do: -LdirA -LdirB -la -lb -- Dimi.

2 1

Re: BuildCommDCBAndTimeouts patch
by Jakob Eriksson 10 Sep '03

10 Sep '03

Could you also make test.c into a regression test for inclusion into Wine? That is almost more important than the actual patch to Wine - if we have the conformance test, it ensures changes to Wine in the future does not destroy functionality. regards, Jakob

4 3

Re: Resend: Shlwapi ordinal fixes (Dave Miller)
by Robert Shearman 10 Sep '03

10 Sep '03

On Wednesday 10 September 2003 5:32 am, Dave Miller wrote: > > Remove about a dozen ordinals we have defined which do not seem to be > important. (They vary from one windows version to another) Alexandre, please don't apply. I am doing a big update on the ordinals of Shlwapi and will incorporate these changes into my patch. Rob

1 0

FAQ update
by Tom 10 Sep '03

10 Sep '03

Hi, Thanks for the update.. I got occupied with something and it took me a little longer than I thought. But I have the sync of lostwages to docs faq in my tree. I will now rm -rf it Regards, Tom

6 28

Re: widl: oleidl.h problem
by Jon Griffiths 10 Sep '03

10 Sep '03

Hi, <snip> >Can some of the widl gurus look at this one please? This is a known problem with widl, see http://www.winehq.org/hypermail/wine-devel/2003/03/0359.html. I sent a patch to fix this issue, but it wasn't the right fix and probably won't apply unmodified now. Cheers, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Relocate error
by Fabian Cenedese 10 Sep '03

10 Sep '03

Hi I worked with wine about six months ago. Except some minor errors my app worked quite good in wine. Then I didn't have time anymore. Now I tried again with the newest wine from cvs. But now I can't even start my app anymore. Wine gives me this error: err:virtual:map_image FATAL: Need to relocate module from addr 40000000, but there are no relocation records wine: could not load 'C:\IMD\Bin\Imd.exe' as Win32 binary I looked in the archives and the only messages concerning this error were at least two years old stating that this error has been fixed long ago. I didn't change this link address in my app (VC6), it has been there even before I started with wine at all. But when I change this address to say 0x48000000 then it works. So is there something else on this address? I know six months is a long time and a lot happened this year. But does anybody know if this is a real error? What could have introduced this behaviour as it worked a few months ago? Thanks Fabi

3 5

Word-splitting in the FAQ
by Francois Gouget 10 Sep '03

10 Sep '03

Tom, you submitted a patch that splits many words in two. I assume that's because they're not in the dictionary but I'm not sure it's appropriate. Here are some examples: - Make sure you have all the VB runtime libraries installed. + Make sure you have all the VB run time libraries installed. - (using a DOS filename). + (using a DOS file name). - the UNIX kernel supports the DOS/MS Windows filesystem type). + the UNIX kernel supports the DOS/MS Windows file system type). And some I am absolutely sure are wrong: - ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink> + ftp://metalab.unc.edu/pub/Linux/system/file systems/dosfs/</ulink> - when running an InstallShield 6 installer. + when running an Install shield 6 installer. - program work (there must be a downloadable version or demo for + program work (there must be a download able version or demo for Also I'm not sure why you changed the Lycos URL: - <ulink url="http://search.lycos.com/">Lycos</ulink>. Some of + <ulink url="http://www.compucan.com/Lycos.htm">lycos</ulink> Some of Actually I'm not sure why we have this link to Lycos at all. How does one find Wine using it? So I'm submitting a patch fixing the second type of changes directly to wine-patches. And here is a patch that reverts most of the word splitting. Maybe it goes too far. What do you think? Index: documentation/faq.sgml =================================================================== RCS file: /home/wine/wine/documentation/faq.sgml,v retrieving revision 1.21 diff -u -r1.21 faq.sgml --- documentation/faq.sgml 8 Sep 2003 19:38:45 -0000 1.21 +++ documentation/faq.sgml 9 Sep 2003 19:02:31 -0000 @@ -424,11 +424,11 @@ <ulink url="http://www.winehq.com/download.shtml">the Download page</ulink> for some of these choices), you can make sure that you are getting the latest version by watching the version numbers in the distribution - file name. For instance, the distribution released on August 13, 2003 + filename. For instance, the distribution released on August 13, 2003 was called Wine-20030813.tar.gz. Patch files are also available. If you are current to the previous version, you can download and apply just the current patch file rather than the entire new distribution. - The patch file names follow the same conventions as the monthly + The patch filenames follow the same conventions as the monthly distribution. <ulink url="http://www.winehq.org/site/cvs"> Read-only CVS</ulink> access is also available. </para> @@ -824,8 +838,8 @@ <answer> <para> Yes, but only if the operating system supports mounting those types - of drives. There is a Linux file system driver called dmsdos that + of drives. There is a Linux filesystem driver called dmsdos that will allow read/write access to Doublespaced and Drivespace 1.0 drives. More specifically, it supports mounting DOS 6.0 and 6.2 Doublespaced, DOS 6.22 Drivespaced, and Windows 95 Doublespaced @@ -859,13 +873,13 @@ <answer> <para> Many folks have successfully installed and run programs - in their UNIX file system without having a DOS partition or MS + in their UNIX filesystem without having a DOS partition or MS Windows. However, in many cases you need a directory and file infrastructure that is similar to an existing Windows installation. Some applications' installation programs want to distribute some of the package's files into the /windows and /windows/system directories in order to run, and unless these exist on your UNIX - file system, those programs will not install correctly and probably + filesystem, those programs will not install correctly and probably will not run well, if at all. Most packages will set that up for you as part of the install process. </para> @@ -905,7 +919,7 @@ machine. If you have DOS/MS Windows installed on your system, you can mount that partition at bootup by modifying the file <filename>/etc/fstab</filename> in your UNIX partition (assuming that - the UNIX kernel supports the DOS/MS Windows file system type). + the UNIX kernel supports the DOS/MS Windows filesystem type). </para> <para> If you edit this file by hand, it should contain something similar @@ -935,7 +949,7 @@ DLLs and APIs that are needed by these Windows applications. This means that Wine will not provide replacements for DLLs that are not shipped with Windows or are always shipped with Windows - application (e.g. the Visual Basic run time). This also + application (e.g. the Visual Basic runtime). This also means that implementing an API that no application ever uses is not a priority. Similarly, until there are applications out there that use the Win64 API, it will not be a priority. That being said, @@ -970,13 +984,13 @@ <question id="Will-I-install-on-any-UNIX-file-system"> <para> Will I be able to install MS Windows applications in any flavor of a - UNIX file system? + UNIX filesystem? </para> </question> <answer> <para> - Wine is written to be file system independent, so MS Windows - applications will install and run under virtually any file system + Wine is written to be filesystem independent, so MS Windows + applications will install and run under virtually any filesystem supported by your brand of UNIX. </para> </answer> @@ -1080,12 +1094,12 @@ <para> It should also be available from any other site that mirrors ibiblio.org. For more download locations, see - <ulink url="http://www.compucan.com/Lycos.htm">lycos</ulink> Some of + <ulink url="http://search.lycos.com/">Lycos</ulink>. Some of these ftp sites may archive previous versions of Wine as well as the current one. To determine which is the latest one, look at the - distribution file name, which will take the form + distribution filename, which will take the form Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution - file name with the numbers for year, month and date, respectively. + filename with the numbers for year, month and date, respectively. The latest one is the one to get. </para> <para> @@ -1313,7 +1327,7 @@ </question> <answer> <para> - Make sure you have all the VB run time libraries installed. You may + Make sure you have all the VB runtime libraries installed. You may need to use the native DLL vbrun60.dll. You can get some from dll-files.com. </para> </answer> @@ -1347,7 +1361,7 @@ </question> <answer> <para> - Try to re login into bash. That might fix it. + Try to logout and login again into bash. That might fix it. </para> <para> If it doesn't, then make sure the wine binary is in your @@ -1405,14 +1419,14 @@ Make sure that you specify the exact path when using the powerful <command>rm -fR</command> command. If you are afraid that you might delete something important, or might otherwise delete other files - within your file system, <command>cd</command> into each Wine + within your filesystem, <command>cd</command> into each Wine sub directory singly and delete the files found there manually, one file or directory at a time. </para> <para> Neither the Wine developers and programmers, nor the Wine FAQ author/maintainer, can be held responsible for your deleting any - files in your own file system. + files in your own filesystem. </para> </answer> </qandaentry> @@ -1427,7 +1441,7 @@ <answer> <para> When invoking Wine, you must specify the entire path to the - executable, or by file name only. For example to run Windows' + executable, or by filename only. For example to run Windows' solitaire, type any of the following: </para> <itemizedlist> @@ -1440,19 +1454,19 @@ <listitem> <para> <command>wine c:\\windows\\sol.exe</command> - (using a DOS file name). + (using a DOS filename). </para> </listitem> <listitem> <para> <command>wine /usr/windows/sol.exe</command> - (using a UNIX file name). + (using a UNIX filename). </para> </listitem> <listitem> <para> <command>wine "c:\windows\sol.exe"</command> - (using quoted DOS file name). + (using quoted DOS filename). </para> </listitem> </itemizedlist> -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Stolen from an Internet user: "f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng !"

2 1

Latest CVS doesnt compile
by Sylvain Petreolle 10 Sep '03

10 Sep '03

After updating to the latest CVS via cvs update (the only patch involved was the header dependancies fix), wine doesnt compile.I tried to rerun './configure' but there is no change.What I get is : (make depend runs fine.)[syl@snoop tests]$ LANG=en_US makegcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o testlist.o testlist.cIn file included from testlist.c:6:../../../include/winbase.h:1323: parse error before "va_list"../../../include/winbase.h:1324: parse error before "va_list"make: *** [testlist.o] Error 1[syl@snoop tests]$Running with :RH 9 updated, gcc 3.2.2. Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". --------------------------------- Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Testez le nouveau Yahoo! Mail

8 10

Re: [winegcc06] Delayed import
by Dimitrie O. Paun 10 Sep '03

10 Sep '03

On August 13, 2003 10:08 pm, Richard Cohen wrote: > --- tools.5/winegcc.c 2003-08-14 00:55:07.000000000 +0100 > +++ tools/winegcc.c 2003-08-14 01:21:41.000000000 +0100 > @@ -193,7 +193,8 @@ > } > argv[j] = 0; > break; > - case 'l': > + case 'l': /* import/static library */ > + case 'd': /* delayed import library */ This is not cool -- winegcc is supposed to be command line compatible with mingw-gcc, and -d conflicts with gcc's -d: -dletters Says to make debugging dumps during compilation at times specified by letters. This is used for debugging the compiler. The file names for most of the dumps are made by appending a pass number and a word to the dumpname. dumpname is generated from the name of the output file, if explicitly specified and it is not an executable, otherwise it is the basename of the source file. In both cases any suffix is removed (e.g. foo.00.rtl or foo.01.sibling). Here are the possible letters for use in letters, and their meanings: ..... Having the option in winewrap is OK, there we control the options. If this feature is useful in Windows, gcc must/will support it, right? If they don't already, we better get in touch with them so we end up with the same option name/syntax. -- Dimi.

2 6

Re: for Red Hat packager
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

>The latest Wine >RPMs are compiled without BiDi support the Red Hat rpms may be, but I can assure you that your help to get bidi into the mdk rpms wasn't invane.

7 14

Jump to page:

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