[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150928135841.GV21513@n2100.arm.linux.org.uk>
Date: Mon, 28 Sep 2015 14:58:41 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: Build regressions/improvements in v4.3-rc3
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@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists