From: Sven Joachim <svenjoac@gmx.de>
To: Mark Brown <broonie@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v3.10.107 build: 2 failures 79 warnings (v3.10.107)
Date: Tue, 08 Aug 2017 16:58:58 +0200 [thread overview]
Message-ID: <87d186umvh.fsf@turtle.gmx.de> (raw)
In-Reply-To: <20170808144406.3u3kjrdxtghgg2od@sirena.org.uk> (Mark Brown's message of "Tue, 8 Aug 2017 15:44:06 +0100")
On 2017-08-08 15:44 +0100, Mark Brown wrote:
> On Tue, Aug 08, 2017 at 02:17:26PM +0200, Willy Tarreau wrote:
>> On Tue, Aug 08, 2017 at 01:08:29PM +0100, Build bot for Mark Brown wrote:
>
>> > x86_64-allnoconfig
>> > /home/broonie/build/linux-stable/scripts/mod/empty.c:1:0: error: code model kernel does not support PIC mode
>> > /home/broonie/build/linux-stable/scripts/mod/devicetable-offsets.c:1:0:
>> > error: code model kernel does not support PIC mode
>> > /home/broonie/build/linux-stable/kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
>
>> Are you sure it's not just a toolchain issue ? I can't reproduce this one
>> here, it completes correctly :
>
> It's *possible* it's related to the toolchain, it might be a new
> toolchain vs old kernel problem.
>
>> Using gcc 4.7.4 here FWIW.
>
> This is GCC 6.3.0-18 from Debian stable which is a bit newer.
Backporting commits 8ae94224c9d72 ("kbuild: add -fno-PIE") and
c6a385539175 ("kbuild: Steal gcc's pie from the very beginning") seems
to be required to build kernels with that compiler, at least if stack
protection is enabled.
For some of the gory details, see https://bugs.debian.org/841420.
Cheers,
Sven
next prev parent reply other threads:[~2017-08-08 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 12:08 v3.10.107 build: 2 failures 79 warnings (v3.10.107) Build bot for Mark Brown
2017-08-08 12:17 ` Willy Tarreau
2017-08-08 14:44 ` Mark Brown
2017-08-08 14:58 ` Sven Joachim [this message]
2017-08-08 15:37 ` Willy Tarreau
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=87d186umvh.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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;
as well as URLs for NNTP newsgroup(s).