Bug#336022: gcc-2.95: kernel 2.4.31 won't compile
Package: gcc-2.95
Version: 1:2.95.4-22
Severity: normal
make bzImage CC=gcc-2.95
..
make CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.31/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 " -C arch/i386/kernel
make[1]: Entering directory `/usr/src/linux-2.4.31/arch/i386/kernel'
gcc-2.95 -D__KERNEL__ -I/usr/src/linux-2.4.31/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENAME=process -c -o process.o process.c
{standard input}: Assembler messages:
{standard input}:853: Error: suffix or operands invalid for `mov'
{standard input}:854: Error: suffix or operands invalid for `mov'
{standard input}:947: Error: suffix or operands invalid for `mov'
{standard input}:948: Error: suffix or operands invalid for `mov'
{standard input}:1006: Error: suffix or operands invalid for `mov'
{standard input}:1007: Error: suffix or operands invalid for `mov'
{standard input}:1009: Error: suffix or operands invalid for `mov'
{standard input}:1021: Error: suffix or operands invalid for `mov'
make[1]: *** [process.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.31/arch/i386/kernel'
make: *** [_dir_arch/i386/kernel] Error 2
I also found someone reporting this error on debian-users ML.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.4
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages gcc-2.95 depends on:
ii binutils 2.16.1cvs20050902-1 The GNU assembler, linker and bina
ii cpp-2.95 1:2.95.4-22 The GNU C preprocessor
ii libc6 2.3.5-7 GNU C Library: Shared libraries an
Versions of packages gcc-2.95 recommends:
ii libc6-dev [libc-dev] 2.3.5-7 GNU C Library: Development Librari
-- no debconf information
Reply to: