Build fails for current CVS update

[Sami Aario]

Hi,

Building with tools/wineinstall fails with the latest CVS update on my
system with the following:

gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include -D__WINE
SRC__  -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-stri
ct-aliasing -gstabs+ -Wpointer-arith  -g -O2 -o ddraw.spec.o ddraw.spec.c
{standard input}: Assembler messages:
{standard input}:654: Error: no such instruction: `yes "ddraw.dll"'
{standard input}:655: Error: no such instruction: `yes
"DDHAL32_VidMemAlloc"'
{standard input}:656: Error: no such instruction: `yes "DDHAL32_VidMemFree"'
{standard input}:657: Error: no such instruction: `yes "DDInternalLock"'

and so on, lots more of the same. Anyone else getting these?

[Sami Aario]

----- Original Message ----- 
From: "Sami Aario" 
To: 
Sent: Saturday, January 10, 2004 1:55 AM
Subject: Build fails for current CVS update
> Hi,
>
> Building with tools/wineinstall fails with the latest CVS update on my
> system with the following:

gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include -D__WINE
>

SRC__  -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-stri
> ct-aliasing -gstabs+ -Wpointer-arith  -g -O2 -o ddraw.spec.o ddraw.spec.c
> {standard input}: Assembler messages:
> {standard input}:654: Error: no such instruction: `yes "ddraw.dll"'
> {standard input}:655: Error: no such instruction: `yes
> "DDHAL32_VidMemAlloc"'
> {standard input}:656: Error: no such instruction: `yes

"DDHAL32_VidMemFree"'
> {standard input}:657: Error: no such instruction: `yes "DDInternalLock"'
>
> and so on, lots more of the same. Anyone else getting these?

I've determined that version 1.73 of tools/winebuild/spec32.c is what is
causing this. Reverting to 1.72 cures this particular problem for me. My
system is a Debian woody installation. Does anyone have any ideas on
what's going on here?

[Vincent Béron]

Le sam 10/01/2004 à 20:05, Sami Aario a écrit :
> ----- Original Message ----- 
> From: "Sami Aario" 
> To: 
> Sent: Saturday, January 10, 2004 1:55 AM
> Subject: Build fails for current CVS update
> > Hi,
> >
> > Building with tools/wineinstall fails with the latest CVS update on my
> > system with the following:
>
> gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include -D__WINE
> >
>
> SRC__  -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-stri
> > ct-aliasing -gstabs+ -Wpointer-arith  -g -O2 -o ddraw.spec.o ddraw.spec.c
> > {standard input}: Assembler messages:
> > {standard input}:654: Error: no such instruction: `yes "ddraw.dll"'
> > {standard input}:655: Error: no such instruction: `yes
> > "DDHAL32_VidMemAlloc"'
> > {standard input}:656: Error: no such instruction: `yes
>
> "DDHAL32_VidMemFree"'
> > {standard input}:657: Error: no such instruction: `yes "DDInternalLock"'
> >
> > and so on, lots more of the same. Anyone else getting these?
>
> I've determined that version 1.73 of tools/winebuild/spec32.c is what is
> causing this. Reverting to 1.72 cures this particular problem for me. My
> system is a Debian woody installation. Does anyone have any ideas on
> what's going on here?

Could you provide an excerpt of a gcc -E (rather than gcc -c) run,
around the lines mentionned? Or post it somewhere on the web?
Which gcc version?

Vincent

[Alexandre Julliard]

"Sami Aario"  writes:
> I've determined that version 1.73 of tools/winebuild/spec32.c is what is
> causing this. Reverting to 1.72 cures this particular problem for me. My
> system is a Debian woody installation. Does anyone have any ideas on
> what's going on here?

Do 'make distclean' and rebuild.

[Sami Aario]

----- Original Message ----- 
From: "Alexandre Julliard" 
To: "Sami Aario" 
Cc: 
Sent: Sunday, January 11, 2004 3:58 AM
Subject: Re: Build fails for current CVS update
> "Sami Aario"  writes:
> > I've determined that version 1.73 of tools/winebuild/spec32.c is what is
> > causing this. Reverting to 1.72 cures this particular problem for me. My
> > system is a Debian woody installation. Does anyone have any ideas on
> > what's going on here?
>
> Do 'make distclean' and rebuild.

This solved my problem, thanks.