public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Cc: Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Linux 4.11 FTBFS on m68k
Date: Sun, 14 May 2017 15:11:24 +1200	[thread overview]
Message-ID: <284dc1b1-1fef-90c3-f56f-7927f5bf22b0@gmail.com> (raw)
In-Reply-To: <20170512084740.GE29311@physik.fu-berlin.de>

Hi Adrian,

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). WIth gcc version 4, the need for
this hack was gone.

What version of gcc does Debian use for building their kernel packages?
What did you use?

Cheers,

	Michael


Am 12.05.2017 um 20:47 schrieb John Paul Adrian Glaubitz:
> On Sun, May 07, 2017 at 03:16:41PM +0200, John Paul Adrian Glaubitz wrote:
>> Just noticed that currently the 4.11 kernel fails to build from source
>> on m68k [1]:
> 
> Ok, this problem is actually Debian-specific. Debian's linux source
> package contains a patch which removes the necessary #include
> directive for <linux/compiler.h> [1].
> 
> I'll open a bug report.
> 
> Adrian
> 
>> [1] https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian/patches/bugfix/m68k/revert-m68k-move-exports-to-definitions.patch#n150
> 

  reply	other threads:[~2017-05-14  3:11 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 [this message]
2017-05-14  6:19     ` Andreas Schwab
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=284dc1b1-1fef-90c3-f56f-7927f5bf22b0@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.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