public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: christophe.barbe.ml@online.fr (christophe barb? )
Cc: linux-kernel@vger.kernel.org, simon@baydel.com
Subject: Re: unresolved symbols __udivdi3 and __umoddi3
Date: Fri, 25 Jan 2002 19:53:38 +0100	[thread overview]
Message-ID: <200201251853.g0PIrcB28774@ns.caldera.de> (raw)
In-Reply-To: <20020125170642.GG671@online.fr>

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.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  reply	other threads:[~2002-01-25 18:58 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 [this message]
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=200201251853.g0PIrcB28774@ns.caldera.de \
    --to=hch@ns.caldera.de \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox