From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: linker error: section __modver vma 0x6028c000 overlaps previous
Date: Wed, 9 May 2012 20:49:42 +0200 [thread overview]
Message-ID: <20120509184941.GA2772@grml> (raw)
In-Reply-To: <CAGdaadba0VehNBk2VL+9T6L-OUk8Gc9UmbRN-5v+z78A0vL6ag@mail.gmail.com>
Hi!
On 00:19 Thu 10 May , Mulyadi Santosa wrote:
> Hi...
>
> On Wed, May 9, 2012 at 11:41 AM,
> <michi1@michaelblizek.twilightparadox.com> wrote:
> > /usr/bin/ld: .tmp_vmlinux2: section __modver vma 0x6028c000 overlaps previous sections
> > ?KSYM ? ?.tmp_kallsyms2.S
> > ?AS ? ? ?.tmp_kallsyms2.o
> > ?LD ? ? ?vmlinux
> > /usr/bin/ld: vmlinux: section __modver vma 0x6028c000 overlaps previous sections
> > ?SYSMAP ?System.map
> > ?SYSMAP ?.tmp_System.map
> > ?LINK linux
>
> modver.... hmmm, raw guess, what happen if you turn off module
> versioning in kernel config?
Module versioning was turned off. If I turn it on, the error disappears.
> And, does this happen if you build standard (non UML) kernel?
I do not have a non-uml config ready for this kernel. "make oldconfig" asks
for almost every option which exists.
-Michi
next prev parent reply other threads:[~2012-05-09 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 4:41 linker error: section __modver vma 0x6028c000 overlaps previous michi1 at michaelblizek.twilightparadox.com
2012-05-09 17:19 ` Mulyadi Santosa
2012-05-09 18:49 ` michi1 at michaelblizek.twilightparadox.com [this message]
2012-05-10 4:53 ` Mulyadi Santosa
2012-05-10 5:36 ` michi1 at michaelblizek.twilightparadox.com
2012-05-10 15:41 ` michi1 at michaelblizek.twilightparadox.com
2012-05-11 17:03 ` Mulyadi Santosa
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=20120509184941.GA2772@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.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.