From: Satish Eerpini <eerpini@gmail.com>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Kernel build failure.
Date: Wed, 1 Jul 2009 19:52:41 +0530 [thread overview]
Message-ID: <93655eb70907010722t25dcbaf0j7323800b55354f32@mail.gmail.com> (raw)
In-Reply-To: <b9df5fa10907010615m25664ebao223ef1f770ebbeeb@mail.gmail.com>
> I'm facing the following problem in building kernel.
> Config attached.
>
>
> LD init/built-in.o
> LD .tmp_vmlinux1
> kernel/built-in.o(.text+0x630e): In function `alloc_fair_sched_group':
> : undefined reference to `.L3922'
> kernel/built-in.o(.text+0x6359): In function `alloc_fair_sched_group':
> : undefined reference to `.L3923'
> kernel/built-in.o(.text+0x432c6): In function `add_del_listener':
> : undefined reference to `.L364'
> drivers/built-in.o(.text+0x85e5e): In function `igdng_compute_m_n':
> : undefined reference to `__udivdi3'
> drivers/built-in.o(.init.text+0x3c1d): In function `con_init':
> : undefined reference to `.L1460'
> net/built-in.o(.text+0x414bb): In function `__tcp_alloc_md5sig_pool':
> : undefined reference to `.L1763'
> make: *** [.tmp_vmlinux1] Error 1
>
built the 2.6.31-rc1-git6 kernel with the config you attached and
everything worked fine, and the kernel compilation was done
successfully.
Thanks
Satish
--
http://satish.playdrupal.com
next prev parent reply other threads:[~2009-07-01 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 13:15 Rakib Mullick
2009-07-01 14:22 ` Satish Eerpini [this message]
2009-07-02 13:45 ` Rakib Mullick
2009-07-14 12:34 ` 2.6.31-rc3: include/trace/events/kmem.h:47: undefined reference to `.L1600' (was: Kernel build failure.) Andreas Mohr
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 3:31 Kernel Build Failure Chris Holvenstot
2007-07-31 4:01 ` Randy Dunlap
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=93655eb70907010722t25dcbaf0j7323800b55354f32@mail.gmail.com \
--to=eerpini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rakib.mullick@gmail.com \
--cc=sam@ravnborg.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®