From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: TQ2440 problem
Date: Mon, 12 Jul 2010 10:14:23 +0200 [thread overview]
Message-ID: <20100712081423.GC1532@pengutronix.de> (raw)
In-Reply-To: <AANLkTimQ62x7qhzNj2WDsi6D6XI-H1ayXx4-Hd6dg6Yt@mail.gmail.com>
Hello,
On Sat, Jul 10, 2010 at 02:01:19PM +0800, CoffBeta wrote:
> CHK include/linux/compile.h
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> init/built-in.o: In function `do_one_initcall':
> /home/ymcheng/linux-2.6.27/init/main.c:704: undefined reference to
> `__gnu_mcount_nc'
> init/built-in.o: In function `init_post':
> /home/ymcheng/linux-2.6.27/init/main.c:796: undefined reference to
> `__gnu_mcount_nc'
> init/built-in.o: In function `name_to_dev_t':
> /home/ymcheng/linux-2.6.27/init/do_mounts.c:76: undefined reference to
> `__gnu_mcount_nc'
> init/built-in.o: In function `set_reset_devices':
> /home/ymcheng/linux-2.6.27/init/main.c:183: undefined reference to
> `__gnu_mcount_nc'
> init/built-in.o: In function `debug_kernel':
> /home/ymcheng/linux-2.6.27/init/main.c:234: undefined reference to
> `__gnu_mcount_nc'
> init/built-in.o:/home/ymcheng/linux-2.6.27/init/main.c:240: more undefined
> references to `__gnu_mcount_nc' follow
> make: *** [.tmp_vmlinux1] ?? 1
>
> why????how can I do it? thanks
Your toolchain is too new for a kernel that old. You need a kernel
having 181f817eaaca4c1f8a9c265d339d2b96de8b245d.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2010-07-12 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 6:01 TQ2440 problem CoffBeta
2010-07-12 8:14 ` Uwe Kleine-König [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=20100712081423.GC1532@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).