Wine Traffic #169 For 5/09/2003

By Brian Vincent

Table Of Contents


This is the 169th release of the Wine's kernel cousin publication. It's main goal is to inform you of what's going on around Wine (the Un*x windows emulator).

Mailing List Stats For This Week

We looked at 214 posts in 623K.

There were 67 different contributors. 34 posted more than once. 30 posted last week too.

The top posters of the week were:

1. News: Wine-20030508, Lycoris GamePak

5/03/2003�-�5/09/2003 (3 posts) Archive Link: "News"

Topics: News

People: Alexandre Julliard,�LinuxPR

Another Wine drop, you know the drill. Alexandre noted the following changes with Wine-20030508:

WHAT'S NEW with Wine-20030508: (see ChangeLog ( for details)

Lycoris announced their GamePak distribution:

Breaking down one of the barrriers to widespread adoption of Desktop/LX as a mainstream operating system, Lycoris and TransGaming unleash the GamePak. A powerful package of five (5) native Desktop/LX games, the GamePak comes bundled with access to one free month of WineX which allows Desktop/LX users to play over 250 Windows games on their Desktop/LX PC. At the low price of $34.95, the GamePak gives Desktop/LX users value, action and compatibility in a single, simple to install package. The GamePak is immediately available from The Lycoris Store ( .

Looks like an easy way to get WineX installed and configured. TransGaming has no announcement on their web site.

eWeek has a positive albeit lame review (,3959,1054585,00.asp) of CrossOver Office 2.0.

2. Compiling Mozilla With Wine Tools

5/08/2003 (3 posts) Archive Link: "Win32 Mozilla 1.4b+ GCC (MingW)?"

Topics: Winelib

People: Brian Vincent,�Dimitrie Paun

I asked the following on Thursday:

Anyone see the release info for Mozilla 1.4 Beta? It says:

Here's the specific build instructions for Windows:

It notes:

Mozilla used to be listed on the fun projects ( page. It was removed last month because Mozilla could only be compiled with MSVC. Yes, we all know Mozilla has native versions for zillions of platforms, but compiling the Win32 version with Winelib would stress the toolchain and uncover things that need to be fixed. Dimi wrote back with a list of known issues that still need to be resolved:

Yes, the 1.4 release will build on MinGW/Cygwin. With a bit of luck, we'll have a binutils release in a week or two, so we can remove some of the ugly, ugly hacks that were put it to work around windres problems that have since been fixed.

Some of this fixes will help a little with an eventual Wine port, but this one will be tough. We still need a lot of work on winegcc/winewrap to get this to work, let alone possible enhancements to gcc for -mthread support.

We are currently failing on simple things with winegcc. For example:

  1. It seems that MinGW's gcc support both main() and WinMain() as entry points irregardless of the -mwindows flags. We don't. This results in configure tests. For example, we can't currently build wxWindows using their configure script because configure invokes winegcc with the -mwindows flag even though it builds simple console apps that have a simple main() function. This obviously works under MinGW. I have little knowledge about linking issues like this, how can we support that in wingcc/winewrap?
  2. We need to add support for the -shared flag to winegcc. This is a big task, and we haven't even started to look at these issues.
  3. I haven't tried, but I don't think we do the right thing when we're invoked with the -mthread flag. Alexandre, what extensions (if any) we need to gcc to be able to support Windows programs that use the -mthread flag?

Alexandre replied and felt the first issue shouldn't be hard to support. As far as the -mthread ( option goes, he thought maybe it could be ignored.

3. Solaris x86 Status

5/05/2003�-�5/07/2003 (3 posts) Archive Link: "solaris x86 development?"

Topics: Ports

People: Peter Lees,�Robert Lunnon

In the you're-the-one-who-uses-that-OS category, Peter Lees wanted to know the status of Wine on Solaris x86:

what is the status of WINE development for solaris x86?

i'm running into some fairly fundamental build bugs & would like to know if anyone has got it working.

Robert Lunnon reported working on it recently and gave some pointers:

Wine can be made to work on Solaris X86 with a few patches. To compile you will need the patch kit and a copy of gcc that uses gas rather than AS. the Solaris assembler expect intel assembly while gas expects AT&T.

I sent diffs last week but I don't know how long it will take for them to reach cvs or if they will ever get there.

Alexandre reported that some of the patches were applied but other parts needed to be cleaned up before he would commit them.

4. Broken flex

5/01/2003 (5 posts) Archive Link: "Cant compile wine.. CVS or release."

Topics: Build Process

People: mdew,�Rein Klazes

I meant to put this one in last week, but it slipped through the cracks. Someone had a problem compiling Wine out of CVS and posted some info on their tools and the error generated:

A few minutes later Rein Klazes responded with the solution, " Flex 2.5.31 bug. Downgrade to 2.5.3a, "make clean" in the tools directory and you are back."

5. Building a Windows API Database

5/02/2003�-�5/05/2003 (14 posts) Archive Link: "Volunteers needed - windows API db script ready"

Topics: Utilities

People: Dave Miller

Back in issue #156 ('d)) we discussed building a table or database of how Windows DLL's are interrelated. By running a perl utility you can scan a Windows installation to locate DLL's and dump API imports and exports using winedump. Dave Miller wrote in to announce more work he'd done on this tool:

The script which dumps dll imports and exports now seems to parse everything correctly and organize it nicely in a text file. We need the script run against various windows versions. The output can be sent directly to me, but please verify I do not already have the data for that particular version of windows. I don't need 10 copies of win2k SP3 for example. :)

The script is available at Please make sure you get There is another script, which will ONLY parse the wine spec files.

To run this you will need winedump, perl, and access to your windows directory from within Linux. The cleaner the windows install the better. We don't want to clutter the database with info from dlls not provided with windows. Usage is as follows:

This will save the imports and exports and also create winver.ref, where winver is specified on the command line with -o. The .ref file is the one which will contain all the info we need. This will be a large file, so I recommend compressing with gzip if you are going to email it to me. It may be large enough to bounce back into your mailbox if you do not. :)

The resulting filename was discussed and everyone decided the output should be named something like <name>-<version>-<service-pack>.ref, such as wine98-4.00.123-SP6a.ref

6. WinZip Registry Patch

5/04/2003 (3 posts) Archive Link: "WinZip registry patch"

Topics: Fixes

People: Nick Brereton,�Sylvain Petreolle

Nick Brereton announced a small patch to help Winzip work better:

Attachment ( is a windows registry file.

Integration of this file directs WinZip to not use the Rich Edit control when displaying comments in Zip files by changing a flag that WinZip read from the registry. This means that it will work with all zip files rather than crashing out on zip files with comments.

Should I post this anywhere else? eg the wine-patch list? Any comments would be appreciated.

Dimi liked the idea and suggested submitting a patch against the default Wine registry. Sylvain Petreolle felt more should be done, " Im not against this patch, but this is hiding a problem and not resolving it. We should make sure a bug is open about this or add comments into richedit/winedefault.reg."

Sharon And Joy

Kernel Traffic is grateful to be developed on a computer donated by Professor Greg Benson and Professor Allan Cruse in the Department of Computer Science at the University of San Francisco. This is the same department that invented FlashMob Computing. Kernel Traffic is hosted by the generous folks at All pages on this site are copyright their original authors, and distributed under the terms of the GNU General Public License version 2.0.