From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@googlemail.com>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: compile error on latest git m68k kernel
Date: Wed, 10 Nov 2010 11:02:12 +0100 [thread overview]
Message-ID: <m3tyjpsdi3.fsf@linux-m68k.org> (raw)
In-Reply-To: <AANLkTi=pzN+7-wQMsVeV4AgVBYA-mGt42MwazaLPmVhg@mail.gmail.com> (Geert Uytterhoeven's message of "Wed, 10 Nov 2010 10:17:35 +0100")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Hi Michael,
>
> On Wed, Nov 10, 2010 at 08:08, Michael Schmitz
> <schmitzmic@googlemail.com> wrote:
>> seen this before?
>
> Not this particular one...
>
>> LD .tmp_vmlinux1
>> fs/built-in.o: In function `alignfile':
>> binfmt_elf.c:(.text+0x307bc): undefined reference to `__divdi3'
>> fs/built-in.o: In function `elf_core_dump':
>> binfmt_elf.c:(.text+0x3139c): undefined reference to `__divdi3'
>> make: *** [.tmp_vmlinux1] Error 1
Where is that called? The right fix in most cases is to use do_div from
<asm/div64.h>.
> ... but depending on the version of gcc, we sometimes need things like
> this, cfr.
> arch/m68k/lib/. The fix is to add a __divdi3 there.
It is not provided for a reason.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-11-10 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimA0ZOhNo=RO5ZhrQFNA6wWORekgj42dMNhnpGY@mail.gmail.com>
2010-11-10 9:17 ` compile error on latest git m68k kernel Geert Uytterhoeven
2010-11-10 10:02 ` Andreas Schwab [this message]
2010-11-10 10:34 ` Geert Uytterhoeven
2010-11-10 11:03 ` Andreas Schwab
2010-11-10 19:41 ` Michael Schmitz
2010-11-12 7:39 ` Michael Schmitz
2010-11-12 13:24 ` Thorsten Glaser
2010-11-13 8:38 ` Michael Schmitz
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=m3tyjpsdi3.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@googlemail.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