[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bug 336022 closed but not fixed(broken binutils)



I had this problem when compiling kernel 2.4.27. The fault, as you have found, was with binutilts. I applied a patch from kernel.org for 2.4 kernels. Just gone there and noticed there is, or so I assume, a patch for 2.6 kernels. Anyway, here they are...

http://www.kernel.org/pub/linux/devel/binutils/linux-2.4-seg-4.patch
http://www.kernel.org/pub/linux/devel/binutils/linux-2.6-seg-5.patch

Worth a try, no?

Steve.


Hendrik Sattler wrote:

NZG wrote:

I'm having the same problem described in bug 336022.
After upgrading binutils to the most recent testing version I cannot
compile any kernel other than 2.6.14.
This bug was closed with the recommendation to upgrade you binutils and/or
use a more recent kernel.

I have done both, but the problem remains.

standard input}:688: Error: suffix or operands invalid for `mov'
{standard input}:689: Error: suffix or operands invalid for `mov'
{standard input}:887: Error: suffix or operands invalid for `mov'
{standard input}:888: Error: suffix or operands invalid for `mov'
{standard input}:967: Error: suffix or operands invalid for `mov'
{standard input}:968: Error: suffix or operands invalid for `mov'
{standard input}:1051: Error: suffix or operands invalid for `mov'
{standard input}:1052: Error: suffix or operands invalid for `mov'
{standard input}:1061: Error: suffix or operands invalid for `mov'
{standard input}:1073: Error: suffix or operands invalid for `mov'
I have tried using gcc-2.95, gcc-3.3, and gcc-4.0.
They all do exactly the same thing.

Same problem here when trying to compile 2.4.25 for some older stuff. Using a Sarge chroot fixed it. 'as' just complains more and that's the problem. Either you stick with older binutils or you have to fix the process.c file in the kernel tree by fixing the inline asm. Maybe there is a patch out there?

HS




Reply to: