From: Andrew Morton <akpm@linux-foundation.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: jdike@addtoit.com, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [Patch] uml: fix a link error
Date: Fri, 16 Jan 2009 12:41:58 -0800 [thread overview]
Message-ID: <20090116124158.4364e269.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090115194033.GA10926@hack.private>
On Thu, 15 Jan 2009 19:40:33 +0000
Am__rico Wang <xiyou.wangcong@gmail.com> wrote:
>
> This patch fixes the following link error:
>
> LD .tmp_vmlinux1
> arch/um/sys-i386/built-in.o: In function sys_call_table':
> (.rodata+0x308): undefined reference to sys_sigprocmask'
> collect2: ld returned 1 exit status
> KSYM .tmp_kallsyms1.S
> nm: '.tmp_vmlinux1': No such file
> AS .tmp_kallsyms1.o
> LD .tmp_vmlinux2
> arch/um/sys-i386/built-in.o: In function sys_call_table':
> (.rodata+0x308): undefined reference to sys_sigprocmask'
> collect2: ld returned 1 exit status
> make[1]: *** [.tmp_vmlinux2] Error 1
> make: *** [sub-make] Error 2
>
>
> Signed-off-by: WANG Cong <wangcong@zeuux.org>
> Cc: Jeff Dike <jdike@addtoit.com>
>
> ---
> diff --git a/arch/um/sys-i386/sys_call_table.S b/arch/um/sys-i386/sys_call_table.S
> index 00e5f52..04147dc 100644
> --- a/arch/um/sys-i386/sys_call_table.S
> +++ b/arch/um/sys-i386/sys_call_table.S
> @@ -6,6 +6,7 @@
>
> #define sys_vm86old sys_ni_syscall
> #define sys_vm86 sys_ni_syscall
> +#define sys_sigprocmask sigprocmask
>
> #define old_mmap old_mmap_i386
>
For how long has this problem been present?
Why aren't lots of other people reporting it?
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org, jdike@addtoit.com,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [Patch] uml: fix a link error
Date: Fri, 16 Jan 2009 12:41:58 -0800 [thread overview]
Message-ID: <20090116124158.4364e269.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090115194033.GA10926@hack.private>
On Thu, 15 Jan 2009 19:40:33 +0000
Am__rico Wang <xiyou.wangcong@gmail.com> wrote:
>
> This patch fixes the following link error:
>
> LD .tmp_vmlinux1
> arch/um/sys-i386/built-in.o: In function sys_call_table':
> (.rodata+0x308): undefined reference to sys_sigprocmask'
> collect2: ld returned 1 exit status
> KSYM .tmp_kallsyms1.S
> nm: '.tmp_vmlinux1': No such file
> AS .tmp_kallsyms1.o
> LD .tmp_vmlinux2
> arch/um/sys-i386/built-in.o: In function sys_call_table':
> (.rodata+0x308): undefined reference to sys_sigprocmask'
> collect2: ld returned 1 exit status
> make[1]: *** [.tmp_vmlinux2] Error 1
> make: *** [sub-make] Error 2
>
>
> Signed-off-by: WANG Cong <wangcong@zeuux.org>
> Cc: Jeff Dike <jdike@addtoit.com>
>
> ---
> diff --git a/arch/um/sys-i386/sys_call_table.S b/arch/um/sys-i386/sys_call_table.S
> index 00e5f52..04147dc 100644
> --- a/arch/um/sys-i386/sys_call_table.S
> +++ b/arch/um/sys-i386/sys_call_table.S
> @@ -6,6 +6,7 @@
>
> #define sys_vm86old sys_ni_syscall
> #define sys_vm86 sys_ni_syscall
> +#define sys_sigprocmask sigprocmask
>
> #define old_mmap old_mmap_i386
>
For how long has this problem been present?
Why aren't lots of other people reporting it?
next prev parent reply other threads:[~2009-01-16 20:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 19:40 [uml-devel] [Patch] uml: fix a link error Américo Wang
2009-01-15 19:40 ` Américo Wang
2009-01-16 20:41 ` Andrew Morton [this message]
2009-01-16 20:41 ` Andrew Morton
2009-01-16 21:38 ` [uml-devel] " Jeff Dike
2009-01-16 21:38 ` Jeff Dike
2009-01-17 9:28 ` [uml-devel] " Rob Landley
2009-01-17 9:28 ` Rob Landley
2009-01-18 6:23 ` Daolong Wang
2009-01-18 6:23 ` Daolong Wang
2009-01-19 15:21 ` Jeff Dike
2009-01-19 15:21 ` Jeff Dike
2009-01-20 1:46 ` Daolong Wang
2009-01-20 1:46 ` Daolong Wang
2009-01-20 2:01 ` Shane Hathaway
2009-01-20 2:01 ` Shane Hathaway
2009-01-27 9:23 ` Al Viro
2009-01-27 9:23 ` Al Viro
2009-02-04 17:26 ` Geert Uytterhoeven
2009-02-04 17:26 ` Geert Uytterhoeven
2009-02-04 20:32 ` Geert Uytterhoeven
2009-02-04 20:32 ` Geert Uytterhoeven
2009-02-04 20:40 ` Greg KH
2009-02-04 20:40 ` Greg KH
2009-02-04 20:54 ` Geert Uytterhoeven
2009-02-04 20:54 ` Geert Uytterhoeven
2009-02-07 11:59 ` Heiko Carstens
2009-02-07 11:59 ` Heiko Carstens
2009-02-08 9:07 ` Américo Wang
2009-02-08 9:07 ` Américo Wang
2009-02-08 9:12 ` Américo Wang
2009-02-08 9:12 ` Américo Wang
2009-02-12 14:40 ` Geert Uytterhoeven
2009-02-12 14:40 ` Geert Uytterhoeven
2009-01-18 8:32 ` Américo Wang
2009-01-18 8:32 ` Américo Wang
2009-01-18 23:29 ` Rob Landley
2009-01-18 23:29 ` Rob Landley
2009-01-22 16:12 ` Américo Wang
2009-01-22 16:12 ` Américo Wang
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=20090116124158.4364e269.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=xiyou.wangcong@gmail.com \
/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.