From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: simon@baydel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: unresolved symbols __udivdi3 and __umoddi3
Date: Fri, 25 Jan 2002 12:06:42 -0500 [thread overview]
Message-ID: <20020125170642.GG671@online.fr> (raw)
In-Reply-To: <3C50FBAE.26883.8EF8C@localhost>
In-Reply-To: <3C50FBAE.26883.8EF8C@localhost>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
GFS uses (provide) a module which provides these symbols.
I don't know if this is still the case with their non-free software but
you can certainly find the last free GFS release.
You can have a look at
http://www.sistina.com
but I guess that if they provide a way to get the last free release this
will not be a easy to find link.
Or at
http://www.opengfs.org
But IIRC these symbol were used only for the 2.2 kernel (that I assume
you are using?) and the support for 2.2 kernel was removed in the
opengfs fork.
Christophe
On Fri, Jan 25, 2002 at 06:31:10AM -0000, simon@baydel.com wrote:
> I am writing a module and would like to perform arithmetic on long
> long variables. When I try to do this the module does not load due
> to the unresolved symbols __udivdi3 and __umoddi3. I notice these
> are normally defined in libc. Is there any way I can do this in a
> kernel module.
>
> Many Thanks
>
> Simon.
> __________________________
>
> Simon Haynes - Baydel
> Phone : 44 (0) 1372 378811
> Email : simon@baydel.com
> __________________________
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
Dogs believe they are human. Cats believe they are God.
[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]
next prev parent reply other threads:[~2002-01-25 17:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 6:31 unresolved symbols __udivdi3 and __umoddi3 simon
2002-01-25 16:45 ` Andreas Dilger
2002-01-25 16:56 ` Richard B. Johnson
2002-01-25 21:42 ` Tim Schmielau
2002-01-28 4:21 ` simon
2002-01-28 17:38 ` Tim Schmielau
2002-01-28 19:17 ` Daniel Phillips
2002-01-28 19:28 ` Mark Zealey
2002-01-28 19:46 ` Momchil Velikov
2002-01-28 20:06 ` Daniel Phillips
2002-01-28 20:14 ` Momchil Velikov
2002-01-29 16:38 ` Horst von Brand
2002-01-30 8:09 ` Daniel Phillips
2002-01-30 8:43 ` Jeff Garzik
2002-01-30 8:23 ` Jeff Garzik
2002-01-28 11:08 ` Daniel Phillips
2002-01-28 11:10 ` Arjan van de Ven
2002-01-28 11:47 ` Daniel Phillips
2002-01-25 17:06 ` christophe barbé [this message]
2002-01-25 18:53 ` Christoph Hellwig
2002-01-25 19:03 ` christophe barbé
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=20020125170642.GG671@online.fr \
--to=christophe.barbe.ml@online.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@baydel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.