had trouble compiling today

[Susan Cragin-2]

It may be me. I've upgraded to Lucid Lynx.
My compile failed.

gcc -c -I. -I. -I../../include -I../../include  -D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wtype-limits -Wpointer-arith  -g -O2  -o int21.o int21.c
int21.c: In function ‘INT21_GetDriveAllocInfo’:
int21.c:3556: internal compiler error: in int_cst_value, at tree.c:8305
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make[2]: *** [int21.o] Error 1
make[2]: Leaving directory `/home/susan/wine/dlls/winedos'
make[1]: *** [winedos] Error 2
make[1]: Leaving directory `/home/susan/wine/dlls'
make: *** [dlls] Error 2
susan@ubuntu:~/wine$

[Reece Dunn-2]

2009/11/5 Susan Cragin <susancragin@...>:
> It may be me. I've upgraded to Lucid Lynx.
> My compile failed.
>
> gcc -c -I. -I. -I../../include -I../../include  -D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wtype-limits -Wpointer-arith  -g -O2  -o int21.o int21.c
> int21.c: In function ‘INT21_GetDriveAllocInfo’:

> int21.c:3556: internal compiler error: in int_cst_value, at tree.c:8305
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.

Looks like a gcc compiler bug, so you will need to report it there
and/or to the Ubuntu bug tracker.

Out of interest:
  a/  did this work when you were running karmic?
  b/  what does "gcc --version" produce?
  c/  is this an incremental build from a previous build on karmic?
  d/  what happens if you clean out all build files (running "git
clean -fxd" in ~/wine will do this if ~/wine is a clone of the wine
git repository) and do a build -- does that resolve the issue?

NOTE: You should still report this to gcc/Ubuntu.

- Reece

[Susan Cragin-2]

>Looks like a gcc compiler bug, so you will need to report it there
>and/or to the Ubuntu bug tracker.
>
>Out of interest:
>  a/  did this work when you were running karmic?
Yes. Worked always with Karmic. Worked yesterday with Lucid. But downloaded new gcc today, and new git. So it's one or the other.

>  b/  what does "gcc --version" produce?
gcc (Ubuntu 4.4.2-1ubuntu3) 4.4.2

>  c/  is this an incremental build from a previous build on karmic?
Yes. (In fact, it's pre-alpha lucid.) It may well be that there is a new gcc that depends on a new something else that hasn't been released yet.

>  d/  what happens if you clean out all build files (running "git
>clean -fxd" in ~/wine will do this if ~/wine is a clone of the wine
>git repository) and do a build -- does that resolve the issue?
Oh, that's a nice command. I'll have to remember that one.
Nothing happens.

>NOTE: You should still report this to gcc/Ubuntu.
Noted. Reported. Bug filed.

>- Reece

As I was getting ready to send this I noted another gcc floating by aptitude, so I gave that one a spin. No luck. The problem persists, but I bet the developers know about it.