[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161104161712.m3r6ph5e5rrbd3jq@linutronix.de>
Date: Fri, 4 Nov 2016 17:17:12 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Christoph Hellwig <hch@...radead.org>,
"Austin S. Hemmelgarn" <ahferroin7@...il.com>,
Ben Hutchings <ben@...adent.org.uk>,
linux-kernel@...r.kernel.org, Sven Joachim <svenjoac@....de>,
Tomas Janousek <tomi@...i.cz>, Joe Perches <joe@...ches.com>,
Adam Borowski <kilobyte@...band.pl>,
Michal Marek <mmarek@...e.com>, linux-kbuild@...r.kernel.org,
doko@...ian.org
Subject: Re: [PATCH 2/2] kbuild: add -fno-PIE
On 2016-11-04 16:10:48 [+0000], Al Viro wrote:
> And I don't see any way around severity:important against gcc-6. Unless the
> policy has changed, "has a major effect on the usability of a package, without
> rendering it completely unusable to everyone" still warrants that. And
> kernel development (including bisects) has, until now, been consdered
> a normal use of gcc.
point. Granted. We had the same thing a while back when `GNU make' update
led to an build error due a rule in kernel's Makefile.
Sebastian
Powered by blists - more mailing lists