From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot-generated ARM toolchain can't compile kernel
Date: Fri, 12 Sep 2008 16:57:10 +0200 [thread overview]
Message-ID: <20080912165710.3e5a0037@surf> (raw)
Hi,
With a recent Buildroot checkout (a few days ago), I've generated a
toolchain for ARM, with gcc 4.2.4 and uclibc 0.9.29. My buildroot
configuration is available at :
http://toulibre.org/~thomas/buildroot/buildroot-config-arm-udivdi3-problem
This toolchain is not able to build a ARM kernel (2.6.25), it fails at
link time complaining about __udivdi3 not being present:
LD vmlinux
net/built-in.o: In function `rt_worker_func':
stats.c:(.text+0x1f7cc): undefined reference to `__udivdi3'
stats.c:(.text+0x1f86c): undefined reference to `__udivdi3'
stats.c:(.text+0x1f884): undefined reference to `__udivdi3'
stats.c:(.text+0x1f9b4): undefined reference to `__udivdi3'
make: *** [vmlinux] Error 1
If I build the exact same kernel with an ARM toolchain generated by
Buildroot, but using gcc 3.4.5 and uclibc 0.9.28, it compiles fine.
When objdumping the kernel, the function rt_worker_func() really makes
some calls to __udivdi3, which shouldn't happen since the kernel uses
a do_div() macro and should never use any function of libgcc.
Any idea of what is happening ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
reply other threads:[~2008-09-12 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080912165710.3e5a0037@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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