This is a discussion on Assembler errors when compiling kernels 2.4.30 and 2.6.11.9 within the Linux Operating System forums, part of the Unix Operating Systems category; --> In phase "make bzImage" I get the following error: CC arch/i386/kernel/process.o {standard input}: Assembler messages: {standard input}:886: Error: suffix ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In phase "make bzImage" I get the following error: CC arch/i386/kernel/process.o {standard input}: Assembler messages: {standard input}:886: Error: suffix or operands invalid for `mov' {standard input}:887: Error: suffix or operands invalid for `mov' {standard input}:1096: Error: suffix or operands invalid for `mov' {standard input}:1097: Error: suffix or operands invalid for `mov' {standard input}:1168: Error: suffix or operands invalid for `mov' {standard input}:1169: Error: suffix or operands invalid for `mov' {standard input}:1270: Error: suffix or operands invalid for `mov' {standard input}:1271: Error: suffix or operands invalid for `mov' {standard input}:1282: Error: suffix or operands invalid for `mov' {standard input}:1294: Error: suffix or operands invalid for `mov' make[1]: *** [arch/i386/kernel/process.o] Error 1 make: *** [arch/i386/kernel] Error 2 I have the following tools: gcc-2.96-112.7.2 (Red Hat rpm) make-3.79.1-8 (Red Hat rpm) binutils-2.16.90.0.3 (self-compiled) util-linux-2.11f-9 (Red Hat rpm) module-init-tools-3.1 (self-compiled) e2fsprogs-1.37 (self-compiled) These tools have greater or equal versions compared to what is required according to the file "Documentation/Changes" of kernel 2.6.11.9. I have seen claims that you should not use gcc 2.96 to compile a kernel, but the Changes file says "2.96 compiler subtree can also be used to build this tree. You should ensure you use gcc-2.96-74 or later." Why do I get this error? My system is originally a Red Hat 7.2, and Red Hat provides gcc3-3.0.4-1 as a rpm package, should I try to use that? Or should I revert to the Red Hat kgcc? |
| |||
| In comp.os.linux.setup juhani.jaakola@kolumbus.fi: > In phase "make bzImage" I get the following error: > CC arch/i386/kernel/process.o > {standard input}: Assembler messages: > {standard input}:886: Error: suffix or operands invalid for `mov' > {standard input}:887: Error: suffix or operands invalid for `mov' [..] > make[1]: *** [arch/i386/kernel/process.o] Error 1 > make: *** [arch/i386/kernel] Error 2 > I have the following tools: > gcc-2.96-112.7.2 (Red Hat rpm) No wonder, you'll get nowhere with this gcc version. IIRC, never got 2.6.x compiled with it, even if it worked nice with 2.4. Do your self a big favor and upgrade the complete system to some recent distro. [..] -- Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94) mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/' #bofh excuse 296: The hardware bus needs a new token. |
| |||
| I tried to compile the 2.6.11.9 kernel with the Red Hat gcc3-3.0.4-1 rpm, but I got the same error. Then I installed GCC 3.4.3, but again I got the same error. Should I re-compile binutils-2.16.90.0.3 with GCC 3.4.3, I compiled that with GCC 2.96? Or is process.c in the kernel broken (both in 2.6.11.9 and 2.4.30), that's where the error occurs????? |
| |||
| juhani.jaakola@kolumbus.fi wrote in message news:<1116184306.709239.288160@g49g2000cwa.googleg roups.com>... > In phase "make bzImage" I get the following error: > > CC arch/i386/kernel/process.o > {standard input}: Assembler messages: > {standard input}:886: Error: suffix or operands invalid for `mov' .... > > I have the following tools: > > gcc-2.96-112.7.2 (Red Hat rpm) > make-3.79.1-8 (Red Hat rpm) > binutils-2.16.90.0.3 (self-compiled) > util-linux-2.11f-9 (Red Hat rpm) > module-init-tools-3.1 (self-compiled) > e2fsprogs-1.37 (self-compiled) > .... I re-compiled binutils-2.16.90.0.3 with gcc-3.4.3 and then I tried to compile kernel 2.6.11.9 again (with gcc-3.4.3), and I got the same error messages again. What could I try next? |
| |||
| In comp.os.linux.setup juhani.jaakola@kolumbus.fi: > I tried to compile the 2.6.11.9 kernel with the Red Hat gcc3-3.0.4-1 > rpm, but I got the same error. > Then I installed GCC 3.4.3, but again I got the same error. > Should I re-compile binutils-2.16.90.0.3 with GCC 3.4.3, I compiled > that with GCC 2.96? > Or is process.c in the kernel broken (both in 2.6.11.9 and 2.4.30), > that's where the error occurs????? There's nothing broken, despite your system. Upgrading to a recent distro would save you many pain. Backup /etc and /home and start over with a new distro. Good luck BTW Please, please keep some context while replying. Seems to be a recent cancer by people using google to post? Is the interface used by google broken or are people just using the wrong button to reply? -- Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94) mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/' #bofh excuse 399: We are a 100% Microsoft Shop. |
| |||
| juhani.jaakola@kolumbus.fi (Juhani Jaakola) wrote in message news:<acce1105.0505162337.7eff83e4@posting.google. com>... > > In phase "make bzImage" I get the following error: > > > > CC arch/i386/kernel/process.o > > {standard input}: Assembler messages: > > {standard input}:886: Error: suffix or operands invalid for `mov' .... > > I have the following tools: > > > > gcc-2.96-112.7.2 (Red Hat rpm) > > make-3.79.1-8 (Red Hat rpm) > > binutils-2.16.90.0.3 (self-compiled) > > util-linux-2.11f-9 (Red Hat rpm) > > module-init-tools-3.1 (self-compiled) > > e2fsprogs-1.37 (self-compiled) .... > I re-compiled binutils-2.16.90.0.3 with gcc-3.4.3 and then I tried to > compile kernel 2.6.11.9 again (with gcc-3.4.3), and I got the same > error messages again. What could I try next? There are two bug reports about this, one in the Mandrake and the other in binutils bug reporting systems: http://archives.mandrivalinux.com/co...4/msg03384.php and http://www.mail-archive.com/bug-binu.../msg00325.html Those threads suggest two solutions: - Use binutils 2.15 or - Apply the following patches to kernel http://www.kernel.org/pub/linux/deve....4-seg-4.patch http://www.kernel.org/pub/linux/deve....6-seg-5.patch jneuheisel writes: "...kernel was using movl to access the 16 bit fs and gs registers. The old gas was silently changing the movl to movw, whereas the new gas was throwing an error...it seems to be a kernel issue, not a gas issue." I'll try this tomorrow. |
| ||||
| juhani.jaakola@kolumbus.fi (Juhani Jaakola) wrote in message <news:acce1105.0505162337.7eff83e4@posting.google. com>... > In phase "make bzImage" I get the following error: > CC arch/i386/kernel/process.o > {standard input}: Assembler messages: > {standard input}:886: Error: suffix or operands invalid for `mov' I applied the patch from http://www.kernel.org/pub/linu*x/dev...6-seg*-5.patch to kernel 2.6.11.10 and compiled it successfully with a self-compiled gcc-3.4.3 and binutils-2.16.90.0.3. Now it even boots, on a system which was originally based on Red Hat 7.2! |
| Thread Tools | |
| Display Modes | |
|
|