From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: linux-next@vger.kernel.org
Subject: linux-next: sparc build failure
Date: Mon, 12 May 2008 17:36:58 +1000 [thread overview]
Message-ID: <20080512173658.01dc993f.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Hi Dave,
Today's linux-next build (sparc allmodconfig) fails like this:
In file included from include2/asm/sigcontext.h:6,
from include2/asm/signal.h:5,
from include/linux/signal.h:4,
from fs/ocfs2/dlm/userdlm.c:30:
include2/asm/ptrace.h:42: error: syntax error before "pt_regs_is_syscall"
include2/asm/ptrace.h:43: warning: return type defaults to `int'
include2/asm/ptrace.h:47: error: syntax error before "pt_regs_clear_syscall"
include2/asm/ptrace.h:48: warning: return type defaults to `int'
In file included from include2/asm/sigcontext.h:6,
from include2/asm/signal.h:5,
from include/linux/signal.h:4,
from drivers/net/usb/rtl8150.c:10:
include2/asm/ptrace.h:42: error: syntax error before "pt_regs_is_syscall"
include2/asm/ptrace.h:43: warning: return type defaults to `int'
include2/asm/ptrace.h:47: error: syntax error before "pt_regs_clear_syscall"
include2/asm/ptrace.h:48: warning: return type defaults to `int'
Seems to have been introduced by commit
28e6103665301ce60634e8a77f0b657c6cc099de ("sparc: Fix debugger syscall
restart interactions") which went into Linus' tree recently ("bool" seems
to be missing a definition).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-05-12 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 7:36 Stephen Rothwell [this message]
2008-05-12 7:40 ` linux-next: sparc build failure David Miller
2008-05-12 7:43 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 6:51 Stephen Rothwell
2008-08-28 6:57 ` Ingo Molnar
2008-08-28 7:12 ` Stephen Rothwell
2008-08-28 7:25 ` Ingo Molnar
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=20080512173658.01dc993f.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.