From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Linux 4.11 FTBFS on m68k
Date: Sun, 14 May 2017 08:19:26 +0200 [thread overview]
Message-ID: <m2bmqwot8x.fsf@linux-m68k.org> (raw)
In-Reply-To: <284dc1b1-1fef-90c3-f56f-7927f5bf22b0@gmail.com> (Michael Schmitz's message of "Sun, 14 May 2017 15:11:24 +1200")
On Mai 14 2017, Michael Schmitz <schmitzmic@gmail.com> wrote:
> this may be compiler version specific - I recall these functions were
> used from the kernel source with gcc 3.3.6 or thereabouts (I had to add
> __divdi3 five years ago for some driver that needed it and it wasn't
> then provided by gcc for some reason).
The kernel deliberately does not use libgcc, and it does not want a
64-bit devision on 32-bit archs.
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:[~2017-05-14 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 13:16 Linux 4.11 FTBFS on m68k John Paul Adrian Glaubitz
2017-05-07 16:11 ` Andreas Schwab
2017-05-08 9:13 ` Geert Uytterhoeven
2017-05-08 17:32 ` Andreas Schwab
2017-05-08 17:34 ` John Paul Adrian Glaubitz
2017-05-12 8:47 ` John Paul Adrian Glaubitz
2017-05-14 3:11 ` Michael Schmitz
2017-05-14 6:19 ` Andreas Schwab [this message]
2017-05-16 1:58 ` Michael Schmitz
2017-05-14 7:55 ` John Paul Adrian Glaubitz
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=m2bmqwot8x.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=debian-68k@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.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