From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Build regressions/improvements in v4.3-rc3
Date: Mon, 28 Sep 2015 14:58:41 +0100 [thread overview]
Message-ID: <20150928135841.GV21513@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAMuHMdU5UGfDSzfNWsZvsgLvJJYK-5VWEZ841Zc4GYfey6RdtA@mail.gmail.com>
On Mon, Sep 28, 2015 at 03:50:16PM +0200, Geert Uytterhoeven wrote:
> Hi Russell,
>
> On Mon, Sep 28, 2015 at 11:48 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Also, a great many of the failures are due to the build toolchain not
> > supporting -fstack-protector-strong. I think it's absolutely right
> > for the build to error out if you enable a kernel feature which requires
> > toolchain support, but the toolchain does not support that feature.
> >
> > What this means is that the build results from kissb are less than
> > useful - without spending ages looking at every single build, it's
> > hard to find the real failures we care about.
> >
> > I'd suggest that either the randconfig is seeded to ensure that
> > CONFIG_CC_STACKPROTECTOR_STRONG is always disabled in ARM randconfigs,
> > or that the ARM toolchain is updated to support this feature.
>
> Or that it's impossible to enable this feature if your toolchain doesn't
> support it?
I think that would require kconfig to call out to the compiler to run
a test build. This kind of thing has been talked about in the past
but the feature never seems to appear - probably because it would end
up increasing the kconfig startup time in every case.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-09-28 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1443382476-12171-1-git-send-email-geert@linux-m68k.org>
2015-09-28 6:57 ` Build regressions/improvements in v4.3-rc3 Geert Uytterhoeven
2015-09-28 9:30 ` Russell King - ARM Linux
2015-09-28 9:48 ` Russell King - ARM Linux
2015-09-28 13:50 ` Geert Uytterhoeven
2015-09-28 13:58 ` Russell King - ARM Linux [this message]
2015-09-28 14:08 ` Geert Uytterhoeven
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=20150928135841.GV21513@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).