From: Sachin Sant <sachinp@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
linux-s390@vger.kernel.org
Subject: Next Aug 19: s390 build failure (arch/s390/kernel/built-in)
Date: Wed, 19 Aug 2009 16:43:29 +0530 [thread overview]
Message-ID: <4A8BDE59.2010400@in.ibm.com> (raw)
In-Reply-To: <20090819190233.86e78493.sfr@canb.auug.org.au>
Today's next build failed on s390 with following errors.
LD .tmp_vmlinux1
arch/s390/kernel/built-in.o: In function `trace_syscall_exit':
include/trace/syscall.h:21: undefined reference to `__tracepoint_syscall_exit'
include/trace/syscall.h:21: undefined reference to `__tracepoint_syscall_exit'
arch/s390/kernel/built-in.o: In function `trace_syscall_enter':
include/trace/syscall.h:14: undefined reference to `__tracepoint_syscall_enter'
include/trace/syscall.h:14: undefined reference to `__tracepoint_syscall_enter'
make: *** [.tmp_vmlinux1] Error 1
thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-08-19 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 9:02 linux-next: Tree for August 19 Stephen Rothwell
2009-08-19 9:35 ` Joel Becker
2009-08-24 7:30 ` Stephen Rothwell
2009-08-19 11:13 ` Sachin Sant [this message]
2009-08-19 11:46 ` Next Aug 19: s390 build failure (arch/s390/kernel/built-in) Ingo Molnar
2009-08-19 11:55 ` Sachin Sant
2009-08-19 12:15 ` [patch] " Ingo Molnar
2009-08-19 13:16 ` Jason Baron
2009-08-19 13:33 ` Sachin Sant
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=4A8BDE59.2010400@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).