Regression: Wine won't compile with latest cvs shlwapi

[Tony Lambregts]

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

[Dimitrie O. Paun]

On April 2, 2002 05:34 pm, Tony Lambregts wrote:
> This is the patch that was commited at 19:33:39 CST
> http://www.winehq.com/hypermail/wine-cvs/2002/03/0072.html

Hey!!! wine-cvs archive is down! ;(

[Jeremy Newman]

No it's not. You just happened to catch it in the 5 seconds it took me
to change a symlink. Good timing on your part I would say. :-D

On Tue, 2002-04-02 at 16:57, Dimitrie O. Paun wrote:
> On April 2, 2002 05:34 pm, Tony Lambregts wrote:
> > This is the patch that was commited at 19:33:39 CST
> > http://www.winehq.com/hypermail/wine-cvs/2002/03/0072.html
>
> Hey!!! wine-cvs archive is down! ;(
>
> -- 
> Dimi.

[Ulrich Weigand]

Tony Lambregts wrote:
> gcc: Internal compiler error: program cc1 got fatal signal 11
> 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.

[snip]
> What do I need to do now?

If you can get cc1 to die with SIGSEGV reproducibly in same place,
then you have most probably found a compiler bug.

The first question is of course, which version of gcc are you
using?  Did you build it yourself or is it the one that came
with your distro (which one?)?  What is the output of
  gcc -v
  rpm -qf `which gcc`

Bye,
Ulrich

[Tony Lambregts]

Ulrich Weigand wrote:
> Tony Lambregts wrote:
> > gcc: Internal compiler error: program cc1 got fatal signal 11
> > 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.
>
> [snip]
> > What do I need to do now?
>
> If you can get cc1 to die with SIGSEGV reproducibly in same place,
> then you have most probably found a compiler bug.
>
> The first question is of course, which version of gcc are you
> using?  Did you build it yourself or is it the one that came
> with your distro (which one?)?  What is the output of
>  gcc -v
>  rpm -qf `which gcc`
>
> Bye,
> Ulrich

Redhat 6.0

gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)

Tony Lambregts

[Alexandre Julliard]

Tony Lambregts  writes:
> 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

That's most likely the usual gcc bug with local WINAPI function
pointers. I've merged a patch to shlwapi that should work around
this.

[Tony Lambregts]

Alexandre Julliard wrote:
> Tony Lambregts  writes:
> > 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
>
> That's most likely the usual gcc bug with local WINAPI function
> pointers. I've merged a patch to shlwapi that should work around
> this.

Your right my version of gcc is buggy . Thankyou for the patch wine 
compiles fine now.

Tony Lambregts

[Ulrich Weigand]

Alexandre Julliard wrote:
> That's most likely the usual gcc bug with local WINAPI function
> pointers.

Doh, I'd completely forgotten that one :-/

Thanks,
Ulrich