All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [signal:arch-sh 1/2] (.data+0x1bc): undefined reference to `sys_sh_pipe'
Date: Mon, 15 Oct 2012 02:37:05 +0000	[thread overview]
Message-ID: <20121015023705.GA15472@localhost> (raw)

Hi Al,

FYI, kernel build failed on

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git arch-sh
head:   c366433956b536324357513f03f1fe6264d8ff98
commit: 4d2fef5f3f0f7cf0ea1a19f63dc8f6637ce41b5c [1/2] sh: switch to generic kernel_thread()/kernel_execve()
config: sh-allnoconfig # make ARCH=sh allnoconfig

All error/warnings:

arch/sh/kernel/cpu/sh2/../../entry-common.S: Assembler messages:
arch/sh/kernel/cpu/sh2/../../entry-common.S:375: Warning: overflow in branch to syscall_exit_work; converted into longer instruction sequence
arch/sh/kernel/cpu/sh2/../../entry-common.S:378: Warning: overflow in branch to syscall_exit_work; converted into longer instruction sequence
--
arch/sh/kernel/built-in.o: In function `sys_call_table':
(.data+0x1bc): undefined reference to `sys_sh_pipe'
arch/sh/kernel/built-in.o: In function `sys_call_table':
(.data+0x3e4): undefined reference to `sys_pread_wrapper'
arch/sh/kernel/built-in.o: In function `sys_call_table':
(.data+0x3e8): undefined reference to `sys_pwrite_wrapper'
arch/sh/kernel/built-in.o: In function `sys_call_table':
(.data+0x554): undefined reference to `sys_fadvise64_64_wrapper'

---
0-DAY kernel build testing backend         Open Source Technology Center
Fengguang Wu, Yuanhan Liu                              Intel Corporation

             reply	other threads:[~2012-10-15  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  2:37 Fengguang Wu [this message]
2012-10-15  3:20 ` [signal:arch-sh 1/2] (.data+0x1bc): undefined reference to `sys_sh_pipe' Al Viro

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=20121015023705.GA15472@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kernel-janitors@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.