From: Mike Travis <travis@sgi.com>
To: linux-mm@kvack.org
Subject: [Fwd: [linux-engr] build errors in 2.6.24-rc5-mm1?]
Date: Thu, 20 Dec 2007 09:05:19 -0800 [thread overview]
Message-ID: <476AA0CF.4080201@sgi.com> (raw)
Does anyone have any idea why I'm getting build errors with the current
2.6.24-rc5-mm1? Could it be a gcc version problem? I've looked
through the notes but didn't see anything pertaining to this problem.
linux-2.6.24-rc5-mm1/arch/x86/vdso/vdso32/sigreturn.S: Assembler messages:
linux-2.6.24-rc5-mm1/arch/x86/vdso/vdso32/sigreturn.S:23: Error: suffix or operands invalid for `pop'
linux-2.6.24-rc5-mm1/arch/x86/vdso/vdso32/syscall.S:18: Error: suffix or operands invalid for `push'
linux-2.6.24-rc5-mm1/arch/x86/vdso/vdso32/syscall.S:25: Error: suffix or operands invalid for `pop'
arch/x86/vdso/vdso32/sigreturn.S:
22 .LSTART_sigreturn:
23 popl %eax /* XXX does this mean it needs unwind info? */
24 movl $__NR_sigreturn, %eax
arch/x86/vdso/vdso32/syscall.S:
17 .LSTART_vsyscall:
18 push %ebp
19 .Lpush_ebp:
24 movl %ebp, %ecx
25 popl %ebp
26 .Lpop_ebp:
Thanks!
Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2007-12-20 17:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=476AA0CF.4080201@sgi.com \
--to=travis@sgi.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox