From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: Christoph Hellwig <hch@ns.caldera.de>
Cc: linux-kernel@vger.kernel.org, simon@baydel.com
Subject: Re: unresolved symbols __udivdi3 and __umoddi3
Date: Fri, 25 Jan 2002 14:03:16 -0500 [thread overview]
Message-ID: <20020125190316.GM671@online.fr> (raw)
In-Reply-To: <20020125170642.GG671@online.fr> <200201251853.g0PIrcB28774@ns.caldera.de>
In-Reply-To: <200201251853.g0PIrcB28774@ns.caldera.de>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
On Fri, Jan 25, 2002 at 07:53:38PM +0100, Christoph Hellwig wrote:
> In article <20020125170642.GG671@online.fr> you wrote:
> > 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.
>
> No - OpenGFS 0.0.9x still needs them even on 2.4.
> The next development series leading toward 0.2 will remove that
> requirement by resturcturing all the code that currently uses
> 64bit arithmetics without any real need.
Oh yes my mistake was that GFS for kernel 2.2 require a lfs patch and I
had in mind that it was this patch that requires 64bits arithmetics.
But this is definitevly not the case (otherwise this should be compiled
in the kernel and not as a module).
Then your module (divdi3.o I guess) is enough for the need of the
original poster of this thread.
But the best thing to do for him is to rewrite his module to avoid
these 64bits operations.
As a side note, I was a contributor for this part of GFS and Sistina
never contacted me to ask me to give them my right before their
relicensing. But perhaps they have dropped the ppc support.
Christophe
>
> Christoph
>
> --
> Of course it doesn't work. We've performed a software upgrade.
--
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
Cats seem go on the principle that it never does any harm to ask for
what you want. --Joseph Wood Krutch
[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]
prev parent reply other threads:[~2002-01-25 19:05 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é
2002-01-25 18:53 ` Christoph Hellwig
2002-01-25 19:03 ` christophe barbé [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=20020125190316.GM671@online.fr \
--to=christophe.barbe.ml@online.fr \
--cc=hch@ns.caldera.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox