playing with Wine on Cygwin
playing with Wine on Cygwin
I'm currently playing with Wine on Cygwin on Windows 2000 on
VirtualBox. Just to see what happens. Also to see how feasible Wine on
Windows is from here.
I've been updating the http://wiki.winehq.org/CygwinSupport page accordingly.
With the 1.1.11 source tarball, I'm getting a compile error:
internettransport.c:348: error:
`Include_winsock_h_before_stdlib_h_or_use_the_MSVCRT_library'
undeclared (first use in this function)
internettransport.c:348: error: (Each undeclared identifier is
reported only once
internettransport.c:348: error: for each function it appears in.)
internettransport.c:348: error: parse error before "infd"
internettransport.c:379: warning: implicit declaration of function
`Include_winsock_h_before_stdlib_h_or_use_the_MSVCRT_library'
internettransport.c:379: error: `infd' undeclared (first use in this function)
make[2]: *** [internettransport.o] Error 1
make[2]: Leaving directory `/cygdrive/c/wine-1.1.11/dlls/inetcomm'
make[1]: *** [inetcomm] Error 2
make[1]: Leaving directory `/cygdrive/c/wine-1.1.11/dlls'
make: *** [dlls] Error 2
Looks like the sort of thing that happens when configure thinks you
have something installed you don't.
I realise this is on VirtualBox, so all results are to be taken with a
large grain of salt. But is anyone else seeing this with Wine on
Cygwin?
Now to give Wine on mingw a try ...
- d.
VirtualBox. Just to see what happens. Also to see how feasible Wine on
Windows is from here.
I've been updating the http://wiki.winehq.org/CygwinSupport page accordingly.
With the 1.1.11 source tarball, I'm getting a compile error:
internettransport.c:348: error:
`Include_winsock_h_before_stdlib_h_or_use_the_MSVCRT_library'
undeclared (first use in this function)
internettransport.c:348: error: (Each undeclared identifier is
reported only once
internettransport.c:348: error: for each function it appears in.)
internettransport.c:348: error: parse error before "infd"
internettransport.c:379: warning: implicit declaration of function
`Include_winsock_h_before_stdlib_h_or_use_the_MSVCRT_library'
internettransport.c:379: error: `infd' undeclared (first use in this function)
make[2]: *** [internettransport.o] Error 1
make[2]: Leaving directory `/cygdrive/c/wine-1.1.11/dlls/inetcomm'
make[1]: *** [inetcomm] Error 2
make[1]: Leaving directory `/cygdrive/c/wine-1.1.11/dlls'
make: *** [dlls] Error 2
Looks like the sort of thing that happens when configure thinks you
have something installed you don't.
I realise this is on VirtualBox, so all results are to be taken with a
large grain of salt. But is anyone else seeing this with Wine on
Cygwin?
Now to give Wine on mingw a try ...
- d.
Re: playing with Wine on Cygwin
There's little reason to suspect virtualization for a compile time error.David Gerard wrote:I'm currently playing with Wine on Cygwin on Windows 2000 on
VirtualBox. Just to see what happens. Also to see how feasible Wine on
Windows is from here.
I've been updating the http://wiki.winehq.org/CygwinSupport page accordingly.
With the 1.1.11 source tarball, I'm getting a compile error:
internettransport.c:348: error:
`Include_winsock_h_before_stdlib_h_or_use_the_MSVCRT_library'
undeclared (first use in this function)
internettransport.c:348: error: (Each undeclared identifier is
reported only once
internettransport.c:348: error: for each function it appears in.)
internettransport.c:348: error: parse error before "infd"
internettransport.c:379: warning: implicit declaration of function
`Include_winsock_h_before_stdlib_h_or_use_the_MSVCRT_library'
internettransport.c:379: error: `infd' undeclared (first use in this function)
make[2]: *** [internettransport.o] Error 1
make[2]: Leaving directory `/cygdrive/c/wine-1.1.11/dlls/inetcomm'
make[1]: *** [inetcomm] Error 2
make[1]: Leaving directory `/cygdrive/c/wine-1.1.11/dlls'
make: *** [dlls] Error 2
Looks like the sort of thing that happens when configure thinks you
have something installed you don't.
I realise this is on VirtualBox, so all results are to be taken with a
large grain of salt. But is anyone else seeing this with Wine on
Cygwin?
Now to give Wine on mingw a try ...
- d.
Coincidentally, this bug also occurs on OpenBSD http://bugs.winehq.org/show_bug.cgi?id=16660
You could try the suggested fix attached to the bug report.
playing with Wine on Cygwin
2008/12/29 jeffz <[email protected]>:
by ./configure on the basis of reading the operating system's entrails
...
On OpenBSD a lot of weird stuff is definitely due to virtualisation -
OpenBSD is a blue pill showing every glitch in the Matrix.
Windows (and hence Cygwin) have the red pill especially built for
them, so are much easier to keep fooled, it's true
- d.
I suspect *everything*, particularly when the makefile is constructedThere's little reason to suspect virtualization for a compile time error.
by ./configure on the basis of reading the operating system's entrails
...
On OpenBSD a lot of weird stuff is definitely due to virtualisation -
OpenBSD is a blue pill showing every glitch in the Matrix.
Windows (and hence Cygwin) have the red pill especially built for
them, so are much easier to keep fooled, it's true

Just trying on XP in VirtualBox as well.Coincidentally, this bug also occurs on OpenBSD http://bugs.winehq.org/show_bug.cgi?id=16660
You could try the suggested fix attached to the bug report.
- d.
Re: playing with Wine on Cygwin
No really. Just try the patches.David Gerard wrote:2008/12/29 jeffz <[email protected]>:
I suspect *everything*, particularly when the makefile is constructedThere's little reason to suspect virtualization for a compile time error.
by ./configure on the basis of reading the operating system's entrails
...
On OpenBSD a lot of weird stuff is definitely due to virtualisation -
OpenBSD is a blue pill showing every glitch in the Matrix.
Windows (and hence Cygwin) have the red pill especially built for
them, so are much easier to keep fooled, it's true
Just trying on XP in VirtualBox as well.Coincidentally, this bug also occurs on OpenBSD http://bugs.winehq.org/show_bug.cgi?id=16660
You could try the suggested fix attached to the bug report.
- d.
playing with Wine on Cygwin
2008/12/29 jeffz <[email protected]>:
out differently!
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
-D_REENTRANT -Wall -pipe -fno-strict-aliasing
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2
-o internettransport.o internettransport.c
In file included from internettransport.c:31:
../../include/ws2tcpip.h:238: error: parse error before "socklen_t"
../../include/ws2tcpip.h:240: error: parse error before "socklen_t"
make[2]: *** [internettransport.o] Error 1
make[2]: Leaving directory `/home/fun/wine-1.1.11/dlls/inetcomm'
make[1]: *** [inetcomm] Error 2
make[1]: Leaving directory `/home/fun/wine-1.1.11/dlls'
make: *** [dlls] Error 2
o_0
- d.
I applied Austin's patch for OpenBSD from bug 16660. And ... it bombedNo really. Just try the patches.
out differently!
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
-D_REENTRANT -Wall -pipe -fno-strict-aliasing
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2
-o internettransport.o internettransport.c
In file included from internettransport.c:31:
../../include/ws2tcpip.h:238: error: parse error before "socklen_t"
../../include/ws2tcpip.h:240: error: parse error before "socklen_t"
make[2]: *** [internettransport.o] Error 1
make[2]: Leaving directory `/home/fun/wine-1.1.11/dlls/inetcomm'
make[1]: *** [inetcomm] Error 2
make[1]: Leaving directory `/home/fun/wine-1.1.11/dlls'
make: *** [dlls] Error 2
o_0
- d.
playing with Wine on Cygwin
On Mon, Dec 29, 2008 at 5:16 PM, David Gerard <[email protected]> wrote:
--
-Austin
You need to use the second patch, the first one is wrong.2008/12/29 jeffz <[email protected]>:
I applied Austin's patch for OpenBSD from bug 16660. And ... it bombedNo really. Just try the patches.
out differently!
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
-D_REENTRANT -Wall -pipe -fno-strict-aliasing
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2
-o internettransport.o internettransport.c
In file included from internettransport.c:31:
../../include/ws2tcpip.h:238: error: parse error before "socklen_t"
../../include/ws2tcpip.h:240: error: parse error before "socklen_t"
make[2]: *** [internettransport.o] Error 1
make[2]: Leaving directory `/home/fun/wine-1.1.11/dlls/inetcomm'
make[1]: *** [inetcomm] Error 2
make[1]: Leaving directory `/home/fun/wine-1.1.11/dlls'
make: *** [dlls] Error 2
o_0
- d.
--
-Austin
playing with Wine on Cygwin
to list as well!
---------- Forwarded message ----------
From: David Gerard <[email protected]>
Date: 2008/12/30
Subject: Re: [Wine] playing with Wine on Cygwin
To: Austin English <[email protected]>
2008/12/29 Austin English <[email protected]>:
the last patch in the bug.
Obviously it's not the thing for Cygwin
I can't be the only person in the world trying to get Wine to compile
under Cygwin ...
- d.
---------- Forwarded message ----------
From: David Gerard <[email protected]>
Date: 2008/12/30
Subject: Re: [Wine] playing with Wine on Cygwin
To: Austin English <[email protected]>
2008/12/29 Austin English <[email protected]>:
On Mon, Dec 29, 2008 at 5:16 PM, David Gerard <[email protected]> wrote:
I applied Austin's patch for OpenBSD from bug 16660. And ... it bombed
out differently!
In file included from internettransport.c:31:
../../include/ws2tcpip.h:238: error: parse error before "socklen_t"
../../include/ws2tcpip.h:240: error: parse error before "socklen_t"
make[2]: *** [internettransport.o] Error 1
I applied http://bugs.winehq.org/attachment.cgi?id=18288 , which isYou need to use the second patch, the first one is wrong.
the last patch in the bug.
Obviously it's not the thing for Cygwin

I can't be the only person in the world trying to get Wine to compile
under Cygwin ...
- d.
I think it's a cool idea. At the very least, building and runningoiaohm wrote:Sorry David Gerard you could be the only person trying to get wine to work under Cygwin.
the wine unit test suite under Cygwin could be useful.
And various individual Wine DLLs could be useful on Windows,
especially the direct x 10 implementation.
So it's not at all crazy...
playing with Wine on Cygwin
2008/12/30 DanKegel <[email protected]>:
still supported by Wine. So Wine for Windows would supply useful
backward compatibility for users. Wine is already a better Windows
than Vista in a lot of cases ...
Wiki page: http://wiki.winehq.org/WineOnWindows
Note I'm also trying Wine on MinGW and Wine on Interix %-D
I note there's also a page on how to cross-compile Wine PE DLLs on
Unix: http://wiki.winehq.org/CompilingDLLsUsingMingw The Wine download
page includes a 2.5-year-old zip file of Windows DLLs from Wine
0.9.14, apparently built using this.
to beat this into working ;-p
- d.
oiaohm wrote:
Sorry David Gerard you could be the only person trying to get wine to work under Cygwin.
Newer versions of Windows fail to support old applications that areI think it's a cool idea. At the very least, building and running
the wine unit test suite under Cygwin could be useful.
And various individual Wine DLLs could be useful on Windows,
especially the direct x 10 implementation.
still supported by Wine. So Wine for Windows would supply useful
backward compatibility for users. Wine is already a better Windows
than Vista in a lot of cases ...
Wiki page: http://wiki.winehq.org/WineOnWindows
Note I'm also trying Wine on MinGW and Wine on Interix %-D
I note there's also a page on how to cross-compile Wine PE DLLs on
Unix: http://wiki.winehq.org/CompilingDLLsUsingMingw The Wine download
page includes a 2.5-year-old zip file of Windows DLLs from Wine
0.9.14, apparently built using this.
You wouldn't be saying that if you were trying the things I'm tryingSo it's not at all crazy...
to beat this into working ;-p
- d.
I did not tell you the biggest issue David. Why some have going the visualization path.
Wine program loader will not work with windows.
Direct x implementation should work on windows with some tweaking all ready. Wined3d is used with a virtualisation solution with windows to send direct X to opengl so it can be passed threw.
http://winehq.org/status/porting Kinda out of date and needs updating as well. Yes it has not been updated for like 2.5 years.
For testing wine test suite should already build under mingw.
Correction: mingw running as a cross complier on Linux. Your failure with mingw looks to be a mingw windows gnumake problem. Please try the same command under Linux/BSD/OS X ie anything bar windows.
Cygwin virtual posix can cause headaches past what you can dream. To get wine working on windows well will require lots of work.
Wine program loader will not work with windows.
Direct x implementation should work on windows with some tweaking all ready. Wined3d is used with a virtualisation solution with windows to send direct X to opengl so it can be passed threw.
http://winehq.org/status/porting Kinda out of date and needs updating as well. Yes it has not been updated for like 2.5 years.
For testing wine test suite should already build under mingw.
Correction: mingw running as a cross complier on Linux. Your failure with mingw looks to be a mingw windows gnumake problem. Please try the same command under Linux/BSD/OS X ie anything bar windows.
Cygwin virtual posix can cause headaches past what you can dream. To get wine working on windows well will require lots of work.