On Wed, 13 Dec 2000, James Abbatiello wrote:
I had two problems on #WineHQ of gcc 2.91.66 crashing on .spec.c files
Does anybody know what might be wrong for these buggy compilers ?
Yes. Upgrade to a version of the compiler that is (basically) less than
over two years old.
On Wed, Dec 13, 2000 at 09:20:39PM -0800, Alexandre Julliard wrote:
Andreas Mohr [EMAIL PROTECTED] writes:
somebody did something evil to our .spec.c files recently, it seems.
I had two problems on #WineHQ of gcc 2.91.66 crashing on .spec.c files
(winaspi32.spec.c,
Hi all,
somebody did something evil to our .spec.c files recently, it seems.
I had two problems on #WineHQ of gcc 2.91.66 crashing on .spec.c files
(winaspi32.spec.c, winspool.drv.spec.c)
In the second case it was 20001202, BTW.
Does anybody know what might be wrong for these buggy compilers ?
Andreas Mohr wrote:
Hi all,
somebody did something evil to our .spec.c files recently, it seems.
I had two problems on #WineHQ of gcc 2.91.66 crashing on .spec.c files
(winaspi32.spec.c, winspool.drv.spec.c)
In the second case it was 20001202, BTW.
Does anybody know what might be
Andreas Mohr [EMAIL PROTECTED] writes:
somebody did something evil to our .spec.c files recently, it seems.
I had two problems on #WineHQ of gcc 2.91.66 crashing on .spec.c files
(winaspi32.spec.c, winspool.drv.spec.c)
In the second case it was 20001202, BTW.
Does anybody know what
