From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.30-rc2
Date: Wed, 15 Apr 2009 22:22:58 +1000 [thread overview]
Message-ID: <49E5D1A2.7010901@eyal.emu.id.au> (raw)
In-Reply-To: <alpine.LFD.2.00.0904141628570.4132@localhost.localdomain>
I get a build failure with this one:
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
arch/x86/mm/built-in.o(.init.text+0x178a): In function `memtest':
: undefined reference to `__udivdi3'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2
I have
gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
I know, very old Debian... but the doco says required version is 3.2.
A quick search indicates that this type of failure may be related to
gcc version related optimization. I saw similar reports in linux-next recently.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au)
prev parent reply other threads:[~2009-04-15 12:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 23:48 Linus Torvalds
2009-04-15 0:22 ` Alessandro Suardi
2009-04-15 1:17 ` Linus Torvalds
2009-04-15 0:40 ` patch-2.6.30-rc2.bz2 does not apply cleanly Tetsuo Handa
2009-04-15 1:42 ` Linux 2.6.30-rc2 Zhang, Yanmin
2009-04-15 2:01 ` Linus Torvalds
2009-04-15 2:24 ` Tetsuo Handa
2009-04-15 13:26 ` Alessandro Suardi
2009-04-15 6:21 ` Brice Goglin
2009-04-15 7:33 ` yakui_zhao
2009-04-15 7:41 ` Zhang Rui
2009-04-15 7:43 ` Brice Goglin
2009-04-15 8:33 ` Linux 2.6.30-rc2: [PATCH] ARM OABI compatibility: fix build error Matthias Kaehlcke
2009-04-15 9:03 ` Russell King - ARM Linux
2009-04-15 9:12 ` Matthias Kaehlcke
2009-04-15 9:29 ` Russell King - ARM Linux
2009-04-15 9:35 ` Matthias Kaehlcke
2009-04-15 12:22 ` Eyal Lebedinsky [this message]
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=49E5D1A2.7010901@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®