[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180420192832.GA1870@amd>
Date: Fri, 20 Apr 2018 21:28:32 +0200
From: Pavel Machek <pavel@....cz>
To: Daniel Micay <danielmicay@...il.com>
Cc: Kees Cook <keescook@...omium.org>,
Tony Lindgren <tony@...mide.com>,
Thorsten Leemhuis <regressions@...mhuis.info>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
pali.rohar@...il.com, sre@...nel.org,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-omap@...r.kernel.org, Kevin Hilman <khilman@...nel.org>,
Aaro Koskinen <aaro.koskinen@....fi>,
ivo.g.dimitrov.75@...il.com,
Patrik Bachan <patrikbachan@...il.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
Mickuláš Qwertz <abcloriens@...il.com>,
Clayton Craft <clayton@...ftyguy.net>,
Martijn Braam <martijn@...xit.nl>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Filip Matijević <filip.matijevic.pz@...il.com>,
Jinbum Park <jinb.park7@...il.com>,
Russell King <rmk+kernel@...linux.org.uk>
Subject: Re: [regression v4.17-rc0] Re: FORTIFY_SOURCE breaks ARM compilation
in -next -- was Re: ARM compile failure in Re: linux-next: Tree for Apr 4
On Fri 2018-04-20 15:18:32, Daniel Micay wrote:
> On 20 April 2018 at 15:15, Pavel Machek <pavel@....cz> wrote:
> > Hi!
> >
> >> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to
> >> >> a particular subset of arm architectures? (My local builds of arm all
> >> >> succeed, for example. Can you send your failing config?) I'll take a
> >> >> closer look on Monday if Daniel doesn't beat me to it.
> >> >
> >> > Daniel, Kees: any news?
> >> >
> >> > I'm aware you did not specify which Monday :-).
> >>
> >> Hi! Sorry, I got distracted. So the .config you sent me builds fine
> >> with my cross compiler. I suspect this is something specific to ELDK's
> >> compiler. I can try some other compiler versions. What version of gcc
> >> is failing?
> >
> > I have:
> >
> > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-gcc --version
> > arm-linux-gnueabi-gcc (GCC) 4.7.2
> > Copyright (C) 2012 Free Software Foundation, Inc.
> > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-ld --version
> > GNU ld (GNU Binutils) 2.23.1.20121113
> > Copyright 2012 Free Software Foundation, Inc.
> >
> > Let me try with eldk-5.6:
> >
> > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-gcc --version
> > arm-linux-gnueabi-gcc (GCC) 4.8.2
> > pavel@duo:/data/l/linux-n900$ arm-linux-gnueabi-ld --version
> > GNU ld (GNU Binutils) 2.24
> >
> > make lib/string.o
> >
> > Seems to succeed, so I guess full build will succeed, too...
>
> It doesn't imply that a full build would work.
You are right. eldk-5.6 does not have problem with string.o, but does
not compile the kernel, either...
CC arch/arm/kernel/asm-offsets.s
arch/arm/kernel/asm-offsets.c:56:2: error: #error Your compiler is
too buggy; it is known to miscompile kernels
#error Your compiler is too buggy; it is known to miscompile
kernels
^
arch/arm/kernel/asm-offsets.c:57:2: error: #error and result in
filesystem corruption and oopses.
#error and result in filesystem corruption and oopses.
^
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists