From: Jean-Jacques Levy <Jean-Jacques.Levy@inria.fr>
To: k_fukui@highway.ne.jp
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: __divdi3 unresolved + X pointer blocks
Date: Wed, 4 Jul 2001 21:06:10 -0400 [thread overview]
Message-ID: <200107050106.VAA01006@macaron.inria.fr> (raw)
In-Reply-To: <20010702235152.Postino-013684@smtp01.highway.ne.jp> (message from Kaoru Fukui on Mon, 2 Jul 2001 23:51:52 +0900)
Kaoru,
I installed gcc-3.0 release, and remained with my undefined
__divdi3. Then I patched inode.c in fs/fat and replaced two divisions
by 512 by >> 9. The error disapeared.
Either gcc-3.0 has a bug, either there is a missing module to
implement long divisions (by 512!) in fs/fat.o
Finally my kernel 2.4.6-pre6 (benh) still does not boot on my tibook
but problem must be elsewhere now.
-JJ-
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-05 1:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 20:31 __divdi3 unresolved + X pointer blocks Jean-Jacques Levy
2001-07-02 14:51 ` Kaoru Fukui
2001-07-05 1:06 ` Jean-Jacques Levy [this message]
2001-07-04 20:05 ` Benjamin Herrenschmidt
2001-07-05 5:50 ` Kernel crash with BenH' tree (was: Re: __divdi3...) Michel Lanners
2001-07-08 22:34 ` __divdi3 unresolved + X pointer blocks Jean-Jacques Levy
2001-07-04 22:22 ` David Edelsohn
2001-07-04 22:24 ` Kaoru Fukui
2001-07-04 22:45 ` Kaoru Fukui
2001-07-04 23:18 ` David Edelsohn
2001-07-05 8:13 ` Geert Uytterhoeven
2001-07-05 8:44 ` Kaoru Fukui
2001-07-05 11:48 ` Holger Bettag
2001-07-05 15:29 ` David Edelsohn
2001-07-05 16:55 ` Michael Schmitz
[not found] <20010711010133.Postino-018213@smtp01.highway.ne.jp>
2001-07-10 16:41 ` Kaoru Fukui
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 14:55 Kaoru Fukui
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=200107050106.VAA01006@macaron.inria.fr \
--to=jean-jacques.levy@inria.fr \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).