public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Linux/m68k <linux-m68k@vger.kernel.org>
Cc: Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Linux 4.11 FTBFS on m68k
Date: Fri, 12 May 2017 10:47:40 +0200	[thread overview]
Message-ID: <20170512084740.GE29311@physik.fu-berlin.de> (raw)
In-Reply-To: <b9276262-0f50-02c3-1751-344651d7e377@physik.fu-berlin.de>

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

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  parent reply	other threads:[~2017-05-12  8:47 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 [this message]
2017-05-14  3:11   ` Michael Schmitz
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=20170512084740.GE29311@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=debian-68k@lists.debian.org \
    --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