linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Momchil Velikov <velco@fadata.bg>
To: Kaoru Fukui <k_fukui@highway.ne.jp>
Cc: hozer@drgw.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: Broken asm/div64.h macro
Date: 28 Jan 2002 10:16:28 +0200	[thread overview]
Message-ID: <87wuy2c2lf.fsf@fadata.bg> (raw)
In-Reply-To: <200201280141.KAA17879@mail.highway.ne.jp>


>>>>> "Kaoru" == Kaoru Fukui <k_fukui@highway.ne.jp> writes:

Kaoru> On 27 Jan, Troy Benjegerdes wrote:
>> Did you actually try compiling PPC this way??
>>
>> vsprintf.o(.text+0x494): undefined reference to `__umoddi3'
>> vsprintf.o(.text+0x494): relocation truncated to fit: R_PPC_REL24
>> __umoddi3
>> vsprintf.o(.text+0x4ac): undefined reference to `__udivdi3'
>> vsprintf.o(.text+0x4ac): relocation truncated to fit: R_PPC_REL24
>> __udivdi3

Kaoru> libgcc.a has those libraries.

Yeah, but we don't link with libgcc.a. (which I forgot).

I'll do something along the lines of
#ifndef __HAVE_ARCH_DO_DIV
...
#endif

... soon.

Regards,
-velco


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-01-28  8:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-26 16:37 Broken asm/div64.h macro Troy Benjegerdes
2002-01-26 17:27 ` Geert Uytterhoeven
2002-01-26 22:30 ` Gabriel Paubert
2002-01-26 22:51 ` Momchil Velikov
2002-01-27 17:49   ` Troy Benjegerdes
2002-01-28  1:38     ` Kaoru Fukui
2002-01-28  8:16       ` Momchil Velikov [this message]
2002-01-28 15:28         ` Tom Rini
2002-01-28 19:45           ` Geert Uytterhoeven
2002-01-29  0:37             ` Tom Rini
2002-01-29  5:05               ` Kaoru Fukui
2002-01-29  6:26                 ` Troy Benjegerdes
2002-01-29 15:01                 ` Tom Rini

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=87wuy2c2lf.fsf@fadata.bg \
    --to=velco@fadata.bg \
    --cc=hozer@drgw.net \
    --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).