Bug#593700: warsow: FTBFS on ia64

[Steve McIntyre]

On Fri, Aug 20, 2010 at 02:08:03PM +0100, Julien Cristau wrote:
>Package: src:warsow
>Version: 0.50+dfsg1-1
>Severity: serious
>Justification: fails to build from source
>
>See
>https://buildd.debian.org/fetch.cgi?pkg=warsow&arch=ia64&ver=0.50%2Bdfsg1-1&stamp=1270692298&file=log&as=raw
>
>ia64-linux-gnu-gcc -g -O2 -pipe -I. -I/usr/include -I/usr/X11R6/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wall -O2 -fno-strict-aliasing -ffast-math -funroll-loops -DNDEBUG -c snd_qf/snd_mix.c -o build/qf/snd_mix.o -DPIC -fPIC -D_REENTRANT
>{standard input}: Assembler messages:
>{standard input}:26: Error: Unknown opcode `pushl %edi'
>{standard input}:27: Error: Unknown opcode `pushl %ebx'
>{standard input}:28: Error: bad expression
>{standard input}:28: Error: Illegal operand separator `e'
>{standard input}:29: Error: bad expression
>{standard input}:29: Error: Illegal operand separator `e'
>{standard input}:30: Error: bad expression
>{standard input}:30: Error: Illegal operand separator `e'
>[...]

Looking at the source, it looks like it's assuming that anything
non-Win32 and using GNU C is i386, so it's using inline i386 asm. I
can see some stuff in the Makefile for dealing with other
architectures, but there's no sign of it having any effect here.

I'd suggest changing this package to switch from Architecture: any to
list just i386 etc...

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
Who needs computer imagery when you've got Brian Blessed?