From: Marc Leeman <marc.leeman@barco.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Insmod trouble
Date: Fri, 2 Apr 2004 08:42:05 +0200 [thread overview]
Message-ID: <20040402064205.GB22365@smtp.barco.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B06DAAE@ismail.innsys.innovsys.com>
> proc_sysinfo: Unknown symbol __fixsfsi
> proc_sysinfo: Unknown symbol __subsf3
> proc_sysinfo: Unknown symbol __extendsfdf2
> proc_sysinfo: Unknown symbol __floatsisf
> proc_sysinfo: Unknown symbol __muldf3
> proc_sysinfo: Unknown symbol __truncdfsf2
> proc_sysinfo: Unknown symbol __mulsf3
> proc_sysinfo: Unknown symbol __addsf3
I would assume that these functions are not compiled in the kernel.
While compiling them as modules, the compiler assumes (via the include
file) that they are external and will not complain about these.
Double check if the source files that contain this functionality are
compiled and linked in the code. You can try to quick-'fix' it by static
inlining these functions in you module.
Maybe these functions assume some architecture and are in a conditional
ifdef CONFIG_XXX flag.
marc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-02 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 0:17 Insmod trouble Rune Torgersen
2004-04-02 6:42 ` Marc Leeman [this message]
2004-04-02 16:54 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 9:05 insmod trouble Marco Schramel
2004-05-25 9:55 ` Wolfgang Denk
2004-05-27 7:15 ` Marco Schramel
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=20040402064205.GB22365@smtp.barco.com \
--to=marc.leeman@barco.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=runet@innovsys.com \
/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).