[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190724155735.GC5571@kroah.com>
Date: Wed, 24 Jul 2019 17:57:35 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: "H.J. Lu" <hjl.tools@...il.com>,
Mike Lothian <mike@...eburn.co.uk>,
Tom Lendacky <thomas.lendacky@....com>, bhe@...hat.com,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, lijiang@...hat.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andy Lutomirski <luto@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH v3 1/2] x86/mm: Identify the end of the kernel area to be
reserved
On Wed, Jul 24, 2019 at 05:49:45PM +0200, Thomas Gleixner wrote:
> On Wed, 24 Jul 2019, Greg KH wrote:
> > On Tue, Jul 23, 2019 at 03:44:54PM +0200, Greg KH wrote:
> > > Sorry, I saw that after writing that. You are right, if the others
> > > don't object, that's fine with me. I'll go poke the various build
> > > systems that are failing right now on 5.3-rc1 and try to get them fixed
> > > for this reason.
> >
> > Ok, I dug around and the gold linker is not being used here, only clang
> > to build the source and GNU ld to link, and I am still seeing this
> > error.
>
> Odd combo.
I'm not disagreeing :)
Wait, does clang link things itself and not need ld?
> > Hm, clang 8 does not cause this error, but clang 9 does. Let me go poke
> > the people who are providing this version of clang to see if there's
> > something they can figure out.
>
> Let me try that with my clang variant. Which version of GNU ld are you
> using?
I think it is 2.27:
$ ./ld --version
GNU ld (binutils-2.27-44492f8) 2.27.0.20170315
Which does feel old to me.
I know 2.32 works fine.
Gotta love old tool-chains :(
greg k-h
Powered by blists - more mailing lists