I have much trouble compiling Wine 0.9.53 and I just don't know what to do. My system is Ubuntu Intrepid Ibex (32-bit) and I have build essential and build-dep wine installed. Also I've used install-wine-deps.sh from official Wine Wiki just to be sure that all needed dependencies are installed.
First I've tried by downloading source code but whenever I try to compile it I get this error:
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o signal_i386.o signal_i386.c
signal_i386.c: In function ‘merge_vm86_pending_flags’:
signal_i386.c:502: error: ‘VIF_MASK’ undeclared (first use in this function)
signal_i386.c:502: error: (Each undeclared identifier is reported only once
signal_i386.c:502: error: for each function it appears in.)
signal_i386.c:513: error: ‘VIP_MASK’ undeclared (first use in this function)
signal_i386.c: In function ‘raise_vm86_sti_exception’:
signal_i386.c:1086: error: ‘VIP_MASK’ undeclared (first use in this function)
signal_i386.c: In function ‘__wine_enter_vm86’:
signal_i386.c:1486: error: ‘VIF_MASK’ undeclared (first use in this function)
signal_i386.c:1487: error: ‘VIP_MASK’ undeclared (first use in this function)
make[2]: *** [signal_i386.o] Error 1
make[2]: Leaving directory `/home/myself/Desktop/wine-0.9.53/dlls/ntdll'
make[1]: *** [ntdll] Error 2
make[1]: Leaving directory `/home/myself/Desktop/wine-0.9.53/dlls'
make: *** [dlls] Error 2
I don't get this error when I'm compiling 1.x versions of Wine - I've tried with 1.01 and 1.1.23 just to be sure; But whenever I try to compile 0.9.x versions I'm stuck with this error (I've tried 0.9.52 and 0.9.54 also).
Today I've tried to compile from git and same error appears - Can someone help me please?
I don't know what to think - kernel headers are installed by default when you install Ubuntu (if I'm not mistaken); Just to be sure I've ran sudo apt-get install linux-headers-$(uname -r) and it prompts me that they are installed:
linux-headers-2.6.27-14-generic is already the newest version.
After reading your post I choose to install some linux-headers packages from repos but that didn't solve the problem...
Today I've tried to compile Wine 0.9.53 on Hardy (in VirtualBox) and it compiles succesfully. Something's not right here and it looks like it has something with kernel headers that are shipped with Intrepid like you suggested. I'll try to compile Wine 0.9.53 later this day on Jaunty but I expect to see same error.
I don't know what to think - kernel headers are installed by default when you install Ubuntu (if I'm not mistaken); Just to be sure I've ran sudo apt-get install linux-headers-$(uname -r) and it prompts me that they are installed:
linux-headers-2.6.27-14-generic is already the newest version.
After reading your post I choose to install some linux-headers packages from repos but that didn't solve the problem...
Today I've tried to compile Wine 0.9.53 on Hardy (in VirtualBox) and it compiles succesfully. Something's not right here and it looks like it has something with kernel headers that are shipped with Intrepid like you suggested. I'll try to compile Wine 0.9.53 later this day on Jaunty but I expect to see same error.
Alternatively, do you have any other idea I should try out? Thanks in advance.
The problem is compiling old code like that often breaks on newer
systems. You could use a reverse regression test to find the patch
that fixes it and compile the old code... http://wiki.winehq.org/ReverseRegressionTesting
The problem is compiling old code like that often breaks on newer
systems. You could use a reverse regression test to find the patch
that fixes it and compile the old code... http://wiki.winehq.org/ReverseRegressionTesting
--
-Austin
You're right I've already tried "the easier way" by substituting those functions
("merge_vm86_pending_flags", "raise_vm86_sti_exception", "__wine_enter_vm86") with "good ones" from Wine 1.01 but without success; I've tried to change them manually but I'm no programmer so I failed again
The reason I choose that path is because this is the first time I'm using Git and there are some things I still don't understand; Now I will try "the right way" - Thanks all of you for your help!
(I guess I'll be back quickly - I suspect I'll get into trouble with Reverse Regression Testing)
The problem is compiling old code like that often breaks on newer
systems. You could use a reverse regression test to find the patch
that fixes it and compile the old code... http://wiki.winehq.org/ReverseRegressionTesting
--
-Austin
You're right I've already tried "the easier way" by substituting those
functions
("merge_vm86_pending_flags", "raise_vm86_sti_exception",
"__wine_enter_vm86") with "good ones" from Wine 1.01 but without success;
I've tried to change them manually but I'm no programmer so I failed again
The reason I choose that path is because this is the first time I'm using
Git and there are some things I still don't understand; Now I will try "the
right way" - Thanks all of you for your help!
(I guess I'll be back quickly - I suspect I'll get into trouble with
Reverse Regression Testing)
You know... you could just try packages from older Ubuntu or Debian – it
should work just fine – I 'm using many wine version, from many different
distros – mostly Ubuntu, and I can safely say – they work great, no
recompilation required – tested with Debian 5.0.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>
It takes long time to do Reverse Regression Testing maybe because I'm still not that familiar with Git (I'll do it anyway because I want to learn how to do it).
But now I have another problem and I hope you'll help me with this:
I set "/home/myself/winebuilds/wine-0.9.53" for install folder and use "checkinstall" to create deb package but after the installation Wine won't run no matter what I do ?!
If I run winecfg or winever from /home/myself/winebuilds/wine-0.9.53/bin it says command not found and when I choose to install Wine from repos it overwrites my version of Wine.
All I want is to have "stable" version of Wine installed in its default location and versions of Wine compiled by me installed in a different location - How can I achieve that and what am I doing wrong here?
It takes long time to do Reverse Regression Testing maybe because I'm still
not that familiar with Git (I'll do it anyway because I want to learn how to
do it).
But now I have another problem and I hope you'll help me with this:
I set "/home/myself/winebuilds/wine-0.9.53" for install folder and use
"checkinstall" to create deb package but after the installation Wine won't
run no matter what I do ?!
If I run winecfg or winever from /home/myself/winebuilds/wine-0.9.53/bin it
says command not found and when I choose to install Wine from repos it
overwrites my version of Wine.
All I want is to have "stable" version of Wine installed in its default
location and versions of Wine compiled by me installed in a different
location - How can I achieve that and what am I doing wrong here?
That doesn't work - still get "command not found"; Maybe I made a mistake
by choosing that destination folder - Maybe it's better idea to use:
./configure --prefix=/opt/wine
or
./configure --prefix=/usr/local/wine
as described in "Advanced Wine Installation"
I'll try that later today - thanks anyway though...
Hmm weird... I suggest you simply check where binary is... simply open .deb
package in some archive manager, then open data.tar.gz (inside .deb package)
and check where it is being unpacked or even better – extract wine from
data.tar.gz yourself (I do that myself) and then run from extraction
location.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>
