From: Carlos Munoz <carlos@kenati.com>
To: linux-kernel@vger.kernel.org
Subject: How can I link the kernel with libgcc ?
Date: Thu, 09 Mar 2006 17:44:16 -0800 [thread overview]
Message-ID: <4410D9F0.6010707@kenati.com> (raw)
Hi all,
I'm writing an audio driver and the hardware requires floating point
arithmetic. When I build the kernel I get the following errors at link
time:
*** Warning: "__subdf3" [sound/sh/siu_sh7343.ko] undefined!
*** Warning: "__muldf3" [sound/sh/siu_sh7343.ko] undefined!
*** Warning: "__divdf3" [sound/sh/siu_sh7343.ko] undefined!
*** Warning: "__adddf3" [sound/sh/siu_sh7343.ko] undefined!
These symbols are coming from gcc. What I would like to do is link the
kernel with libgcc to solve this errors. I'm looking at the kernel
makefiles and it doesn't seem obvious to me how to do it. Does anyone
know how I can link the kernel with libgcc, or point me in the right
direction ?
By the way this is for the Renesas SH7343 processor.
Thanks,
Carlos Munoz
next reply other threads:[~2006-03-10 1:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 1:44 Carlos Munoz [this message]
2006-03-10 1:45 ` How can I link the kernel with libgcc ? Valdis.Kletnieks
2006-03-10 2:06 ` Lee Revell
2006-03-10 3:01 ` Carlos Munoz
2006-03-10 3:22 ` Lee Revell
2006-03-10 3:25 ` Carlos Munoz
2006-03-10 3:25 ` Lee Revell
2006-03-10 3:47 ` Carlos Munoz
2006-03-10 10:37 ` Denis Vlasenko
2006-03-10 11:05 ` Bart Hartgers
2006-03-10 18:03 ` Carlos Munoz
2006-03-10 18:33 ` linux-os (Dick Johnson)
2006-03-10 18:41 ` Ben Slusky
2006-03-10 19:18 ` Al Viro
2006-03-10 20:04 ` Carlos Munoz
2006-03-10 10:18 ` Jes Sorensen
2006-03-10 18:07 ` Carlos Munoz
2006-03-10 8:01 ` Arjan van de Ven
2006-03-10 2:02 ` Lee Revell
[not found] <5OEVB-3GX-15@gated-at.bofh.it>
2006-03-10 2:32 ` Robert Hancock
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=4410D9F0.6010707@kenati.com \
--to=carlos@kenati.com \
--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