From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linuxfoundation.org, jdike@addtoit.com,
linux-kernel@vger.kernel.org,
Peter Oberparleiter <oberparleiter@googlemail.com>
Subject: Re: 2.6.26-rc5-mm1: uml link error
Date: Tue, 10 Jun 2008 12:51:39 +0200 [thread overview]
Message-ID: <484E5CBB.2040203@de.ibm.com> (raw)
In-Reply-To: <E1K5oBn-0006v4-KJ@pomaz-ex.szeredi.hu>
Miklos Szeredi wrote:
> I get this error on linking uml:
>
> /usr/lib64/gcc/x86_64-suse-linux/4.2.1/../../../../x86_64-suse-linux/bin/ld:arch/um/kernel/vmlinux.lds:267: syntax error
>
> Reverting 'kernel-call-constructors.patch' fixes it.
Should be fixed with the patch below (applies on top of
kernel-call-constructors.patch):
--
From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
Fix for linker error on UML:
/usr/lib64/gcc/x86_64-suse-linux/4.2.1/../../../../x86_64-suse-linux/bin/ld:arch/um/kernel/vmlinux.lds:267: syntax error
The error is triggered by the use of SORT(CONSTRUCTORS) in the UML
linker script which conflicts with the kernel-call-constructors patch.
Here is what the ld info page says about sorting constructors:
If you are using the GNU C++ support for initialization priority,
which provides some control over the order in which global
constructors are run, you must sort the constructors at link time
to ensure that they are executed in the correct order.
As there's no C++ code inside the kernel it should be safe to remove
the SORT construct.
Found-by: Miklos Szeredi <miklos@szeredi.hu>
Signed-off-by: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
---
arch/um/kernel/dyn.lds.S | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.26-rc5-mm2/arch/um/kernel/dyn.lds.S
===================================================================
--- linux-2.6.26-rc5-mm2.orig/arch/um/kernel/dyn.lds.S
+++ linux-2.6.26-rc5-mm2/arch/um/kernel/dyn.lds.S
@@ -102,7 +102,7 @@ SECTIONS
*(.data.init_irqstack)
DATA_DATA
*(.data.* .gnu.linkonce.d.*)
- SORT(CONSTRUCTORS)
+ CONSTRUCTORS
}
.data1 : { *(.data1) }
.tdata : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
next prev parent reply other threads:[~2008-06-10 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 20:42 2.6.26-rc5-mm1: uml link error Miklos Szeredi
2008-06-10 10:51 ` Peter Oberparleiter [this message]
2008-06-10 11:19 ` Miklos Szeredi
2008-06-10 13:57 ` Jeff Dike
2008-06-10 14:08 ` Miklos Szeredi
2008-06-10 14:08 ` Peter 1 Oberparleiter
2008-06-10 14:21 ` Peter Oberparleiter
2008-06-10 15:27 ` Jeff Dike
2008-06-10 16:54 ` Jeff Dike
2008-06-10 17:21 ` Sam Ravnborg
2008-06-11 12:18 ` Peter Oberparleiter
2008-06-11 12:38 ` Miklos Szeredi
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=484E5CBB.2040203@de.ibm.com \
--to=peter.oberparleiter@de.ibm.com \
--cc=akpm@linuxfoundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=oberparleiter@googlemail.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.