Regression: Wine won't compile with latest cvs shlwapi
Tony Lambregts
tony_lambregts at telusplanet.net
Tue Apr 2 16:34:05 CST 2002
I can't get recent cvs versions to compile. After running cvs update -PAd and
./tools/installwine I get these messages
gcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [ordinal.o] Error 1
make[2]: Leaving directory `/usr/local/src/wine/dlls/shlwapi'
make[1]: *** [shlwapi/shlwapi.dll.so] Error 2
make[1]: Leaving directory `/usr/local/src/wine/dlls'
make: *** [dlls] Error 2
Compilation failed, aborting install.
At first I thought it might be something wrong with my system so I backed out
cvs to March 1st 2002 and everything worked.
I talked to Lawson on wine-users and he says I should look at
http://www.bitwizard.nl/sig11/ (This link is about mostly about compiling a
kernal but it applies to compiling wine as well)
I have looked at it and tried most of the things suggested in it. I still stop
in exactly the same place.
Things i have tried
I ran dd if=/dev/hda7 of=/dev/null bs=1024k count=96 and re-ran make
I lowered my clock speed from 200mhz to 133mhz
I have 4 72 pin simms, 2-16's and 2-32's I have tried compiling with each set
individualy
I have increased my swap space
None of this helped.
In the mean time I have done some regression testing using CVS
cvs update -D "2002-03-19 19:31:04 CST"
./configure
make depend && make
compiles with no errors
cvs update -D "2002-03-19 19:33:40 CST"
./configure
make depend && make
results with this
gcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [ordinal.o] Error 1
make[2]: Leaving directory `/usr/local/src/wine/dlls/shlwapi'
make[1]: *** [shlwapi/shlwapi.dll.so] Error 2
make[1]: Leaving directory `/usr/local/src/wine/dlls'
make: *** [dlls] Error 2
Compilation failed, aborting install.
This is the patch that was commited at 19:33:39 CST
http://www.winehq.com/hypermail/wine-cvs/2002/03/0072.html
Now I'm not the shapest knife in the drawer in fact I can be quite dull
but this is a very strong indication that this patch is the one that is
causing the problem.
What do I need to do now?
Tony Lambregts
More information about the wine-devel
mailing list